JEDEC JESD220-2 UFS存储卡标准

UFS2.2和UFS2.1对比有哪些更新
UFS2.2和UFS2.1对比有哪些更新
卡饭网大白 2020-08-20 09:55:43
今天发布了UFS 2.2标准，已经有多个芯片进行支持，也明确了该标准的规范，其中UFS 2.2比UFS2.1有更快的写入速度，相信可以给用户带来更好的使用体验的，还加入了全新的功能。

下面就让小编给大家介绍一下。

JEDEC固态技术协会今天公布了新的Universal Flash Storege ( UFS）标准UFS 2.2，新增支持联发科天玑80OU和天玑720 SoC芯片。

天玑800U和天玑720 SoC芯片在之前已经支持UFS 2.2标准，但是当时最新的UFS标准2.x版本为UFS 2.1，3.x版本为UFS 3.1，所以详细的内容还没有公布。

现在JEDEC已经发布了UFS 2.2标准，文件号为JESDJESD22OC-2.2，已经明确了该标准的规范。

UFS 2.2和UFS 2.1的区别在于增加了Write Booster(写入加速器)功能，比UFS 2.1提高了写入速度。

写入速度的提高会带来更快的应用启动速度、缓存加载带来更好的浏览行为、更快的编码时间等诸多良好特性。

在eMMC逐渐从主流消费市场退出后，UFS 2.2或将成为主力，况且NAND闪存仍处于降价轨道，某种程度上加快了普及速度。

以上就是UFS2.2和UFS2.1对比有哪些更新的全部内容，希望以上内容能帮助到朋友们。

jedec参数JEDEC（全称为Joint Electron Device Engineering Council）是一个非营利性的国际标准化组织，致力于电子器件和半导体技术的标准化工作。

JEDEC的成立旨在促进电子工业的发展，提高电子产品的质量和可靠性。

本文将介绍JEDEC的一些重要参数和其在电子工业中的应用。

JEDEC定义了一系列关于半导体器件的参数，这些参数对于电子工程师在设计和制造电子产品时非常重要。

其中一个重要的参数是温度系数（Temperature Coefficient），它衡量了器件在温度变化下的性能稳定性。

温度系数可以用来衡量器件的温度敏感性，帮助工程师选择适合的器件用于不同的应用环境。

另外，JEDEC还定义了器件的工作温度范围，这对于确保器件的正常工作非常重要。

除了温度相关的参数，JEDEC还定义了器件的封装规格。

封装是将芯片和电路连接到外部世界的关键步骤，它包括芯片的封装形式以及引脚的布局。

JEDEC定义了一系列标准封装，例如DIP（Dual In-line Package）、SOP（Small Outline Package）等，以及相应的引脚布局和尺寸。

这些标准封装可以确保不同厂商的芯片能够在相同的封装下互换使用，提高了电子产品的可扩展性和兼容性。

JEDEC还定义了器件的供电电压范围和电源电流。

供电电压范围是指器件正常工作所需的电压范围，这对于电源设计和电路稳定性至关重要。

电源电流则是指器件在正常工作状态下所消耗的电流，这对于电源选择和电路设计也非常重要。

JEDEC通过定义这些参数，帮助工程师更好地理解和选择合适的器件，从而提高电子产品的性能和可靠性。

JEDEC还定义了一系列关于存储器器件的标准。

存储器是电子产品中重要的组成部分，它用于存储和读取数据。

JEDEC定义了不同类型的存储器器件，例如DRAM（Dynamic Random-Access Memory）、SRAM（Static Random-Access Memory）等，并规定了它们的工作电压、时序、引脚布局等参数。

jedec 三类内存标准
JEDEC（联合电子设备工程委员会）制定了三种内存标准，分别是DDR（双倍数据率）、SDRAM（同步动态随机存取存储器）和NVRAM（非易失性存储器）。

1. DDR（Double Data Rate）：DDR内存是一种高速、高带宽
的内存标准，用于提升计算机系统的性能。

DDR内存有多个
版本，包括DDR2、DDR3和DDR4，每个版本都有逐步提高
的数据传输速度和带宽。

DDR内存在计算机系统中广泛应用，包括台式机、笔记本电脑和服务器等。

2. SDRAM（Synchronous Dynamic Random Access Memory）：SDRAM是一种同步动态随机存取存储器，采用了同步电路控
制数据传输，提供更高的数据传输速度。

SDRAM有多个版本，包括DDR SDRAM、DDR2 SDRAM、DDR3 SDRAM和
DDR4 SDRAM等。

SDRAM用于计算机系统的主存储器，提
供了快速的数据读写速度。

3. NVRAM（Non-Volatile Random Access Memory）：
NVRAM是一种非易失性随机存取存储器，可以在断电或重启后保留数据。

NVRAM使用不同的技术实现，包括闪存、磁性随机存取存储器（MRAM）、相变存储器（PRAM）等。

NVRAM广泛应用于嵌入式系统、汽车电子、物联网设备等对数据持久性要求较高的领域。

STANDARDUniversal Flash Storage (UFS) Card ExtensionVersion 1.0JESD220-2MARCH 2016JEDEC SOLID STATE TECHNOLOGY ASSOCIATIONNOTICEJEDEC standards and publications contain material that has been prepared, reviewed, and approved through the JEDEC Board of Directors level and subsequently reviewed and approved by the JEDEClegal counsel.JEDEC standards and publications are designed to serve the public interest through eliminatingmisunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for use by those other than JEDEC members, whether the standard is to be used eitherdomestically or internationally.JEDEC standards and publications are adopted without regard to whether or not their adoption may involve patents or articles, materials, or processes. By such action JEDEC does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the JEDEC standards orpublications.The information included in JEDEC standards and publications represents a sound approach to product specification and application, principally from the solid state device manufacturer viewpoint. Within the JEDEC organization there are procedures whereby a JEDEC standard or publication may be further processed and ultimately become an ANSI standard. No claims to be in conformance with this standardmay be made unless all requirements stated inthe standard are met.Special Legal Disclaimer: JEDEC has received information that certain patents or patent applications may be essential to this standard. However, as of the publication date of this standard, no statements regarding an assurance to license such patents or patent applications have been provided. JEDEC does not make any determination as to the validity or relevancy of such patents or patent applications. Anyone making use of the standard assumes all liability resulting from such use. JEDEC and its members disclaim any representation or warranty, express or implied, relating to the standard and its use. Inquiries, comments, and suggestions relative to the content of this JEDEC standard or publication should be addressed to JEDEC at the address below, or refer to under Standards and Documentsfor alternative contact information.Published by©JEDEC Solid State Technology Association 20163103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107This document may be downloaded free of charge; however JEDEC retains the copyright on this material.By downloading this file the individual agrees not to charge for or resell the resulting material.PRICE: Contact JEDECPrinted in the U.S.A.All rights reservedPLEASE!DON’T VIOLATETHELAW!This document is copyrighted by JEDEC and may not bereproduced without permission.For information, contact:JEDEC Solid State Technology Association3103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107or refer to under Standards-Documents/Copyright Information.JEDEC Standard No. 220-2 UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0ContentsPage Foreword i Introduction i 1Scope 1 2Normative Reference 1 3Terms, and definitions 1 3.1Acronyms 1 3.2Terms and definitions 2 3.3Keywords 2 3.4Abbreviations 3 3.5Conventions 3 4Introduction 4 4.1Overview 4 4.2Functional Features 4 5UFS Card System Architecture 5 5.1Overview 5 5.2UFS Card Signals 5 6UFS Card Design 6 7Feature comParison of embedded UFS and UFS card 9 8UFS Card initialization 10 8.1Initialization Sequence 11 9Power Consumption 12 Annex A (informative) Host Guideline for UFS Card Detection 13 FiguresFigure 5.1 — UFS Card Block Diagram 5 Figure 6.1 — UFS Card Top View 6 Figure 6.2 — UFS Card Bottom View 7 Figure 6.3 — UFS Card Side View 8 Figure 8.1 — UFS Card Initialization 10 Figure 8.2 — UFS Card Initialization Sequence 11 TablesTable 5.1 — Signal Name and Definitions 5 Table 7.1 — Comparison of embedded UFS and UFS Card 9JEDEC Standard No. 220-2UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0ForewordThis standard has been prepared by JEDEC. The purpose of this standard is to define a UFS card specification. This document will be extension of the UFS Standard, JESD220.IntroductionThe UFS device (embedded/removable) is a universal data storage and communication media. It is designed to cover a wide area of applications as smart phones, cameras, organizers, PDAs, digital recorders, MP3 players, internet tablets, electronic toys, etc.JEDEC Standard No. 220-2Page 1 UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0 (From JEDEC Board Ballot JCB-16-12, formulated under the cognizance of the JC-64.1 Subcommittee on Electrical Specifications and Command Protocols (Item 133.69).)1ScopeThis standard specifies the characteristics of the UFS card electrical interface and the memory device. This document defines the added/modified features in UFS card compared to embedded UFS device. For other common features JESD220, UFS, Version 2.0, will be referenced.2Normative ReferenceThe following normative documents contain provisions that, through reference in this text, constitute provisions of this standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents listed. For undated references, the latest edition of the normative document referred to applies.[MIPI-M-PHY], MIPI Alliance Specification for M-PHY SM Specification, Version 3.0[MIPI-UniPro], MIPI Alliance Specification for Unified Protocol (UniPro SM), Version 1.6[MIPI-DDB], MIPI Alliance Specification for Device Descriptor Block (DDB), Version[SAM], SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010[SPC], T10 Specification: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010 [SBC], T10 Specification: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010 [UFS], JEDEC JESD220B, Universal Flash Storage (UFS), Version 2.0[UFS], JEDEC JEP95, MO-320, UFS Card Form Factor3Terms, and definitionsFor the purpose of this standard, the terms and definitions given in the documents included in section 2“Normative Reference” and the following apply.3.1JEDEC Standard No. 220-2Page 23 Terms, and definitions (cont’d)3.2Terms and definitionsByte: An 8‐bit data value with most significant bit labeled as bit 7 and least significant bit as bit 0. Device: An addressable device on the UFS bus usually a target that contains at least one LUNHost: An addressable device on the UFS bus which is usually the main CPU that hosts the UFS bus3.3KeywordsSeveral keywords are used to differentiate levels of requirements and options, as follow:Can: A keyword used for statements of possibility and capability, whether material, physical, or causal (can equals is able to).Expected: A keyword used to describe the behavior of the hardware or software in the design models assumed by this standard. Other hardware and software design models may also be implemented. Ignored: A keyword that describes bits, bytes, quadlets, or fields whose values are not checked by the recipient.Mandatory: A keyword that indicates items required to be implemented as defined by this standard. May: A keyword that indicates a course of action permissible within the limits of the standard (may equals is permitted).Must: The use of the word must is deprecated and shall not be used when stating mandatory requirements; must is used only to describe unavoidable situations.Optional: A keyword that describes features which are not required to be implemented by this standard. However, if any optional feature defined by the standard is implemented, it shall be implemented as defined by the standard.Reserved: A keyword used to describe objects—bits, bytes, and fields—or the code values assigned to these objects in cases where either the object or the code value is set aside for future standardization. Usage and interpretation may be specified by future extensions to this or other standards. A reserved object shall be zeroed or, upon development of a future standard, set to a value specified by such a standard. The recipient of a reserved object shall not check its value. The recipient of a defined object shall check its value and reject reserved code values.Shall: A keyword that indicates a mandatory requirement strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to). Designers are required to implement all such mandatory requirements to assure interoperability with other products conforming to this standard.Should: A keyword used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited (should equals is recommended that).Will: The use of the word will is deprecated and shall not be used when stating mandatory requirements; will is only used in statements of fact.JEDEC Standard No. 220-2Page 3 3 Terms, and definitions (cont’d)3.4Abbreviationsetc. - And so forth (Latin: et cetera)e.g. - For example (Latin: exempli gratia)i.e. - That is (Latin: id est)3.5ConventionsUFS specification follows some conventions used in SCSI documents since it adopts several SCSI standards.A binary number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 and 1 immediately followed by a lower-case b (e.g., 0101b). Spaces may be included in binary number representations to increase readability or delineate field boundaries (e.g., 0 0101 1010b).A hexadecimal number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 through 9 and/or the upper-case English letters A through F immediately followed by a lower-case h (e.g., FA23h). Spaces may be included in hexadecimal number representations to increase readability or delineate field boundaries (e.g.,B FD8C FA23h).A decimal number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 through 9 not immediately followed by a lower-case b or lower-case h (e.g.,25).A range of numeric values is represented in this standard in the form "a to z", where a is the first value included in the range, all values between a and z are included in the range, and z is the last value included in the range (e.g., the representation "0h to 3h" includes the values 0h, 1h, 2h, and 3h).When the value of the bit or field is not relevant, x or xx appears in place of a specific value.The first letter of the name of a Flag is a lower-case f (e.g., fMyFlag).The first letter of the name of a parameter included a Descriptor or the first letter of the name of an Attribute is:∙ a lower-case b if the parameter or the Attribute size is one byte (e.g., bMyParameter),∙ a lower-case w if the parameter or the Attribute size is two bytes (e.g., wMyParameter),∙ a lower-case d if the parameter or the Attribute size is four bytes (e.g., dMyParameter),∙ a lower-case q if the parameter or the Attribute size is eight bytes (e.g., qMyParameter).JEDEC Standard No. 220-2Page 44Introduction4.1OverviewThe JESD220 standard already defined some features for UFS card (removable). The UFS card uses same protocol as embedded UFS device, but it has few card specific requirements like power consumption.4.2Functional FeaturesUFS card functional features are similar to UFS embedded device. These include:∙Support for MIPI M-PHY PWM-Gear1. HS-Gear2 (optional) and HS-Gear3∙Supports Multiple partitions (LUNs) with partition Management∙Supports Multiple User Data Partition with Enhanced User Data Area options∙Reliable write operation∙Background operations∙Secure operations, Purge and Erase to enhance data security∙Write Protection options, including Permanent and Power-On Write Protection∙Task management operations∙Power management operations5UFS Card System Architecture5.1OverviewThe UFS card will use same protocol as embedded UFS device. There will not be any change in the overall system architecture of removable UFS card compared to embedded card.5.2UFS Card SignalsFigure 5.1 shows the conceptual drawing of UFS card.C/DFigure 5.1 — UFS Card Block Diagram6 UFS Card DesignThe UFS card will follow the shark design and a simplified pictorial representation is shown in Figure 6.1. Refer to JEP95, MO-320, for more detailed mechanical dimensions of Figure 6.1, Figure 6.2 and Figure 6.3.Figure 6.1 — UFS Card Top View6 UFS Card Design (cont’d)Figure 6.2 — UFS Card Bottom ViewPin 16 UFS Card Design (cont’d)Figure 6.3 — UFS Card Side View7Feature comparison of embedded UFS and UFS cardThe embedded UFS and UFS card follow the same protocol. But they will be used in different environment, the use cases will differ. So the UFS card shall have differences in supporting few features compared to embedded UFS. Table 7.1 shows the difference between embedded UFS and UFS card.The UFS card is supposed to be lite version of embedded UFS. So support for unnecessary gears shall be removed and UFS card shall supports only PWM-Gear1, HS-Gear2 (optional), and HS-Gear3. Similarly the UFS card shall support up to 1 lane compared to embedded UFS supports 2 lanes.VCCQ : The VCCQ pin is removed from UFS card to reduce the pin count. The UFS card vendors can use embed LDO to get the lower voltage which is aligned to their low voltage core from 3.3 V or 1.8 V source. Also as a power supply, 3.3 V and 1.8 V are mandatory considering the NAND controller, I/O logic. But 1.2 V can be generated wisely from 3.3 V or 1.8 V. So VCCQ pin (1.2 V) is not supported in UFS card.HW Reset : In case of embedded UFS the chip cannot be detached from the system PCB, so the HW reset pin is required.But in UFS card, card removal is possible, therefore the HW reset pin can be avoided. The minimizing of UFS card pin count can reduce the development and testing cost.Attributes : In embedded UFS the bRefClkFreq, bMaxNumOfRTT, and bMaxDataInSize, bMaxDataOutSize, bOutOfOrderDataEn and bActiveICCLevel attribute values are persistent. As the embedded UFS chip can’t be removed from the host, making these attributes value as persistent avoids re-initialization of these attributes. But in case of UFS card, it can be inserted in to different host which may want to use different values for these parameters. So in UFS card these attributes value shall reset to default value after every reset.8 UFS Card initializationThe UFS cad initialization follows same sequence as of eUFS. But as this is a removable device,VCC(3.3 V) and VCCQ2(1.8 V) may be provided after the UFS card is fully inserted into the card slot. The C/D pin may be used to support card insertion detection (refer to Annex A).Figure 8.1 — UFS Card InitializationCard Insertion UFS Link Start -up Process WaitNot Inserted Supply VCCQ2(1.8 V), VCC(3.3 V) Detect Card insertion in VoltageInserted8.1Initialization SequenceOnce the reset is done, the host will set the attributes to make the card compatible with the particular host.Figure 8.2 — UFS Card Initialization SequenceThe UFS card initialization is same as of embedded UFS, except the bRefClkFreq, bMaxNumOfRTT, bMaxDataInSize, bMaxDataOutSize,bOutOfOrderDataEn and bActiveICClevel attributes value will be set by the host. In embedded UFS these attributes will retain the value after the reset. But since the UFS card can be inserted into different host, these attribute values will be reset to their default value. The host has to set appropriate value before changing the mode to high speed mode.9Power ConsumptionThe UFS card shall be able to work in any host. Therefore power level which any UFS card can work shall be defined for host to provide required amount of power. So considering the removable card industry, the 1.6 watt would be needed for power consumption of the UFS card . The UFS card shall consume maximum 300 mA from VCC(3.3 V) and maximum 300 mA from VCCQ2(1.8 V).Annex A (informative) Host Guideline for UFS Card DetectionThe card detection (C/D) pin may be utilized to detect card insertion, by adding pull-up resistor to the C/D pin in the host-side C/D pin. When the UFS card is not inserted, host-side C/D pin shows non-zero voltage value. When the UFS card is inserted, host-side C/D pin shows zero voltage value because C/D pin of device is tied to ground.Figure A.1 — Host guideline for UFS Card DetectionUFS Card UFS HostStandard Improvement Form JEDECThe purpose of this form is to provide the Technical Committees of JEDEC with input from the industry regarding usage of the subject standard. Individuals or companies are invited to submit comments to JEDEC. All comments will be collected and dispersed to the appropriate committee(s).If you can provide input, please complete this form and return to:JEDECAttn: Publications Department3103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107Fax: 703.907.7583Requirement, clause numberTest method number Clause numberUnclear Too RigidIn ErrorOther2. Recommendations for correction:3. Other suggestions for document improvement:Submitted byName: Phone: Company: E-mail: Address:City/State/Zip: Date:。

