Difference between revisions of "NS and APT Services"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | The NS system module is the first module launched after the core processes sm, fs, pm, loader, and pxi are loaded. This module is launched by the pm process, with the titleID loaded from [[Shared_Registers|REG_NSTID]]. NS first launches [[ErrDisp]], then the menu. | + | The NS system module is the first module launched from a NAND title after the core processes sm, fs, pm, loader, and pxi are loaded. This module is launched by the pm process, with the titleID loaded from [[Shared_Registers|REG_NSTID]]. NS first launches [[ErrDisp]], then the menu. On retail the menu TID is loaded from [[Shared_Registers#REG_MENUTID|REG_MENUTID]], while on dev/debug the menu TID is loaded from [[CfgS:GetConfigInfoBlk2#ConfigInfoBlks|config]]. The TID of the launched menu is then written to [[Shared_Registers#REG_ACTIVEMENUTID|REG_ACTIVEMENUTID]]. |
| + | |||
| + | = Alternate menu = | ||
| + | When launching the regular menu fails, NS will then attempt to launch the alternate menu. This title could be used as a recovery process, however it normally doesn't exist on retail. | ||
= NS service "ns:s" = | = NS service "ns:s" = | ||
Revision as of 20:37, 22 July 2012
The NS system module is the first module launched from a NAND title after the core processes sm, fs, pm, loader, and pxi are loaded. This module is launched by the pm process, with the titleID loaded from REG_NSTID. NS first launches ErrDisp, then the menu. On retail the menu TID is loaded from REG_MENUTID, while on dev/debug the menu TID is loaded from config. The TID of the launched menu is then written to REG_ACTIVEMENUTID.
When launching the regular menu fails, NS will then attempt to launch the alternate menu. This title could be used as a recovery process, however it normally doesn't exist on retail.
NS service "ns:s"
| Command Header | Description |
|---|---|
| 0x0002.... | LaunchTitle |