UFS 2.2 标准详解：JEDEC JESD220C-2.2

需积分: 5 143 浏览量更新于2024-06-17 收藏 4.53MB PDF 举报

"Universal Flash Storage (UFS) Version 2.2 JESD220C-2-2.pdf 是一个由JEDEC固态技术协会发布的标准文档，详细阐述了UFS（通用闪存存储）协议的第2.2版。此版本是对2016年3月发布的JESD220C 2.1版的更新，旨在促进闪存存储设备的互操作性和性能提升。" Universal Flash Storage (UFS)是一种高速、低功耗的非易失性存储接口标准，广泛应用于移动设备如智能手机、平板电脑以及高端嵌入式系统。UFS 2.2标准是这一技术的重要里程碑，它带来了诸多改进和新特性，以满足不断增长的数据传输速率需求和设备性能优化。 1. **速度提升**：UFS 2.2引入了更高效的数据传输协议，如增强的Host Performance Booster (eHPB) 功能，允许主机系统在读写操作之间快速切换，从而提高整体性能。此外，它还支持更高的数据传输速度，比如理论上的最大接口速度可达到11.6 Gbps，远超UFS 2.1的理论上限。 2. **能效优化**：UFS 2.2标准关注设备的能源效率，通过改进电源管理算法和减少不必要的电源转换，降低了功耗，这对于电池寿命有限的移动设备至关重要。 3. **错误校正与可靠性**：为了确保数据的完整性，UFS 2.2增加了更强的错误校正码(ECC)，如增强型Error Correction Code (eECC)，能够更有效地检测和纠正存储错误，提高了存储器的可靠性。 4. **多队列支持**：UFS 2.2支持多个I/O队列，这允许并发读写操作，进一步提升了系统吞吐量和响应时间，尤其是在处理大量数据的场景下。 5. **兼容性和互操作性**：作为JEDEC的标准，UFS 2.2确保不同制造商的设备能够无缝协作，减少了用户在选择和使用产品时的困扰，同时也促进了整个行业的创新和发展。 6. **安全性**：标准可能包括针对数据保护和安全性的增强措施，例如加密功能，以防止未经授权的访问和数据泄露。 7. **标准化过程**：JEDEC标准的制定遵循严格的流程，包括董事局的审查、法律顾问的批准，旨在消除制造商和消费者之间的误解，促进产品的互换性，并帮助消费者快速准确地选择合适的产品。 UFS 2.2 JESD220C-2-2标准文档是移动设备和嵌入式系统设计者、开发者以及制造商的重要参考，它定义了新一代高速、低功耗闪存存储接口的规范，推动了存储技术的持续进步。

JEDEC Standard No. 220C-2.2

-xii-

JEDEC Standard No. 220C-2.2

Page 1

UNIVERSAL FLASH STORAGE (UFS), 2.2

(From JEDEC Board Ballot JCB-20-27, formulated under the cognizance of the JC-64.1 Subcommittee

on Electrical Specifications and Command Protocols, Item 138.88)

1 SCOPE

This standard specifies the characteristics of the UFS electrical interface and the memory device. Such

characteristics include (among others) low power consumption, high data throughput, low

electromagnetic interference and optimization for mass memory subsystem efficiency. The UFS electrical

interface is based on an advanced differential interface by MIPI M-PHY specification which together with

the MIPI UniPro specification forms the interconnect of the UFS interface. The architectural model is

referencing the INCITS T10 (SCSI) SAM standard and the command protocol is based on INCITS T10

(SCSI) SPC and SBC standards.

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 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 indicated. For

undated references, the latest edition of the normative document referred to applies.

[MIPI-M-PHY], MIPI Alliance Specification for M-PHY

, Version 3.00.00

[MIPI-UniPro], MIPI Alliance Specification for Unified Protocol (UniPro

), Version 1.6.00

[MIPI-DDB], MIPI Alliance Specification for Device Descriptor Block (DDB), Version 1.0

[SAM], INCITS T10 draft standard: SCSI Architecture Model – 5 (SAM–5), Revision 05, 19 May 2010

[SPC], INCITS T10 draft standard: SCSI Primary Commands – 4 (SPC-4), Revision 27, 11 October 2010

[SBC], INCITS T10 draft standard: SCSI Block Commands – 3 (SBC–3), Revision 24, 05 August 2010