STANDARDUniversal Flash Storage (UFS) Card ExtensionVersion 1.0JESD220-2MARCH 2016JEDEC SOLID STATE TECHNOLOGY ASSOCIATIONNOTICEJEDEC standards and publications contain material that has been prepared, reviewed, and approved through the JEDEC Board of Directors level and subsequently reviewed and approved by the JEDEClegal counsel.JEDEC standards and publications are designed to serve the public interest through eliminatingmisunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for use by those other than JEDEC members, whether the standard is to be used eitherdomestically or internationally.JEDEC standards and publications are adopted without regard to whether or not their adoption may involve patents or articles, materials, or processes. By such action JEDEC does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the JEDEC standards orpublications.The information included in JEDEC standards and publications represents a sound approach to product specification and application, principally from the solid state device manufacturer viewpoint. Within the JEDEC organization there are procedures whereby a JEDEC standard or publication may be further processed and ultimately become an ANSI standard. No claims to be in conformance with this standardmay be made unless all requirements stated inthe standard are met.Special Legal Disclaimer: JEDEC has received information that certain patents or patent applications may be essential to this standard. However, as of the publication date of this standard, no statements regarding an assurance to license such patents or patent applications have been provided. JEDEC does not make any determination as to the validity or relevancy of such patents or patent applications. Anyone making use of the standard assumes all liability resulting from such use. JEDEC and its members disclaim any representation or warranty, express or implied, relating to the standard and its use. Inquiries, comments, and suggestions relative to the content of this JEDEC standard or publication should be addressed to JEDEC at the address below, or refer to under Standards and Documentsfor alternative contact information.Published by©JEDEC Solid State Technology Association 20163103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107This document may be downloaded free of charge; however JEDEC retains the copyright on this material.By downloading this file the individual agrees not to charge for or resell the resulting material.PRICE: Contact JEDECPrinted in the U.S.A.All rights reservedPLEASE!DON’T VIOLATETHELAW!This document is copyrighted by JEDEC and may not bereproduced without permission.For information, contact:JEDEC Solid State Technology Association3103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107or refer to under Standards-Documents/Copyright Information.JEDEC Standard No. 220-2 UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0ContentsPage Foreword i Introduction i 1Scope 1 2Normative Reference 1 3Terms, and definitions 1 3.1Acronyms 1 3.2Terms and definitions 2 3.3Keywords 2 3.4Abbreviations 3 3.5Conventions 3 4Introduction 4 4.1Overview 4 4.2Functional Features 4 5UFS Card System Architecture 5 5.1Overview 5 5.2UFS Card Signals 5 6UFS Card Design 6 7Feature comParison of embedded UFS and UFS card 9 8UFS Card initialization 10 8.1Initialization Sequence 11 9Power Consumption 12 Annex A (informative) Host Guideline for UFS Card Detection 13 FiguresFigure 5.1 — UFS Card Block Diagram 5 Figure 6.1 — UFS Card Top View 6 Figure 6.2 — UFS Card Bottom View 7 Figure 6.3 — UFS Card Side View 8 Figure 8.1 — UFS Card Initialization 10 Figure 8.2 — UFS Card Initialization Sequence 11 TablesTable 5.1 — Signal Name and Definitions 5 Table 7.1 — Comparison of embedded UFS and UFS Card 9JEDEC Standard No. 220-2UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0ForewordThis standard has been prepared by JEDEC. The purpose of this standard is to define a UFS card specification. This document will be extension of the UFS Standard, JESD220.IntroductionThe UFS device (embedded/removable) is a universal data storage and communication media. It is designed to cover a wide area of applications as smart phones, cameras, organizers, PDAs, digital recorders, MP3 players, internet tablets, electronic toys, etc.JEDEC Standard No. 220-2Page 1 UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0 (From JEDEC Board Ballot JCB-16-12, formulated under the cognizance of the JC-64.1 Subcommittee on Electrical Specifications and Command Protocols (Item 133.69).)1ScopeThis standard specifies the characteristics of the UFS card electrical interface and the memory device. This document defines the added/modified features in UFS card compared to embedded UFS device. For other common features JESD220, UFS, Version 2.0, will be referenced.2Normative ReferenceThe following normative documents contain provisions that, through reference in this text, constitute provisions of this standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. However, parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents listed. For undated references, the latest edition of the normative document referred to applies.[MIPI-M-PHY], MIPI Alliance Specification for M-PHY SM Specification, Version 3.0[MIPI-UniPro], MIPI Alliance Specification for Unified Protocol (UniPro SM), Version 1.6[MIPI-DDB], MIPI Alliance Specification for Device Descriptor Block (DDB), Version[SAM], SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010[SPC], T10 Specification: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010 [SBC], T10 Specification: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010 [UFS], JEDEC JESD220B, Universal Flash Storage (UFS), Version 2.0[UFS], JEDEC JEP95, MO-320, UFS Card Form Factor3Terms, and definitionsFor the purpose of this standard, the terms and definitions given in the documents included in section 2“Normative Reference” and the following apply.3.1JEDEC Standard No. 220-2Page 23 Terms, and definitions (cont’d)3.2Terms and definitionsByte: An 8‐bit data value with most significant bit labeled as bit 7 and least significant bit as bit 0. Device: An addressable device on the UFS bus usually a target that contains at least one LUNHost: An addressable device on the UFS bus which is usually the main CPU that hosts the UFS bus3.3KeywordsSeveral keywords are used to differentiate levels of requirements and options, as follow:Can: A keyword used for statements of possibility and capability, whether material, physical, or causal (can equals is able to).Expected: A keyword used to describe the behavior of the hardware or software in the design models assumed by this standard. Other hardware and software design models may also be implemented. Ignored: A keyword that describes bits, bytes, quadlets, or fields whose values are not checked by the recipient.Mandatory: A keyword that indicates items required to be implemented as defined by this standard. May: A keyword that indicates a course of action permissible within the limits of the standard (may equals is permitted).Must: The use of the word must is deprecated and shall not be used when stating mandatory requirements; must is used only to describe unavoidable situations.Optional: A keyword that describes features which are not required to be implemented by this standard. However, if any optional feature defined by the standard is implemented, it shall be implemented as defined by the standard.Reserved: A keyword used to describe objects—bits, bytes, and fields—or the code values assigned to these objects in cases where either the object or the code value is set aside for future standardization. Usage and interpretation may be specified by future extensions to this or other standards. A reserved object shall be zeroed or, upon development of a future standard, set to a value specified by such a standard. The recipient of a reserved object shall not check its value. The recipient of a defined object shall check its value and reject reserved code values.Shall: A keyword that indicates a mandatory requirement strictly to be followed in order to conform to the standard and from which no deviation is permitted (shall equals is required to). Designers are required to implement all such mandatory requirements to assure interoperability with other products conforming to this standard.Should: A keyword used to indicate that among several possibilities one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain course of action is deprecated but not prohibited (should equals is recommended that).Will: The use of the word will is deprecated and shall not be used when stating mandatory requirements; will is only used in statements of fact.JEDEC Standard No. 220-2Page 3 3 Terms, and definitions (cont’d)3.4Abbreviationsetc. - And so forth (Latin: et cetera)e.g. - For example (Latin: exempli gratia)i.e. - That is (Latin: id est)3.5ConventionsUFS specification follows some conventions used in SCSI documents since it adopts several SCSI standards.A binary number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 and 1 immediately followed by a lower-case b (e.g., 0101b). Spaces may be included in binary number representations to increase readability or delineate field boundaries (e.g., 0 0101 1010b).A hexadecimal number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 through 9 and/or the upper-case English letters A through F immediately followed by a lower-case h (e.g., FA23h). Spaces may be included in hexadecimal number representations to increase readability or delineate field boundaries (e.g.,B FD8C FA23h).A decimal number is represented in this standard by any sequence of digits consisting of only the Western-Arabic numerals 0 through 9 not immediately followed by a lower-case b or lower-case h (e.g.,25).A range of numeric values is represented in this standard in the form "a to z", where a is the first value included in the range, all values between a and z are included in the range, and z is the last value included in the range (e.g., the representation "0h to 3h" includes the values 0h, 1h, 2h, and 3h).When the value of the bit or field is not relevant, x or xx appears in place of a specific value.The first letter of the name of a Flag is a lower-case f (e.g., fMyFlag).The first letter of the name of a parameter included a Descriptor or the first letter of the name of an Attribute is:∙ a lower-case b if the parameter or the Attribute size is one byte (e.g., bMyParameter),∙ a lower-case w if the parameter or the Attribute size is two bytes (e.g., wMyParameter),∙ a lower-case d if the parameter or the Attribute size is four bytes (e.g., dMyParameter),∙ a lower-case q if the parameter or the Attribute size is eight bytes (e.g., qMyParameter).JEDEC Standard No. 220-2Page 44Introduction4.1OverviewThe JESD220 standard already defined some features for UFS card (removable). The UFS card uses same protocol as embedded UFS device, but it has few card specific requirements like power consumption.4.2Functional FeaturesUFS card functional features are similar to UFS embedded device. These include:∙Support for MIPI M-PHY PWM-Gear1. HS-Gear2 (optional) and HS-Gear3∙Supports Multiple partitions (LUNs) with partition Management∙Supports Multiple User Data Partition with Enhanced User Data Area options∙Reliable write operation∙Background operations∙Secure operations, Purge and Erase to enhance data security∙Write Protection options, including Permanent and Power-On Write Protection∙Task management operations∙Power management operations5UFS Card System Architecture5.1OverviewThe UFS card will use same protocol as embedded UFS device. There will not be any change in the overall system architecture of removable UFS card compared to embedded card.5.2UFS Card SignalsFigure 5.1 shows the conceptual drawing of UFS card.C/DFigure 5.1 — UFS Card Block Diagram6 UFS Card DesignThe UFS card will follow the shark design and a simplified pictorial representation is shown in Figure 6.1. Refer to JEP95, MO-320, for more detailed mechanical dimensions of Figure 6.1, Figure 6.2 and Figure 6.3.Figure 6.1 — UFS Card Top View6 UFS Card Design (cont’d)Figure 6.2 — UFS Card Bottom ViewPin 16 UFS Card Design (cont’d)Figure 6.3 — UFS Card Side View7Feature comparison of embedded UFS and UFS cardThe embedded UFS and UFS card follow the same protocol. But they will be used in different environment, the use cases will differ. So the UFS card shall have differences in supporting few features compared to embedded UFS. Table 7.1 shows the difference between embedded UFS and UFS card.The UFS card is supposed to be lite version of embedded UFS. So support for unnecessary gears shall be removed and UFS card shall supports only PWM-Gear1, HS-Gear2 (optional), and HS-Gear3. Similarly the UFS card shall support up to 1 lane compared to embedded UFS supports 2 lanes.VCCQ : The VCCQ pin is removed from UFS card to reduce the pin count. The UFS card vendors can use embed LDO to get the lower voltage which is aligned to their low voltage core from 3.3 V or 1.8 V source. Also as a power supply, 3.3 V and 1.8 V are mandatory considering the NAND controller, I/O logic. But 1.2 V can be generated wisely from 3.3 V or 1.8 V. So VCCQ pin (1.2 V) is not supported in UFS card.HW Reset : In case of embedded UFS the chip cannot be detached from the system PCB, so the HW reset pin is required.But in UFS card, card removal is possible, therefore the HW reset pin can be avoided. The minimizing of UFS card pin count can reduce the development and testing cost.Attributes : In embedded UFS the bRefClkFreq, bMaxNumOfRTT, and bMaxDataInSize, bMaxDataOutSize, bOutOfOrderDataEn and bActiveICCLevel attribute values are persistent. As the embedded UFS chip can’t be removed from the host, making these attributes value as persistent avoids re-initialization of these attributes. But in case of UFS card, it can be inserted in to different host which may want to use different values for these parameters. So in UFS card these attributes value shall reset to default value after every reset.8 UFS Card initializationThe UFS cad initialization follows same sequence as of eUFS. But as this is a removable device,VCC(3.3 V) and VCCQ2(1.8 V) may be provided after the UFS card is fully inserted into the card slot. The C/D pin may be used to support card insertion detection (refer to Annex A).Figure 8.1 — UFS Card InitializationCard Insertion UFS Link Start -up Process WaitNot Inserted Supply VCCQ2(1.8 V), VCC(3.3 V) Detect Card insertion in VoltageInserted8.1Initialization SequenceOnce the reset is done, the host will set the attributes to make the card compatible with the particular host.Figure 8.2 — UFS Card Initialization SequenceThe UFS card initialization is same as of embedded UFS, except the bRefClkFreq, bMaxNumOfRTT, bMaxDataInSize, bMaxDataOutSize,bOutOfOrderDataEn and bActiveICClevel attributes value will be set by the host. In embedded UFS these attributes will retain the value after the reset. But since the UFS card can be inserted into different host, these attribute values will be reset to their default value. The host has to set appropriate value before changing the mode to high speed mode.9Power ConsumptionThe UFS card shall be able to work in any host. Therefore power level which any UFS card can work shall be defined for host to provide required amount of power. So considering the removable card industry, the 1.6 watt would be needed for power consumption of the UFS card . The UFS card shall consume maximum 300 mA from VCC(3.3 V) and maximum 300 mA from VCCQ2(1.8 V).Annex A (informative) Host Guideline for UFS Card DetectionThe card detection (C/D) pin may be utilized to detect card insertion, by adding pull-up resistor to the C/D pin in the host-side C/D pin. When the UFS card is not inserted, host-side C/D pin shows non-zero voltage value. When the UFS card is inserted, host-side C/D pin shows zero voltage value because C/D pin of device is tied to ground.Figure A.1 — Host guideline for UFS Card DetectionUFS Card UFS HostStandard Improvement Form JEDECThe purpose of this form is to provide the Technical Committees of JEDEC with input from the industry regarding usage of the subject standard. Individuals or companies are invited to submit comments to JEDEC. All comments will be collected and dispersed to the appropriate committee(s).If you can provide input, please complete this form and return to:JEDECAttn: Publications Department3103 North 10th StreetSuite 240 SouthArlington, VA 22201-2107Fax: 703.907.7583Requirement, clause numberTest method number Clause numberUnclear Too RigidIn ErrorOther2. Recommendations for correction:3. Other suggestions for document improvement:Submitted byName: Phone: Company: E-mail: Address:City/State/Zip: Date:。

