JEDEC JESD220-2-2016 Universal Flash Storage (UFS) Card Extension Version 1 0.pdf

《JEDEC JESD220-2-2016 Universal Flash Storage (UFS) Card Extension Version 1 0.pdf》由会员分享，可在线阅读，更多相关《JEDEC JESD220-2-2016 Universal Flash Storage (UFS) Card Extension Version 1 0.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、JEDEC STANDARD Universal Flash Storage (UFS) Card Extension Version 1.0 JESD220-2 MARCH 2016 JEDEC SOLID STATE TECHNOLOGY ASSOCIATION NOTICE JEDEC standards and publications contain material that has been prepared, reviewed, and approved through the JEDEC Board of Directors level and subsequently re

2、viewed and approved by the JEDEC legal counsel. JEDEC standards and publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting

3、 and obtaining with minimum delay the proper product for use by those other than JEDEC members, whether the standard is to be used either domestically or internationally. JEDEC standards and publications are adopted without regard to whether or not their adoption may involve patents or articles, mat

4、erials, 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 or publications. The information included in JEDEC standards and publications represents a sound approach to product specif

5、ication 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 standard may b

6、e made unless all requirements stated in the 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

7、 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

8、 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 www.jedec.org under Standards and Documents for alternative contact i

9、nformation. Published by JEDEC Solid State Technology Association 2016 3103 North 10th Street Suite 240 South Arlington, VA 22201-2107 This 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 fo

10、r or resell the resulting material. PRICE: Contact JEDEC Printed in the U.S.A. All rights reserved PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by JEDEC and may not be reproduced without permission. For information, contact: JEDEC Solid State Technology Association 3103 North 10th Stre

11、et Suite 240 South Arlington, VA 22201-2107 or refer to www.jedec.org under Standards-Documents/Copyright Information. JEDEC Standard No. 220-2 -i- UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0 Contents Page Foreword i Introduction i 1 Scope 1 2 Normative Reference 1 3 Terms, and definit

12、ions 1 3.1 Acronyms 1 3.2 Terms and definitions 2 3.3 Keywords 2 3.4 Abbreviations 3 3.5 Conventions 3 4 Introduction 4 4.1 Overview 4 4.2 Functional Features 4 5 UFS Card System Architecture 5 5.1 Overview 5 5.2 UFS Card Signals 5 6 UFS Card Design 6 7 Feature comParison of embedded UFS and UFS car

13、d 9 8 UFS Card initialization 10 8.1 Initialization Sequence 11 9 Power Consumption 12 Annex A (informative) Host Guideline for UFS Card Detection 13 Figures Figure 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.

14、1 UFS Card Initialization 10 Figure 8.2 UFS Card Initialization Sequence 11 Tables Table 5.1 Signal Name and Definitions 5 Table 7.1 Comparison of embedded UFS and UFS Card 9 JEDEC Standard No. 220-2 -ii- UNIVERSAL FLASH STORAGE (UFS) CARD EXTENSION, VERSION 1.0 Foreword This standard has been prepa

15、red by JEDEC. The purpose of this standard is to define a UFS card specification. This document will be extension of the UFS Standard, JESD220. Introduction The UFS device (embedded/removable) is a universal data storage and communication media. It is designed to cover a wide area of applications as

16、 smart phones, cameras, organizers, PDAs, digital recorders, MP3 players, internet tablets, electronic toys, etc. JEDEC Standard No. 220-2 Page 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

17、on Electrical Specifications and Command Protocols (Item 133.69).) 1 Scope This 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

18、JESD220, UFS, Version 2.0, will be referenced. 2 Normative Reference The 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 ap

19、ply. 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 Specifi

20、cation for M-PHYSM Specification, Version 3.0 MIPI-UniPro, MIPI Alliance Specification for Unified Protocol (UniProSM), Version 1.6 MIPI-DDB, MIPI Alliance Specification for Device Descriptor Block (DDB), Version SAM, SCSI Architecture Model 5 (SAM5), Revision 05, 19 May 2010 SPC, T10 Specification:

