Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Why is “Specification Revision Field” of a “GoodCRC” message not consistent with the received Message Header?
The “GOODCRC” message of the “Specification Revision Field” follows the below definition from the USB-PD 3.0 Specification. The details are documented in the USB-PD 3.0 Version 1.2 Specification as follows:
The 2-bit Specification Revision field of a GoodCRC Message does not carry any meaning and Shall be considered as don’t care by the recipient of the Message. The sender of a GoodCRC Message Shall set the Specification Revision field to 01b when responding to a Message that contains 01b in the Specification Revision field of the Message Header. The sender of a GoodCRC Message May set the Specification Revision field to 00b or 01b or 10b when responding to a Message that contains 10b in the Specification Revision field of the Message Header.
Since it is clearly documented in the USB-PD 3.0 specification that the GoodCRC message does not carry any meaning, the GoodCRC message may or may not be consistent with the message header. Since this message is also supposed to be disregarded by the recipient, end customers should not treat such inconsistency as a CCGx firmware issue.