SPMU447 June 2026 CC2755P20
Because of the feature known as debug persistence, once the SACI_CMD_DEBUG_SUBMIT_CHALLENGE_RESP command has returned with SUCCESS, the device persists the successful debug authentication. This means that a simple reset of the device does not clear the authentication of a current debug session. There are three ways to clear the debug persistence:
None.
| Word | Bits | Field | Value | Decsription |
|---|---|---|---|---|
0 | 7:0 | cmdId | 0x20 | Command ID |
15:8 | respSeqNumber | User defined | Optional response sequence number, included in the response header | |
31:16 | reserved0 | 0x0000 | Reserved |
| Words | Bits | Field | Value | Description |
|---|---|---|---|---|
0 | 7:0 | cmdId | 0x20 | Command ID, copied from the first command parameter word |
15:8 | respSeqNumber | User defined | Optional sequence number, copied from the first command parameter word | |
23:16 | result | SUCCESS | Command result | |
31:24 | dataWordCount | 0 | Size of additional response data, in number of 32-bit words |
These checks are performed before command execution, in the indicated order: