Trusted
225
edits
Changes
Add more bootrom error codes, change complement representation to negative sign instead, and reword errors to be more understandable
|-
|-
| 0x00
| 0x00
| Success
| Device was not considered to be loaded.
Can also indicate success, but not necessarily when seeing the blue bootrom error screen.
|-
|-
| 0xEE(~17)
| 0xFF(-1)
| NCSD header validation function failed: NCSD magicnum is invalid or RSA verification failed.
| Partition skipped due to it not being a FIRM partition (partition fs type isn't 0x3 and partition fs crypt-type isn't 0x2).
|-
|-
| 0xDE(~33)
| 0xFE(-2)
| FIRM header validation function failed: FIRM magicnum is invalid or RSA verification failed.
| Device initialization failed due to it missing or malfunctioning
|-
|-
| 0xDF(~32)
| 0xF8(-8)
| Failed to read sector data from the device.
| The FIRM header magic is not matching "FIRM".
|-
|-
| 0xCF(~48)
| 0xF7(-9)
| FIRM section validation function failed: FIRM section is invalid.
| FIRM image loading got skipped due to already having found an equal or higher priority (firmhdr+4) FIRM to load.
|-
|-
| 0xF7(~8)
| 0xEF(-17)
| A NAND FIRM from another partition was already found with a priority(firmhdr+4) >= to the value for the current partition's FIRM priority.
| Failed to load NCSD header from NAND
|-
|-
| 0xF8(~7)
| 0xEE(-18)
| The FIRM magicnum(firmhdr+0) is invalid.
| NCSD header magic is not "NCSD", or NCSD header RSA verification failed.
|-
|-
| 0xFF(~0)
| 0xDF(-33)
| Initial value for each entry in the 8-entry array of status-codes for the NAND NCSD partitions. Indicates that the partition is not a FIRM partition(partition fs type isn't 0x3 or partition fs crypt-type isn't 0x2).
| Failed to read FIRM header from device.
|-
| 0xDE(-34)
| FIRM header magic is not "FIRM", or FIRM header RSA verification failed.
|-
| 0xCF(-49)
| FIRM section loading failed for any of these reasons:
* FIRM section load address blacklist got tripped
* Failed to read FIRM section data into memory
* FIRM section hash verification failed
|}
|}