21、 SCSI Primary Commands 4 (SPC-4), Revision 27, 11 October 2010 SBC, T10 Specification: SCSI Block Commands 3 (SBC3), Revision 24, 05 August 2010 UFS, JEDEC JESD220B, Universal Flash Storage (UFS), Version 2.0 UFS, JEDEC JEP95, MO-320, UFS Card Form Factor 3 Terms, and definitions For the purpose of

22、this standard, the terms and definitions given in the documents included in section 2 “Normative Reference” and the following apply. 3.1 Acronyms HCI Host Controller Interface UFS Universal Flash Storage MIPI Mobile Industry Processor Interface PWM Pulse Width Modulation RPMB Replay Protected Memory

23、 Block SBC SCSI Block Commands SPC SCSI Primary Commands LUN Logical Unit Number NA Not applicable KB Kilobyte eUFS Embedded Universal Flash Storage JEDEC Standard No. 220-2 Page 2 3 Terms, and definitions (contd) 3.2 Terms and definitions Byte: An 8bit data value with most significant bit labeled a

24、s 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 LUN Host: An addressable device on the UFS bus which is usually the main CPU that hosts the UFS bus 3.3 Keywords Several keywords are used to differentiate levels of r

25、equirements 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 hard

26、ware 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

27、 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 a

28、re 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 objectsbits, bytes, and fieldsor the code values assigned to these objects in cases wh

29、ere 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 re

30、cipient 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 permitte

31、d (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 me

32、ntioning 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 us

33、ed when stating mandatory requirements; will is only used in statements of fact. JEDEC Standard No. 220-2 Page 3 3 Terms, and definitions (contd) 3.4 Abbreviations etc. - And so forth (Latin: et cetera) e.g. - For example (Latin: exempli gratia) i.e. - That is (Latin: id est) 3.5 Conventions UFS spe

34、cification 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 incl

35、uded 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

36、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-A

37、rabic 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

38、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 th

39、e 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 param

40、eter 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-2 Page 4 4 Introduction 4.1 Overview The JESD220 standard already defined some features for UFS card (removable). The UFS c

41、ard uses same protocol as embedded UFS device, but it has few card specific requirements like power consumption. 4.2 Functional Features UFS 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 Multipl

42、e 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 Protect

43、ion Task management operations Power management operations JEDEC Standard No. 220-2 Page 5 5 UFS Card System Architecture 5.1 Overview The 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 embedde

44、d card. 5.2 UFS Card Signals Figure 5.1 shows the conceptual drawing of UFS card. Figure 5.1 UFS Card Block Diagram Table 5.1 Signal Name and Definitions Name Type Description VCC Supply Supply voltage for the memory devices VCCQ2 Supply Supply voltage used typically for the PHY interface and the me

45、mory controller and any other internal low voltage block VSS Supply Ground C/D GND Card Detection Pin REF_CLK Input Input reference clock. When not active, this signal should be pull-down or driven low by the host SoC. Differential input signals into UFS device from the host DIN_T DIN_C Input Downst

46、ream data lane 0. DIN_T is the positive node of the differential signal. Differential output signals from the UFS device to the host DOUT_T DOUT_C Output Upstream data lane 0. DOUT_T is the positive node of the differential signal. C/D JEDEC Standard No. 220-2 Page 6 6 UFS Card Design The UFS card w

47、ill 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 View JEDEC Standard No. 220-2 Page 7 6 UFS Card Design (contd) Figure 6.2 UF

48、S Card Bottom View Pin 1 JEDEC Standard No. 220-2 Page 8 6 UFS Card Design (contd) Figure 6.3 UFS Card Side View JEDEC Standard No. 220-2 Page 9 7 Feature comparison of embedded UFS and UFS card The embedded UFS and UFS card follow the same protocol. But they will be used in different environment, t

49、he 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. Table 7.1 Comparison of embedded UFS and UFS Card Category Item eUFS 2.0 UFS card v1.0 General Supported PWM Gears G1, G2, G3, G4 (Mandatory) G5, G6, G7 (optional) G1 Only (PWM shall be able to be operated without reference clock) Supported HS Gears G1,G2,G3 (optional) HS-Gear3, HS-Gear2 (optional) Interface Power Supplies VCC