Changes

Jump to navigation Jump to search
10 bytes added ,  13:19, 18 October 2015
m
Line 12: Line 12:  
**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.
 
**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 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]].
+
* 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|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.
549

edits

Navigation menu