Difference between revisions of "NSS:LaunchFIRM"
Jump to navigation
Jump to search
Steveice10 (talk | contribs) m (→Request) |
|||
Line 8: | Line 8: | ||
| Header code [0x000100C0] | | Header code [0x000100C0] | ||
|- | |- | ||
− | | 1 | + | | 1-2 |
− | + | | u64, Application Title ID | |
− | |||
− | |||
− | | Application | ||
|- | |- | ||
| 3 | | 3 |
Latest revision as of 04:12, 20 January 2016
Request[edit]
Index Word | Description |
---|---|
0 | Header code [0x000100C0] |
1-2 | u64, Application Title ID |
3 | Unused |
Response[edit]
Index Word | Description |
---|---|
0 | Header code |
1 | Result code |
Description[edit]
When this TID is zero, the gamecard TID is obtained via AM. If the TID is the JPN System Settings titleID, the TID used for applet entry initialization is loaded from an array of System Settings titleIDs, where the array-index is determined by the region. This command then initializes the titleID+mediatype field for appletID 0x300, in the titleID applet array using the TID. This is mostly the same as NSS:LaunchApplicationFIRM without the Configuration Memory checks. This calls the same code which NSS:LaunchApplicationFIRM uses for flags bit0=1.
When the required FIRM for the specified title matches the already running FIRM, NS will skip FIRM-launch and just do a normal title launch.