Bootloader - Revision history

MarcusD: Add some """"low-hanging"""" SD driver error code bits

2024-10-18T17:21:44Z

Add some """"low-hanging"""" SD driver error code bits

@@ Line 129: / Line 129: @@
 * 3rd line is: <code>print_string(..., "%08X %08X", *((unsigned int*)(0x1FFFE000+0x10))`, `*((unsigned int*)(0x1fffe000+0x14)));//See below memory notes.</code>
 * 4th line is: <code>print_string(..., "%08X %08X",*((unsigned int*)(0x1FFFE000+0x18))`, `*((unsigned int*)(0x1fffe000+0x1C)));//See below memory notes.</code>
 === 0x1FFFE000 memory ===
@@ Line 141: / Line 142: @@
 * s8[8] 0x1FFFE000+0x10: Status-codes originally from nand_findfirmpartition_loadfirm(), for each of the 8 NCSD partitions.
 * u32 0x1FFFE000+0x18: SD driver internal error bitfield
-* u32 0x1FFFE000+0x1C: SD driver SD hardware status bits from the controller, AND-ed with 0xFDFF0080 if eMMC, and 0xFDF90008 if SD.
+* u32 0x1FFFE000+0x1C: R1 status bits received from the SD device, AND-ed with 0xFDFF0080 if eMMC (NAND), otherwise 0xFDF90008 if SD.
 === BootROM Status Codes ===

MarcusD: Change indentation of bootrom error sections, as it makes more logical sense

2024-10-18T16:09:08Z

Change indentation of bootrom error sections, as it makes more logical sense

← Older revision		Revision as of 20:09, 18 October 2024
Line 130:		Line 130:
	* 4th line is: <code>print_string(..., "%08X %08X",((unsigned int)(0x1FFFE000+0x18))`, `((unsigned int)(0x1fffe000+0x1C)));//See below memory notes.</code>		* 4th line is: <code>print_string(..., "%08X %08X",((unsigned int)(0x1FFFE000+0x18))`, `((unsigned int)(0x1fffe000+0x1C)));//See below memory notes.</code>

	== 0x1FFFE000 memory ==		=== 0x1FFFE000 memory ===
	This memory is used by boot9 mainly for sending info to the arm11 for the error-screen. The data in this region is still stored in memory by the time the ARM9+ARM11 jumps to FIRM.		This memory is used by boot9 mainly for sending info to the arm11 for the error-screen. The data in this region is still stored in memory by the time the ARM9+ARM11 jumps to FIRM.

Line 143:		Line 143:
	* u32 0x1FFFE000+0x1C: SD driver SD hardware status bits from the controller, AND-ed with 0xFDFF0080 if eMMC, and 0xFDF90008 if SD.		* u32 0x1FFFE000+0x1C: SD driver SD hardware status bits from the controller, AND-ed with 0xFDFF0080 if eMMC, and 0xFDF90008 if SD.

	== BootROM Status Codes ==		=== BootROM Status Codes ===
	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"
	\|-		\|-

MarcusD: Confirmed all bootrom fields to be accurate

2024-10-18T16:07:02Z

Confirmed all bootrom fields to be accurate

← Older revision		Revision as of 20:07, 18 October 2024
Line 114:		Line 114:
	* <code>NN</code>: NAND header (NCSD) load error code		* <code>NN</code>: NAND header (NCSD) load error code
	* <code>p<N></code>: NAND FIRM partition load error code. Note the order of the partitions in the error code!		* <code>p<N></code>: NAND FIRM partition load error code. Note the order of the partitions in the error code!
	* <code>sd_softE</code>: software error (driver status bits, see one section lower)		* <code>sd_softE</code>: software error (SD driver status bits, see one section lower)
	* <code>sd_hardE</code>: hardware error (SD ~~controller~~ status bits ? see one section lower)		* <code>sd_hardE</code>: hardware error (SD device status bits, see one section lower)

MarcusD: Document bootrom error screen format in a human-readable format

2024-10-18T12:33:55Z

Document bootrom error screen format in a human-readable format

← Older revision		Revision as of 16:33, 18 October 2024
Line 103:		Line 103:

	== BootROM Errors ==		== BootROM Errors ==
			Here is the format of the numbers displayed on the error screen:
			BOOTROM 8046
			ERRCODE: ffWWGGNN
			p3p2p1p0 p7p6p5p4
			sd_softE sd_hardE

			* <code>ff</code>: sleep switch state (2==MCU sleep switch closed, 1==GPIO sleep switch closed (very bad if this happens), 0==sleep switch open)
			* <code>WW</code>: NVRAM (WiFi Flash) FIRM load error code
			* <code>GG</code>: ntrboot FIRM load error code
			* <code>NN</code>: NAND header (NCSD) load error code
			* <code>p<N></code>: NAND FIRM partition load error code. Note the order of the partitions in the error code!
			* <code>sd_softE</code>: software error (driver status bits, see one section lower)
			* <code>sd_hardE</code>: hardware error (SD controller status bits ? see one section lower)


	Sample error-screen(where firm0+firm1 RSA signatures were corrupted):		Sample error-screen(where firm0+firm1 RSA signatures were corrupted):

MarcusD: Add missing 1FFFE000 field info, and clean up some wording

2024-10-18T12:25:38Z

Add missing 1FFFE000 field info, and clean up some wording

