SD Specifications Part 1 UHS-II Simplified Addendum - SD Association

More documents

Recommendations

Info

UHS-II Simplified Addendum Version 1.01©Copyright 2010-2013 SD Card Association7. SD-TRAN SpecificationSD-TRAN rides over CM-TRAN and acts as bridge between Legacy SD protocol and UHS-II commonprotocol for SD-compatibility. This chapter presents encapsulated SD packet formats, transactionsequences, initialization for SD-TRAN, state machine, error handling and timing rules. These are basedon CM-TRAN specification, but SD-memory is applied to some specific rules described in this chapter.In this case, the specific rules in SD-TRAN are effective instead of those in CM-TRAN.In this section, UHS-II specifications for SD-memory are described, not included for SDIO.7.1 SD-TRAN OverviewTransactionApplicationspecific layerCM-TRAN(Common layer)SD-TRAN(SD specific)Tran ManagementTPSMTBSMTSSMSD CMD/RES/DATSD Card RegisterSD State MachineProtocol Bridge (SDCM)Transactions (Data, Control)EnumerationConfigurationCommon Packets (DCMD, CCMD, RES, DATA)**-TRAN(extensible TRAN for future use)Extended Part (2nd gen or later)CMD QueuingRelaxed OrderingID based Mux/DemuxFigure 7-1 : SD-TRAN OverviewThe features of SD-TRAN are shown below; Preserving Legacy SD infrastructures (CMD, RES, status, errors and etc.) Bridging between Legacy SD protocol (e.g. Host/Device register interface) and UHS-II commonprotocol (CM-TRAN)7.1.1 Packet Types and Format OverviewEncapsulated SD packets are defined in SD-TRAN in order to ensure Legacy SD compatibility andpreserve Legacy SD infrastructures.Conceptual diagram of SD-encapsulation is shown in Figure 7-2.UHS-II Packet(abstract)Header Argument PayloadSD CMD / RES / DATALegacy SD CMD/RES/DATA areencapsulated in Argument and/orPayload field of UHS-II packetFigure 7-2 : Conceptual Diagram of SD-encapsulationSD-encapsulation formats in each types of TLP are shown in Figure 7-3.76
UHS-II Simplified Addendum Version 1.01©Copyright 2010-2013 SD Card AssociationCCMDHeaderR/WArgumentPLEN, I/O AddressPayload(only write CCMD)(Rsvd)CmdIndexPLENArgumentCRC7SD Control Command (e.g. CMD8, 12, etc.)DCMDHeaderR/WArgumentTMODERsvdExtended ArgumentData AddressTLEN(Rsvd)(TMODE)CmdIndexArgument (data address)TLEN (In case of CMD18, 25)CRC7SD Data Command (e.g. CMD18, 25, etc.)RESHeaderNACKArgumentCMD_ECHO_BACKPayload(only read CCMD)(Other than R2)(NACK)(CMD_ECHO_BACK)PLENRes ContentCRC7(R2)(NACK)(CMD_ECHO_BACK)Res Content PLEN incl. internal CRC7SD ResponseDATAHeaderPayloadSD Data Block (typ. 512B)CRC16: Packet Type: Existence depends on transaction typeFigure 7-3 : Encapsulation of Legacy SD FormatBasically, CRC7 or CRC16 for Legacy SD are not overridden in SD-encapsulation format because allTLPs are added CRC16 in Link Layer.Details are described in next section.7.1.2 Registers for Legacy SDRegisters for Legacy SD such as CID or CSD can be accessed only by SD encapsulated CMD. Forexample, when Host wants to get CID, Host sends an encapsulated CMD2 (ALL_SEND_CID).7.2 SD-TRAN Protocol7.2.1 Packet Format DetailsIn this section, the bracketed number in the figures denotes the bit position in Legacy SD command orresponse format. Note that broadcast packet is not permitted in SD-TRAN.7.2.1.1 CCMDFigure 7-4 illustrates CCMD on SD-TRAN.77
Page 4:
UHS-II Simplified Addendum Version
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39: UHS-II Simplified Addendum Version
Page 60: UHS-II Simplified Addendum Version
show all

SD Specifications Part 1 UHS-II Simplified Addendum - SD Association

Create successful ePaper yourself

Delete template?

Save as template?