[JESD8-12A], 1.2 V +/- 0.1V (Normal Range) and 0.8 - 1.3 V (Wide Range) Power Supply Voltage and

Interface Standard for Nonterminated Digital Integrated Circuits

[HBM-MM], JEDEC Recommended ESD Target Levels for HBM/MM Qualification, JEP155A.01,

March 2012

[CDM], JEDEC Recommended ESD-CDM Target Levels, JEP157, October 2009

[HMAC-SHA], Eastlake, D. and T. Hansen, US Secure Hash Algorithms (SHA and HMAC-SHA), RFC

4634, July 2006.

JEDEC Standard No. 220C-2.2

Page 2

3 TERMS AND DEFINITIONS

For the purposes of this standard, the terms and definitions given in the document included in clause 2,

Normative Reference, and the following apply.

Application Client: An entity that is the source of SCSI commands and task management function

requests in the host.

Byte: An 8‐bit data value with most significant bit labeled as bit 7 and least significant bit as bit 0.

Command Descriptor Block: The structure used to communicate commands from an application client

to a device server. A CDB may have a fixed length of up to 16 bytes or a variable length of between 12

and 260 bytes.

Device ID: The bus address of a UFS device.

Device Server: An entity in the device that processes SCSI commands and task management functions.

Doubleword: A 32‐bit data value with most significant bit labeled as bit 31 and least significant bit as bit

Dword: 32‐bit data value, a Doubleword.

Gigabyte: 1,073,741,824 or 2

bytes.

Host: An entity or a device with the characteristics of a primary computing device that includes one or

more SCSI initiator devices.

Initiator device: Within a transaction, the originator of a SCSI command request message to a target

device.

Kilobyte: 1024 or 2

bytes.

Logical Unit: A logical unit is an internal entity of a bus device that performs a certain function or

addresses a particular space or configuration within a bus device.

Logical Unit Number: A numeric value that identifies a logical unit within a device

Megabyte: 1,048,576 or 2

bytes.

Quadword: A 64‐bit data value with most significant bit labeled as bit 63 and least significant bit as 0.

Segment: A specified number of sequentially addressed bytes representing a data structure or section of

a data structure.

Segment ID: A 16‐bit value that represents an index into a table or an address of a segment descriptor or

simply an absolute value that is an element of an absolute address

SCSI Request Block: A data packet that contains a multi‐byte SCSI command and additional contextual

information needed to carry out the command operation. A SCSI Request Block is built by the host and is

targeted at a particular bus device.

Target device: Within a transaction, the recipient of a SCSI command request message from an initiator

device.

Task: A task is a SCSI command which includes all transactions to complete all data transfers and a

status response that will satisfy the requirements of the requested services of the command.

Transaction: A UFS primitive action which results in transmission of serial data packets between a

target device and initiator device.

JEDEC Standard No. 220C-2.2

Page 4

3.1 Acronyms (cont’d)

SBC

SCSI Block Commands

SID

Segment ID

SDU

Service Data Unit

SPC

SCSI Primary Commands

Terabyte

T_PDU

MIPI Unipro Protocol Data Unit

T_SDU

MIPI Unipro protocol Service Data Unit

UFS

Universal Flash Storage

UMPC

Ultra-Mobile PC

UniPro

Unified Protocol

UPIU

UFS Protocol Information Unit

UTP

UFS Transport Protocol

3.2 Conventions

This standard 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 in 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).

剩余395页未读，继续阅读

ByronYao

粉丝: 1
资源: 31

UFS 2.2 标准详解：JEDEC JESD220C-2.2

JEDEC JESD220C-2.2：2020 Universal Flash Storage (UFS) Version 2.

JEDEC JESD220C-2.2：2020 Universal Flash Storage (UFS) Version 2.2 - 完整英文电子版（392页） .pdf

JESD220C(UFS2.1 SPEC).pdf

UFS2.2 SPEC--JESD220C-2_2.pdf

JESD220C-2_2-ufs v2.2.pdf

2020版UFS 2.2标准发布 - JEDEC JESD220C-2.2详解

JESD220C-2_2 UFS 2.2

UFS版2.2详解：JEDEC JESD220C-2_2标准文档

JEDEC JESD220D：2018 Universal Flash Storage (UFS) Version 3.0 -

JEDEC JESD220E：2020 Universal Flash Storage (UFS) Version 3.1 -

最新资源