← Older revision		Revision as of 16:25, 18 October 2024
Line 123:		Line 123:
	* u32 0x1FFFE000+4: ARM11 MPCore "Count Register 0 (PMN0)".		* u32 0x1FFFE000+4: ARM11 MPCore "Count Register 0 (PMN0)".
	* u32 0x1FFFE000+8: ARM11 MPCore "Count Register 1 (PMN0)".		* u32 0x1FFFE000+8: ARM11 MPCore "Count Register 1 (PMN0)".
	* ~~8bit-entry-array~~ 0x1FFFE000+0xC: 8bit status-codes initialized by boot9 main(), for the FIRM-boot devices. +0 is NAND, +1 is NTRCARD and +2 is ~~wifi-spiflash~~.		* s8[4] 0x1FFFE000+0xC: 8bit status-codes initialized by boot9 main(), for the FIRM-boot devices. +0 is NAND, +1 is NTRCARD and +2 is WiFi Flash, +3 is sleep sensor state.
	* ~~...~~		* s8[8] 0x1FFFE000+0x10: Status-codes originally from nand_findfirmpartition_loadfirm(), for each of the 8 NCSD partitions.
	* 8bit-entry-array 0x1FFFE000+0x10: Status-codes originally from nand_findfirmpartition_loadfirm(), for each of the 8 NCSD partitions.		* u32 0x1FFFE000+0x18: SD driver internal error bitfield
			* u32 0x1FFFE000+0x1C: SD driver SD hardware status bits from the controller, AND-ed with 0xFDFF0080 if eMMC, and 0xFDF90008 if SD.

	== BootROM Status Codes ==		== BootROM Status Codes ==

MarcusD: Add unobtainable FD error, for the sake of 100% completeness

2024-10-18T12:20:07Z

Add unobtainable FD error, for the sake of 100% completeness

← Older revision		Revision as of 16:20, 18 October 2024
Line 142:		Line 142:
	\| 0xFE(-2)		\| 0xFE(-2)
	\| Device initialization failed due to it missing or malfunctioning		\| Device initialization failed due to it missing or malfunctioning
			\|-
			\| 0xFD(-3)
			\| unobtainable SD driver initialization failed due to boot9 state not being initialized correctly (it's always initialized)
	\|-		\|-
	\| 0xF8(-8)		\| 0xF8(-8)

MarcusD: Add more bootrom error codes, change complement representation to negative sign instead, and reword errors to be more understandable

2024-10-18T06:41:42Z

Add more bootrom error codes, change complement representation to negative sign instead, and reword errors to be more understandable

← Older revision		Revision as of 10:41, 18 October 2024
Line 134:		Line 134:
	\|-		\|-
	\| 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
	\|}		\|}

Elghis: /* Hardware Failure indications */

2023-07-04T20:07:07Z

Hardware Failure indications

← Older revision		Revision as of 00:07, 5 July 2023
Line 346:		Line 346:
	When a hardware failure is detected, a LED indicator is shown.		When a hardware failure is detected, a LED indicator is shown.

	If you ~~try to~~ replace ~~the~~ screen with ~~the one of a other~~ model, the console ~~will power~~ on, ~~and~~ the screens stays black, but after a minute, the wireless LED ~~will blink~~ four times, ~~stay~~ on for a second, then ~~power~~ off. The blue led ~~is still~~ on, though.		If you replace a Nintendo 3ds console's screen with another Nintendo 3ds model's screen, the console powers on, the screens stays black, but after a minute, the wireless LED blinks four times, stays on for a second, then powers off. The blue led stays on, though.

	We do not have much ~~info~~ about this as usually, when a hardware failure is detected, crashes or ~~instant power~~ off ~~happens~~.		We do not have much information about this as usually, when a hardware failure is detected, the console crashes or powers off immediately.

	== Tools ==		== Tools ==
	* [https://github.com/yellows8/boot9_tools boot9_tools]		* [https://github.com/yellows8/boot9_tools boot9_tools]

Cooolgamer: added hardware failure indications

2023-07-04T19:03:39Z

added hardware failure indications

← Older revision		Revision as of 23:03, 4 July 2023
Line 342:		Line 342:
	\| [[NCSD]] header in sector 0 is corrupt (failed signature check).		\| [[NCSD]] header in sector 0 is corrupt (failed signature check).
	\|}		\|}

			== Hardware Failure indications ==
			When a hardware failure is detected, a LED indicator is shown.

			If you try to replace the screen with the one of a other model, the console will power on, and the screens stays black, but after a minute, the wireless LED will blink four times, stay on for a second, then power off. The blue led is still on, though.

			We do not have much info about this as usually, when a hardware failure is detected, crashes or instant power off happens.

	== Tools ==		== Tools ==
	* [https://github.com/yellows8/boot9_tools boot9_tools]		* [https://github.com/yellows8/boot9_tools boot9_tools]

Radostin04: add a couple new bootrom error codes observed when firm0 and firm1 were corrupt

2021-01-06T09:33:59Z

add a couple new bootrom error codes observed when firm0 and firm1 were corrupt

← Older revision		Revision as of 12:33, 6 January 2021
Line 332:		Line 332:
	\| <tt>00F800FF F8F8FFFF FFFFFFFF 00000000 00000000</tt>		\| <tt>00F800FF F8F8FFFF FFFFFFFF 00000000 00000000</tt>
	\| Both the firm0 and firm1 partitions are corrupt (failed signature checks).		\| Both the firm0 and firm1 partitions are corrupt (failed signature checks).
			\|-
			\| <tt>00F800FF DEDEFFFF FFFFFFFF 00000000 00000000</tt>
			\| Both the firm0 and firm1 partitions are corrupt (possibly related to certain flags missing?)
			\|-
			\| <tt>00F800FF CFCFFFFF FFFFFFFF 00000000 00000000</tt>
			\| Both the firm0 and firm1 partitions are corrupt
	\|-		\|-
	\| <tt>00F800EE FFFFFFFF FFFFFFFF 00000000 00000000</tt>		\| <tt>00F800EE FFFFFFFF FFFFFFFF 00000000 00000000</tt>