12 Appendix: Error Codes
(Ask a Question)The system controller executes system service requests from the design. When a service is completed, a status code is returned to the user application. This status code can be 0 (success) or an 8-bit error code. The following table lists the error codes.
| Error Code | Description | Explanation |
|---|---|---|
| 1 | Validator or hash chaining mismatch | Bitstream is constructed incorrectly, or a wrong security key is used. |
| 2 | Unexpected data received | Additional data is received after the End of the Bitstream (EOB) component. |
| 3 | Invalid/corrupt encryption key | Requested key mode is disabled, or the key could not be read or reconstructed. |
| 4 | Invalid component header | Bitstream contains invalid component data. |
| 5 | Back level not satisfied | Bitstream version is older than that of the current back level in the device. |
| 6 | Illegal bitstream mode | Requested bitstream mode is disabled by user security. |
| 7 | DSN binding mismatch | Bitstream is rejected because the Device Serial Number (DSN) in the bitstream does not match the DSN on the device. |
| 8 | Illegal component sequence | Bitstream ends in the ERR state, meaning it is an illegal bitstream. Every bitstream begins in the BEGIN state, but only a legal bitstream ends in the END state. |
| 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 of the target device. |
| 11 | Unsupported bitstream protocol version (regeneration required) | Bitstream is rejected because of an attempt made by the old device to decode the new version of bitstream or by the new device to decode the old version of the bitstream. |
| 12 | Verify not permitted on this bitstream | When the device programs the bitstream with encryption keys, it is not possible to use the bitstream later to verify the device contents because the device refers to the modified encryption keys. |
| 13 | Invalid device certificate | Device certificate is missing or invalid. |
| 14 | Invalid DIB | Device integrity bits are invalid. |
| 21 | Device not in SPI master mode | Bitstream is executed in IAP mode, but the device is not configured as SPI master. |
| 22 | No valid images found (auto update) | Bitstream is executed through auto update mode, but no valid image pointers are found. |
| 23 | No valid images found (IAP) | Bitstream is executed through IAP via index mode, but no valid image pointers are found. |
| 24 | Programmed design version newer than auto update image | Bitstream is executed through auto update mode, and the design version is the latest. |
| 25 | Reserved | |
| 26 | Selected image invalid and no recovery performed because the device is running a valid design | Bitstream is executed through auto update or IAP mode, and the selected image is invalid. |
| 27 | Selected recovery image failed to program | Bitstream is executed through auto update or IAP mode, and the selected recovery image failed to program the device. |
| 127 | Abort | A non-bitstream instruction is executed during bitstream loading. |
| 128 | NVMVERIFY | Fabric/security key segment verification failed. |
| 129 | PROTECTED | The device non-volatile memory cannot be modified because of device security settings. |
| 130 | NOTENA | Programming mode is not enabled. |
| 131 | SNVMVERIFY | The sNVM verify operation failed. |
| 132 | SYSTEM | An error occurred in the system hardware (PUF or DRBG). |
| 133 | BADCOMPONENT | An error is detected in a component’s payload. |
| 134 | HVPROGERR | The HV programming subsystem has failed. |
| 135 | HVSTATE | The HV programming subsystem is in an unexpected state because of an error. |