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 Association5.2.3 Header for UHS-II PacketFigure 5-2 illustrates header structure for UHS-II packet that is compliant to UHS-II Addendum Version1.00. First, Node ID whose range is from 0 to 15 denotes a value to identify the individual Hosts andDevices. Node ID = 0 is set aside for Host. For Devices, number 15 is set as the initial value for Node IDafter I/F power cycle or FULL_RESET, and one of numbers from 1 to 15 is assigned to each Device byEnumeration process described in Section 0. Note that Node ID of Boot Device is temporarily assignedfor Boot Code Loading at first, then one of numbers from 1 to 15 is assigned by Enumeration.Considering future extension, header format is allowed to be changed linked to LINK/TRAN MajorRevision in CFG_REG (refer to Table 6-9).BitByte07 6 5 4 3 2 1 0NP TYP (Packet Type)DID (Destination ID)1 SID (Source ID)RsvdTID (Transaction ID)Figure 5-2 : Header FormatUHS-II Packet Header shall be composed of the following fields; NP (Native Packet): Indicator whether the packet follows native protocol or not 0: not native protocol (application specific protocol) 1: native protocol NP field in MSG shall be set to '1'. (MSG packet transaction is defined on native protocol.) TYP[2:0] (Packet Type): Packet type described in Table 5-3. DID[3:0] (Destination ID): Node ID of destination Device or Host. SID[3:0] (Source ID): Node ID of source Device or Host. TID[2:0] (Transaction ID): Identification number of outstanding transactions The TID field is defined in order to manage outstanding transactions for multiplecommand execution. (Details of multiple command execution will be defined in the futurespecification.) Rsvd (Reserved): Reserved bits. Initiator shall set them to '0', and receiver shall ignore them.TYP [2:0] Packet Type Description Note000b CCMD Control Command packet TLP001b DCMD Data Command packet TLP010b RES Response packet TLP011b DATA Data payload packet TLP111b MSG Message packet Handled in LINKOthers Reserved Reserved --Table 5-3 : Packet Type Encodings and DescriptionsDID and SID are used as routing information. If SID = DID, the packet is handled as broadcast. ForUHS-II Addendum Version 1.00, broadcast packet is applicable only for CCMD. Details of broadcastCCMD are described in Section 6.2.2.3.Basically, Host or Device processes a packet with the same DID as its own Node ID. In case ofreceiving a packet with different DID from own Node ID, Host or Device does not process it exceptbroadcast packet and bypasses it to the next Host or Device on the bus. If Host or Device receivesbroadcast packet (SID = DID), it shall process even when DID is not equal to its own Node ID, andtransmit to the next Host or Device.34
UHS-II Simplified Addendum Version 1.01©Copyright 2010-2013 SD Card Association5.2.4 Message Packet (MSG)5.2.4.1 OverviewMessage Packet (MSG) is introduced to realize flow control, error or interrupt handling instead of hardwiredsignals.Figure 5-3 illustrates a structure of MSG packet. Note that NP in Header shall be set to 1.BitByte017 6 5 4 3 2 1 0Header(NP=1, Packet Type = MSG)2 CTG RsvdIDX3CODEHeaderArgumentFigure 5-3 : MSG Format CTG[2:0] (Message Category): indicates category of MSG. Refer to Table 5-4 for more details. IDX[3:0] (Message Index): indicates message Index related to CTG. Refer to Table 5-4 for moredetails. CODE[7:0] (Message Code): indicates code to define message detail. Rsvd (Reserved): Reserved bits. Initiator shall set them to '0', and receiver shall ignore them.CTG IDX CODE DescriptionBits Name Bits Name000b LMSG(See Note0000b FCREQ Refer to Table5-5Flow Control Request from initiator ofDATA(1)) 0001b FCRDY Refer to Table Flow Control Ready from receiver of DATA5-50010b STAT Refer to Table5-6Status of DATA Burst transfer notified fromreceiver of DATAothers Reserved Reserved Reserved011b INT all Reserved Reserved Reserved for interrupt100b AMSG See Note (2) Application specific message. It dependson application defined in CFG_REG.Others Reserved all Reserved Reserved ReservedNote:(1) LMSG is handled within LINK.Table 5-4 : Detailed Definition of MSGAlso refer to Section 6.2.2.8 for operating reserved bits in the packet.35
Page 4: UHS-II Simplified Addendum Version
Page 10 and 11: UHS-II Simplified Addendum Version
Page 60: UHS-II Simplified Addendum Version
Page 97 and 98:
UHS-II Simplified Addendum Version
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113:
show all

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

Create successful ePaper yourself

Delete template?

Save as template?