UFS 8 - UAP – SCSI Commands（3）
UFS 8 - UAP – SCSI Commands（3）
-
- 3.5 READ (6) Command
-
- 3.5.1 Read (6) Command Parameters
- 3.5.2 Read (6) Command Data Transfer
- 3.5.3 Read (6) Command Status Response
- 3.6 READ (10) Command
-
- 3.6.1 Read (10) Command Parameters
- 3.6.2 Read (10) Command Data Transfer
- 3.6.3 Read (10) Command Status Response
- 3.7 READ (16) Command
-
- 3.7.1 Read (16) Command Parameters
- 3.7.2 Read (16) Command Data Transfer
- 3.7.3 Read (16) Command Status Response
UFS 1-UFS架构简介1
UFS 2 -UFS架构简介2
UFS 3 - UFS RPMB
UFS 4 - UFS Boot
UFS 5 - UFS UIC Layer: MIPI M-PHY
UFS 6 - UAP – SCSI Commands（1）
UFS 7 - UAP – SCSI Commands（2）
3.5 READ (6) Command
The READ (6) command (see Table 11.10) requests that the Device Server read from the medium the specified number of logical block(s) and transfer them to the Application Client.
The Command CDB shall be sent in a single COMMAND UPIU.
3.5.1 Read (6) Command Parameters
- LOGICAL BLOCK ADDRESS: Address of first block
- TRANSFER LENGTH: Number of contiguous logical blocks of data that shall be read and transferred. A transfer length of zero specifies that 256 logical blocks shall be read. Any other value specifies the number of logical blocks that shall be read.
3.5.2 Read (6) Command Data Transfer
- The Device Server will read the specified logical block(s) from the medium and transfer them to the Application Client in a series of DATA IN UPIU’s
- The data segment of each DATA IN UPIU shall contain an integer number of logical blocks
- Zero or an incomplete number of DATA IN UPIU’s could be transferred if a read error occurs before the entire data transfer is complete
3.5.3 Read (6) Command Status Response
- Status response will be sent in a single RESPONSE UPIU
- If all requested data is successfully read and transferred, the READ command will terminate with a STATUS response of GOOD
- If the unit is not ready to accept a new command (e.g., still processing previous command) a STATUS response of BUSY will be returned
- Failure can occur for numerous reasons. When the READ command fails a STATUS response of CHECK CONDITION will be returned along with an appropriate SENSE KEY, such as
- ILLEGAL REQUEST (range or CDB errors)
- MEDIUM ERROR (medium failure, ECC, etc.)
- HARDWARE ERROR (hardware failure)
- UNIT ATTENTION (reset, power-on, etc.)
- etc.
3.6 READ (10) Command
The READ (10) command (see Table 11.11) requests that the Device Server read from the medium the specified number of logical block(s) and transfer them to the Application Client.
The Command CDB shall be sent in a single COMMAND UPIU
- The RDPROTECT field is set to zero for UFS.
3.6.1 Read (10) Command Parameters
- DPO = Disable Page Out
“0” = specifies that the retention priority shall be determined by the RETENTION PRIORITY fields in the Caching mode page
“1” = specifies that the device server shall assign the logical blocks accessed by this command the lowest retention priority for being fetched into or retained by the cache. A DPO bit set to one overrides any retention priority specified in the Caching mode page. - FUA: Force Unit Access
‘0’ = The Device Server may read the logical blocks from the cache and/or the medium. ‘1’ = The Device Server shall read the logical blocks from the medium. If a cache contains a more recent version of a logical block, then the device server shall write the logical block to the medium before reading it. - FUA_NV is defined per SBC. Since non-volatile cache support is not currently defined in this standard, the FUA_NV parameter value in the CDB is ignored by the UFS Device Server.
- LOGICAL BLOCK ADDRESS: Address of first block
- TRANSFER LENGTH: Number of contiguous logical blocks of data that shall be read and transferred. A transfer length of zero specifies that no logical blocks will be read. This condition shall not be considered an error.
- GROUP NUMBER: Notifies the Target device that the data linked to a ContextID:
In case the GROUP NUMBER is set to a reserved value, the operation shall fail and a status response of CHECK CONDITION will be returned along with the sense key set to ILLEGAL REQUEST.
3.6.2 Read (10) Command Data Transfer
- The Device Server will read the specified logical block(s) from the medium and transfer them to the Application Client in a series of DATA IN UPIU’s
- The data segment of each DATA IN UPIU shall contain an integer number of logical blocks
- Zero or an incomplete number of DATA IN UPIU’s could be transferred if a read error occurs before the entire data transfer is complete.
3.6.3 Read (10) Command Status Response
- Status response will be sent in a single RESPONSE UPIU
- If all requested data is successfully read and transferred, the READ command will terminate with a STATUS response of GOOD
- If the unit is not ready to accept a new command (e.g., still processing previous command) a STATUS response of BUSY will be returned
- Failure can occur for numerous reasons. When the READ command fails a STATUS response of CHECK CONDITION will be returned along with an appropriate SENSE KEY, such as
- ILLEGAL REQUEST (range or CDB errors)
- MEDIUM ERROR (medium failure, ECC, etc.)
- HARDWARE ERROR (hardware failure)
- UNIT ATTENTION (reset, power-on, etc.)
- etc.
3.7 READ (16) Command
The READ (16) command (see Table 11.12) requests that the Device Server read from the medium the specified number of logical block(s) and transfer them to the Application Client
The Command CDB shall be sent in a single COMMAND UPIU
- The RDPROTECT field is set to zero for UFS.
3.7.1 Read (16) Command Parameters
- DPO = Disable Page Out
“0” = specifies that the retention priority shall be determined by the RETENTION PRIORITY fields in the Caching mode page
“1” = specifies that the device server shall assign the logical blocks accessed by this command the lowest retention priority for being fetched into or retained by the cache. A DPO bit set to one overrides any retention priority specified in the Caching mode page. - FUA: Force Unit Access
‘0’ = The Device Server may read the logical blocks from the cache and/or the medium. ‘1’ = The Device Server shall read the logical blocks from the medium. If a cache contains a more recent version of a logical block, then the device server shall write the logical block to the medium before reading it. - FUA_NV is defined per SBC. Since non-volatile cache support is not currently defined in this standard, the FUA_NV parameter value in the CDB is ignored by the UFS Device Server.
- LOGICAL BLOCK ADDRESS: Address of first block
- TRANSFER LENGTH: Number of contiguous logical blocks of data that shall be read and transferred. A transfer length of zero specifies that no logical blocks will be read. This condition shall not be considered an error.
- GROUP NUMBER: See Read (10) Command.
3.7.2 Read (16) Command Data Transfer
- The Device Server will read the specified logical block(s) from the medium and transfer them to the Application Client in a series of DATA IN UPIU’s
- The data segment of each DATA IN UPIU shall contain an integer number of logical blocks
- Zero or an incomplete number of DATA IN UPIU’s could be transferred if a read error occurs before the entire data transfer is complete
3.7.3 Read (16) Command Status Response
- Status response will be sent in a single RESPONSE UPIU
- If all requested data is successfully read and transferred, the READ command will terminate with a STATUS response of GOOD
- If the unit is not ready to accept a new command (e.g., still processing previous command) a STATUS response of BUSY will be returned
- Failure can occur for numerous reasons. When the READ command fails a STATUS response of CHECK CONDITION will be returned along with an appropriate SENSE KEY, such as
- ILLEGAL REQUEST (range or CDB errors)
- MEDIUM ERROR (medium failure, ECC, etc.)
- HARDWARE ERROR (hardware failure)
- UNIT ATTENTION (reset, power-on, etc.)
- etc.