Read Debug Information Service

Fetches debug information on programming, user initialization, device programming cycle count, and In-application programming (IAP) actions. The device programming cycle count increases for device PROGRAM and ERASE actions. The following table lists the debug information reported by this service.

Table 1. Read Debug Information Service Request
System Service Descriptor Bit Field Value Description
15:7 MBOXADDR[10:2] Mailbox address. See Table 2.
6:0 06H Read Debug service command.
Table 2. Debug Information
Size (Bytes) Byte Offset Parameter Description
32 0 Reserved Reserved
4 32 TOOL_INFO Reflects the tool specific data passed in during programming. IAP sets this field to 0.
1 36 TOOL_TYPE Tool type used to program device:
  • 1: JTAG
  • 2: IAP
  • 3: SPI_SLAVE
4 37 Reserved Reserved
1 41 FRAME_ERRORCODE An error has occurred during bitstream frame processing and the error is identified by the FRAME_ERRORCODE field. See Table 5.
6 42 Reserved Reserved
1 48 UIC_STATUS Device and design initialization Status.
  • 0: Successful completion.
  • Others: Device and design initialization failed.
11 49 Reserved Reserved
4 60 CYCLECOUNT Programming cycle count. CYCLECOUNT gets incremented for both Programming and Erase operations as ERASE is internally a Programming action.
1 64 IAP ERRORCODE IAP Error Information. Returns ERRORCODE 21-27, see Table 5.
7 65 Reserved Reserved
4 72 IAP Location SPI address that was last run in IAP
4 76 SYSCTRL_STATUS System Controller status
4 80 RESET_REASON When a reset occurs, a bit is set in the reset reason register that allows the source of the reset to be determined post reset. Multiple bits are set in the reset reason register when a reset occurs. See Table 4 for bit position of the bits set in the RESET_REASON register to find out the source of reset.
Table 3. SYSCTRL_STATUS
Field Name Width (bits) Field Offset
SRAM_INIT_COMPLETE 1 0
UIC_SCRIPT_COMPLETE 1 8
US_RAM_INIT_DONE 1 16
RESET_REASON 5 24
Table 4. Reset Reason
Reset Reason Description RESET_REASON[4:0]
POR Master POR asserted. 0
POR1P05 POR asserted due to the 1P05 supply is not at correct level. 1
POR1P8 POR asserted due to the 1P8 supply is not at correct level. 2
POR2P5 POR asserted due to the 2P5 supply is not at correct level. 3
Reserved Reserved. 4
DEVRST Indicates that the device is reset by the DEVRSTN pin. 5
AVIONICS Indicates that the device has exited system controller suspend mode. 6
WATCHDOG Indicates that the System Controller's watchdog had triggered the reset. 7
SYSCON_SYSRESET Indicates that the system controller requested the system reset. 8
MESH Indicates that the security mesh triggered the reset. 9
SECURITY_LOCKS Indicates that the security locks system detected a security issue and reset the system. 10
CLOCK_GLITCH Indicates that the clock glitch system detected an issue and reset the system. 11
VIRGIN Indicates that the virgin security system detected an issue and reset the system. 12
TAMPER_RESPONSE Indicates that the user asserted the system reset tamper response. 13
Table 5. ERRORCODE
ERRORCODE Description Additional Notes
0 No error
1 Bitstream authentication failed Invalid bitstream or wrong key used.
2 Unexpected data received Additional data is received after end of bitstream component.
3 Invalid/corrupt encryption key The requested key mode is disabled or the key could not be read/reconstructed.
4 Invalid component header Invalid bitstream
5 Back level not satisfied Bitstream version is older than that of the current back level value set in the device.
6 Illegal bitstream key mode Bitstream key mode is not initialized or bitstream key mode is disabled by user security.
7 DSN binding mismatch Bitstream is rejected because DSN in the bitstream does not match with the DSN present in the device. A bitstream can be bound to device's unique DSN such that only a specific device can be programmed with that bitstream.
8 Illegal component sequence Incorrect bitstream
9 Insufficient device capabilities Bitstream is rejected because the capabilities specified in the bitstream do not match the target device's capabilities.
10 Incorrect DEVICEID Bitstream is rejected because an attempt by the DEVICEID specified in the bitstream does not match the part identification field (for example, MPF300, MPF500 and so on) of the target device.
11 Unsupported bitstream protocol version (bitstream regeneration required) Bitstream is rejected because of an attempt made by the old version of a device to decode a bitstream created in new format or by the new version of a device to decode a bitstream created in old format.
12 Verify not permitted on this bitstream Verify programming action is disabled in the bitstream.
13 Invalid Device Certificate Device certificate is invalid or not present.
14 Invalid DIB Device integrity bits (DIB) are invalid.
21 Device not in SPI Master Mode Error may occur only when bitstream is executed through IAP mode. The System Controller SPI controller is not configured in master mode.
22 No valid images found Error may occur when bitstream is executed through Auto Update mode. Occurs when No valid image pointers are found.
23 No valid images found Error may occur when bitstream is executed through IAP mode via Index Mode. Occurs when No valid image pointers are found.
24 Programmed design version is the same as the Auto Update image found Error may occur when bitstream is executed through Auto Update mode.
25 Reserved

Reserved

26 Selected image was invalid and no recovery was performed due to valid design in device. Error may occur only when bitstream is executed through Auto Update or IAP mode. Error could also occur due to BACKLEVEL protection.
27 Selected and Recovery image failed to program Error may occur only when bitstream is executed through Auto Update or IAP mode.
127 Abort Non-bitstream instruction is executed during bitstream loading.
128 NVMVERIFY Fabric or security segment verification failed.
129 PROTECTED Device security is prevented modification of non-volatile memory.
130 NOTENA Programming mode not enabled
131 PNVMVERIFY pNVM verify operation failed
132 SYSTEM System hardware error (PUF or DRBG)
133 BADCOMPONENT An internal error was detected in a bitstream component payload.
134 HVPROGERR Failure in programming subsystem.
135 HVSTATE Error in the programming subsystem.