jedec 三类内存标准JEDEC（Joint Electron Device Engineering Council）是一个半导体工业的标准制定组织，它颁布了多种内存标准。

其中，JEDEC定义了三类常见的内存标准，分别是DRAM、SRAM和Flash。

1. DRAM（Dynamic Random Access Memory）：- DRAM是一种动态随机存取存储器，它是计算机系统中最常见的内存类型之一。

- DRAM存储单元由一个电容和一个访问晶体管组成，电容存储数据位。

由于电容会逐渐失去电荷，所以需要定期刷新（刷新周期）。

- JEDEC定义了不同类型的DRAM标准，如DDR（Double Data Rate）、DDR2、DDR3、DDR4等，它们在数据传输速率和技术方面有所不同。

2. SRAM（Static Random Access Memory）：- SRAM是一种静态随机存取存储器，相比于DRAM，它不需要定期刷新，但相对更昂贵且密度较低。

- SRAM存储单元由多个触发器（flip-flop）构成，每个触发器可以存储一个位。

- JEDEC并没有像DRAM那样详细定义SRAM的特定规范，因为SRAM通常用于较小的高速缓存而不是主存。

3. Flash Memory：- Flash是一种非易失性存储器，可用于数据存储和固件存储。

- JEDEC定义了多种Flash存储器标准，包括NAND Flash和NOR Flash。

