Changes

* 2 Seconds - bootrom attempts to initialize the NAND. If the NAND is successfully initialized, the bootrom loads the firmware stored in the NAND [[FIRM]] partition which handles booting the rest of the system. 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 - bootrom attempts to initialize the NAND. If the NAND is successfully initialized, the bootrom loads the firmware stored in the NAND [[FIRM]] partition which handles booting the rest of the system. 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.

* 3 Seconds - all essential hardware is active. The [[Process_Manager_Ports|PM]] module launches [[NS]], [[NS]] then launches the [[Configuration Memory#ACTIVEMENUTID|current active menu]]. For retail units this menu is usually the [[Home Menu]].

* 3 Seconds - all essential hardware is active. The [[Process_Manager_Services|PM]] module launches [[NS]], [[NS]] then launches the [[Configuration Memory#ACTIVEMENUTID|current active menu]] via PM module. For retail units this menu is usually the [[Home Menu]]. Note that PM module first launches the module dependencies when launching a process, prior to actually launching the process.

* 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