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

需积分: 49 97 浏览量更新于2024-07-15 1 收藏 4.62MB PDF 举报

"JESD220C-2_2-ufs v2.2.pdf" 是一份关于 Universal Flash Storage (UFS) 协议的详细规范文档，版本为2.2，由JEDEC（固态技术协会）发布，旨在提供UFS 2.2版本的技术细节和要求。 UFS（Universal Flash Storage）是一种高速、低功耗的存储接口标准，主要用于移动设备，如智能手机和平板电脑。这个标准是为了解决日益增长的数据存储需求和对性能的提升，同时保持较低的能耗，以延长设备的电池寿命。在UFS 2.2版本中，主要包含了以下关键知识点： 1. **双通道传输**：UFS支持双通道数据传输，相比于单通道，可以显著提高数据读写速度，从而提升设备的整体性能。 2. **HS-G3 PHY层**：HS-G3 (High Speed Gear 3) 物理层是UFS 2.2中的一个重要升级，它提供了更高的传输速率，通常超过11.6 Gbps，使得读写速度达到GB/s级别。 3. **命令队列（Command Queue）**：UFS 2.2引入了命令队列功能，允许设备同时处理多个I/O请求，提高了并发处理能力，降低了延迟。 4. **电源管理优化**：新版本对电源管理进行了优化，包括更精细的电源状态转换和低功耗模式，以适应不同工作场景，进一步节省能源。 5. **增强的错误校验**：UFS 2.2可能包含了更先进的错误检测和纠正机制，确保数据的完整性和可靠性。 6. **兼容性与互操作性**：标准的更新旨在确保不同厂商生产的UFS设备能够无缝配合，减少用户在选择和使用过程中的困扰。 7. **安全特性**：UFS 2.2可能会包含更多的安全特性，例如加密和安全启动，以保护用户数据和设备免受恶意攻击。 8. **标准化测试**：文档将详细描述如何进行符合性测试和验证，以确保设备符合UFS 2.2的标准。这份文档对于设计、开发、测试以及理解和使用UFS 2.2存储设备的工程师来说是必不可少的参考材料，它提供了全面的技术指南和要求，有助于确保产品与标准的兼容性和一致性。同时，对于那些想要深入理解现代移动设备存储技术的人员来说，也是一个宝贵的资源。

JEDEC Standard No. 220C-2.2

-xii-

Downloaded by xiong wanjun (xiongwanjun@chinatsp.com) on Oct 11, 2020, 7:43 pm PDT

chinatsp

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.

Downloaded by xiong wanjun (xiongwanjun@chinatsp.com) on Oct 11, 2020, 7:43 pm PDT

chinatsp

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.

Downloaded by xiong wanjun (xiongwanjun@chinatsp.com) on Oct 11, 2020, 7:43 pm PDT

chinatsp

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).

Downloaded by xiong wanjun (xiongwanjun@chinatsp.com) on Oct 11, 2020, 7:43 pm PDT

chinatsp

剩余395页未读，继续阅读

wanjx1234

粉丝: 1
资源: 10

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

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

UFS V2.1-JESD220C

UFS2.2规范规范规范规范

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

JESD220C-2_2 UFS 2.2

Universal Flash Storage (UFS) Version 2.2 JESD220C-2-2.pdf

UFS 2.2 标准详解：JEDEC JESD220C-2.2

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

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

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

最新资源