NAND Flash通常用于主存储，而NOR Flash通常用于存储固件和代码。

-不同的Flash标准有不同的特性，例如擦写速度、读取速度、寿命等，其中NAND Flash 还被广泛用于SSD（固态硬盘）。

这些标准的制定有助于确保不同厂商生产的内存设备在计算机系统中的互操作性，并提供了一致的规范，以便硬件和软件开发人员设计和编写兼容的系统。

jesd22 标准JESD22标准。

JESD22标准是美国电子行业标准委员会（JEDEC）制定的一系列关于可靠性测试和可靠性评估的标准。

这些标准涵盖了半导体器件和电子产品的各个方面，旨在确保其在不同环境条件下的可靠性和稳定性。

作为电子行业的重要标准之一，JESD22标准对于半导体器件和电子产品的设计、生产和使用具有重要意义。

首先，JESD22标准涵盖了各种环境条件下的可靠性测试方法。

这些环境条件包括高温、低温、湿热、机械应力等，通过对器件在这些条件下的性能进行测试，可以评估其在实际使用中的可靠性。

这些测试方法旨在模拟器件在不同环境下的工作情况，从而发现潜在的可靠性问题，并采取相应的措施加以改进。

其次，JESD22标准还包括了可靠性评估的指导原则。

这些原则涵盖了从测试方案的制定到结果分析的全过程，旨在确保可靠性测试的科学性和准确性。

