Changes

  ...

  ...

== The 3DS' Boot procedure: ==

== Boot procedure: ==

* 0 Seconds - unit is powered on the ARM9 and ARM11 [[Memory_layout|bootroms]] begins execution

* 0 seconds - unit is powered on. The ARM9 and ARM11 [[Memory_layout|bootroms]] begin execution.

* 2 Seconds - ARM9 bootrom attempts to initialize the NAND. If the NAND is successfully initialized, the ARM9 bootrom loads the [[FIRM|firmware]] stored in the NAND [[FIRM]] partition which handles booting the rest of the system(if verification for NAND firm0 fails, the ARM9 bootrom will attempt to use firm1 instead). The ARM11 kernel loaded from FIRM then launches the [[NCCH#CXI|CXI]] ARM11 system modules loaded from FIRM(Note that the ARM11 kernel does not handle any encryption/RSA verification, this is handled by the [[FIRM|ARM9]]). 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 - ARM9 bootrom attempts to initialize the NAND.

**If the NAND is successfully initialized, the ARM9 bootrom loads the [[FIRM|firmware]] stored in the NAND [[FIRM]] partition which handles booting the rest of the system (if verification for NAND firm0 fails, the ARM9 bootrom will attempt to use firm1 instead). The ARM11 kernel loaded from FIRM then launches the [[NCCH#CXI|CXI]] ARM11 system modules loaded from FIRM (i.e. sm, fs, pm, loader, and pxi). (Note that the ARM11 kernel does not handle any encryption/RSA verification, this is handled by the [[FIRM|ARM9]].)

**If the NAND cannot be initialized (i.e. the NAND chip is not connected/damaged/etc), a blue error screen similar to the one above appears.

* 3 Seconds - all essential hardware is active. The [[Process_Manager_Services|PM]] module launches [[NS]], [[NS]] then launches [[ErrDisp]] and the [[Configuration Memory#ACTIVEMENUTID|current active menu]] via PM module. For retail units this menu is usually the [[Home Menu]]. NS will [[NS|auto-boot]] titles instead of launching ErrDisp/Home Menu, if auto-booting is needed. Note that PM module first launches the module dependencies when launching a process, prior to actually launching the process.

* 3 seconds - all essential hardware is active. The [[Process_Manager_Services|PM]] module launches [[NS]], [[NS]] then launches [[ErrDisp]] and the [[Configuration Memory#ACTIVEMENUTID|current active menu]] via PM module. For retail units, this menu is usually the [[Home Menu]]. NS will [[NS|auto-boot]] titles instead of launching ErrDisp/Home Menu, if auto-booting is needed. Note that the PM module first launches the module dependencies when launching a process, prior to actually launching the process. Further details on the Home Menu startup process can be found [[Home_Menu#Home_Menu_startup|here]].

* 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.

== BootROM ==

== BootROM ==

The non-protected areas of the ARM9 and ARM11 bootROMs are identical, for launch-day regular Old3DS, 2DS, and regular New3DS.

The non-protected areas of the ARM9 and ARM11 bootROMs are identical, for launch-day regular Old3DS, 2DS, and regular New3DS.

Besides NATIVE_FIRM, the bootloader is also capable to boot other firmwares (such as TWL_FIRM and AGB_FIRM). However, this will result either in a japanese Error-screen or a system shutdown, directly after FIRM-Launching.

Besides NATIVE_FIRM, the bootloader is also capable to boot other firmwares (such as TWL_FIRM and AGB_FIRM). However, this will result either in a japanese Error-screen or a system shutdown, directly after FIRM-Launching.