Difference between revisions of "Bootloader"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
* 2 Seconds - bootloader attempts to initialize the NAND. If the NAND is successfully initialized, it takes over booting the 3DS. If the NAND, cannot be initialized (i.e. the NAND chip is not connected/damaged etc) a blue error screen similar to the screen above appears. | * 2 Seconds - bootloader attempts to initialize the NAND. If the NAND is successfully initialized, it takes over booting the 3DS. If the NAND, cannot be initialized (i.e. the NAND chip is not connected/damaged etc) a blue error screen similar to the screen above appears. | ||
− | * 3 Seconds - all essential hardware is active - | + | * 3 Seconds - all essential hardware is active - [[NS]] loads the [[Shared_Registers#REG_ACTIVEMENUTID|current active menu]], for retail units this is usually the [[Home Menu]]. |
− | |||
* 4 Seconds - the LCD screens are initialized | * 4 Seconds - the LCD screens are initialized | ||
* 7 Seconds - [[Home Menu]] is fully initialized/loaded | * 7 Seconds - [[Home Menu]] is fully initialized/loaded |
Revision as of 08:25, 22 September 2012
When the 3DS does not find the NAND chip, the following error is displayed:
The 3DS' Boot procedure:
- 0 Seconds - unit is powered on bootloader begins
- 2 Seconds - bootloader attempts to initialize the NAND. If the NAND is successfully initialized, it takes over booting the 3DS. If the NAND, cannot be initialized (i.e. the NAND chip is not connected/damaged etc) a blue error screen similar to the screen above appears.
- 3 Seconds - all essential hardware is active - NS loads the current active menu, for retail units this is usually the Home Menu.
- 4 Seconds - the LCD screens are initialized
- 7 Seconds - Home Menu is fully initialized/loaded