通过遵循这些原则，可以有效地评估器件的可靠性，并为产品的设计和改进提供重要参考。

此外，JESD22标准还对可靠性数据的统计分析提出了要求。

在可靠性测试中产生的大量数据需要进行合理的统计分析，以确定器件的可靠性参数和可靠性指标。

这些统计分析方法旨在从数据中发现规律和趋势，为产品的可靠性设计提供依据。

总的来说，JESD22标准是电子行业不可或缺的一部分，它为半导体器件和电子产品的可靠性设计和评估提供了重要的指导。

遵循这些标准，可以有效地发现和解决产品在不同环境下的可靠性问题，提高产品的质量和可靠性，满足市场和客户的需求。

在实际应用中，各个企业和组织应当严格遵循JESD22标准的要求，制定科学合理的测试方案，进行可靠性测试和评估，并根据测试结果不断改进产品的设计和生产工艺。

只有这样，才能确保产品在各种复杂环境下的可靠性和稳定性，赢得客户的信赖和市场的认可。

综上所述，JESD22标准是电子行业的重要标准之一，它对半导体器件和电子产品的可靠性设计和评估具有重要意义。

遵循这些标准，可以有效地提高产品的质量和可靠性，满足市场和客户的需求，推动电子行业的健康发展。

jedec内存标准-回复Jedec内存标准从根本上来说，是计算机行业所接受的一种规范，用于确保尺寸、功能和兼容性的一致性。

