SD Specifications Part 1 UHS-II Simplified Addendum - SD Association
SD Specifications Part 1 UHS-II Simplified Addendum - SD Association
SD Specifications Part 1 UHS-II Simplified Addendum - SD Association
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>UHS</strong>-<strong>II</strong> <strong>Simplified</strong> <strong>Addendum</strong> Version 1.01©Copyright 2010-2013 <strong>SD</strong> Card <strong>Association</strong>6.2.2.6 RES (NACK = 1)Figure 6-13 illustrates RES (NACK = 1) structure.BitByte01237 6 5 4 3 2 1 0NACK=1Header(NP=1, Packet Type = RES)ECODERsvdRsvdHeaderArgumentFigure 6-13 : RES (NACK = 1) Format NACK (Negative Acknowledgement): Indicator whether the corresponding CMD is accepted ornot. NACK = 1 means the corresponding CMD is rejected. In the case of NACK = 1 (CMD is rejected), the requested operation is not in execution(an error has occurred in the corresponding CMD). ECODE[2:0] (Error Code): Error code to represent error descriptions (refer to Table 6-4). Rsvd (Reserved): Reserved bits. Initiator shall set them to '0', and receiver shall ignore them.Table 6-4 shows the error descriptions represented by ECODE. If CMD includes multiple errors, RESwith NACK = 1 is generated with the error whose ECODE value is the smallest. For example, whensome command is issued at improper state with illegal argument (e.g. illegal address), the ECODE of itsRES with NACK = 1 is COND_ERR.ECODEDescriptionValueName001b COND_ERR Command is issued in any improper statesdefined in all layers in this specification.010b ARG_ERR At least one of parameters in any of Argumentfield, Extended Argument field, or Payload field isimproper in the CMD.011b GEN_ERR Other errors not belonging to the errors above.others Reserved ReservedTable 6-4 : Error Categories and Descriptions6.2.2.7 DATAFigure 6-14 illustrates a basic DATA structure.53