Jedec（全称为Joint Electronic Device Engineering Council，联合电子设备工程委员会）是一个由半导体制造商、计算机制造商、电子设计自动化工具供应商和其他相关组织组成的标准化组织。

这些标准定义了计算机内存设备的物理特征和功能，以确保其在不同计算机系统中的兼容性。

内存是计算机系统中的一个关键组件，用于存储和读取数据以供处理器使用。

Jedec内存标准确保了不同内存设备的互操作性，使得不同厂商的计算机系统能够使用同一类型的内存。

Jedec内存标准通常涵盖以下方面：1. 内存尺寸和插槽类型：Jedec规定了不同类型内存的尺寸和形状，以确保其能够正确安装在计算机主板或服务器中。

例如，DDR4内存的尺寸为288引脚，而SO-DIMM内存则较小，适用于笔记本电脑和其他小型计算设备。

2. 内存插槽布局和电气连接：Jedec定义了不同类型内存插槽的布局，以确保内存能够正确插入并与主板上的电子连接。

这些标准还规定了内存与主板上其他组件之间的电气连接方式。

这对于确保数据传输的稳定性和可靠性至关重要。

3. 内存速度和时序：Jedec决定了不同内存设备的操作速度和时序。

内存速度指的是内存设备处理数据的能力，通常以数据传输速率来衡量（比如DDR4-3200）。

时序则是指内存设备在接收和发送数据时，各个操作的时间间隔。

这些标准的目的是确保不同内存设备之间的数据传输时序一致，以防止数据传输错误。

4. 功能和特性：Jedec标准还定义了内存设备的一些功能和特性，例如纠错码（ECC）以及不同种类的缓存和保护机制。

这些功能和特性的目的是提高内存的可靠性和数据完整性。

除了上述方面，Jedec内存标准还包括对内存模块的测试、维护和可靠性要求的规定。

这些要求确保了内存设备在长时间使用过程中的稳定性和性能。

内存 jedec标准内存JEDEC标准。

JEDEC是一家美国电子行业协会，它制定了许多与半导体存储器相关的标准，其中包括内存模块的标准。

内存JEDEC标准是指符合JEDEC制定的内存模块规范的产品，它们在尺寸、接口、工作电压、时序等方面都符合JEDEC的规定。

本文将介绍内存JEDEC标准的相关内容。

首先，内存JEDEC标准对内存模块的尺寸和接口进行了规定。

根据JEDEC标准，常见的内存模块包括DIMM（双列直插式内存模块）和SODIMM（小型双列直插式内存模块）。

这些内存模块在长度、宽度和插槽位置等方面都有严格的规定，以保证其能够正确插入主板上的内存插槽，并与主板的内存控制器正常通信。

其次，内存JEDEC标准还规定了内存模块的工作电压和时序。

在工作电压方面，JEDEC标准规定了不同类型的内存模块应该采用的工作电压范围，以确保其在不同的主板上能够正常工作。

在时序方面，JEDEC标准规定了内存模块的访问速度、延迟和刷新周期等参数，以确保其能够与主板的内存控制器协同工作，实现高效的数据传输。

此外，内存JEDEC标准还规定了内存模块的物理布局和引脚定义。

这些规定包括内存芯片的布局方式、引脚的功能定义、插槽的键位设计等，以确保不同厂家生产的内存模块在插入主板时能够正确对齐，并且能够与主板的内存控制器正确连接。

最后，内存JEDEC标准还规定了内存模块的测试方法和标识要求。

在测试方法方面，JEDEC标准规定了内存模块应该通过哪些测试项目以确保其质量和可靠性。

在标识要求方面，JEDEC标准规定了内存模块应该在外包装上标注哪些信息，以便用户能够准确识别其型号、容量、速度等信息。

总的来说，内存JEDEC标准是一系列与内存模块相关的规范，它涵盖了内存模块的尺寸、接口、工作电压、时序、物理布局、引脚定义、测试方法和标识要求等方面的内容。

遵循内存JEDEC标准生产的内存模块能够保证其在不同的主板上能够正常工作，并且能够与主板的内存控制器协同工作，实现高效的数据传输。

C:\Users\ ATC6100\ Desktop\ JEDEC标准\ JESD22-A100D.pdfC:\Users\ATC6100\ Desktop\JESD22-A101D.pdfC:\Users\ATC6100\Desktop\JEDEC标准\JESD22-A102E.pdf C:\Users\ ATC6100\ Desktop\JESD22-1D标准解读.docxC:\Users\ATC6100\Desktop\JESD22-A103E.pdfC:\Users\ATC6100\Desktop\JESD22-A104E.pdfC:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-A105C_0.pdfC:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-A106B-01.pdfC:\Users\ATC6100\Desktop\JEDEC标准\JESD22-A107C.pdfC:\Users\ATC6100\Desktop\JEDEC标准\JESD22-A108D.pdfC:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-A109B.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-A110E.pdf C:\Users\ATC6100\Desktop\JEDEC标准\JESD22-A111B.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\J-STD-020E.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-A113H.pdf C:\Users\ATC6100\Desktop\C:\Users\ATC6100\Desktop\JEDEC标准\JESD22-A117D.pdf C:\Users\ATC6100\Desktop\JEDEC标准\JESD22-A118B.pdf C:\Users\ATC6100\Desktop\JEDEC标准\JESD22-A119A.pdf C:\Users\ATC6100\Desktop\JESD22-A120B.pdfC:\Users\ATC6100\Desktop\JEDEC标准\JESD22-A121A_R.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-A122A.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-B100B.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-B101C.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-A120B.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-B103B-01.pdf C:\Users\ATC6100\Desktop\JESD22-B110B.pdf C:\Users\ATC6100\Desktop\JESD22-B105E.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-B106E.pdf C:\Users\ATC6100\Desktop\JESD22\JEDEC标准\JESD22-B107D_R.pdf C:\Users\ATC6100\Desktop\JEDEC标准\JESD22-B108B.pdfC:\Users\ ATC6100\ Desktop\ JEDEC标准\JESD22-B109B.pdf C:\Users\ ATC6100\ Desktop\JESD22-B110B.pdfC:\Users\ ATC6100\ Desktop\ JEDEC标准\ JESD22-B111A.pdf C:\Users\ ATC6100\ Desktop\ JEDEC标准\JESD22-B112B.pdfC:\Users\ATC6100\Desktop\ JEDEC标准\JESD22-B113A.pdfC:\Users\ATC6100\Desktop\JEDEC标准\JESD22-B114A.pdfC:\Users\ATC6100\Desktop\C:\Users\ATC6100\Desktop\JESD22-B117B.pdfC:\Users\ ATC6100\ Desktop\C:\Users\ ATC6100\ Desktop\C:\Users\ ATC6100\ Desktop\。