NSS:LaunchApplicationFIRM: Difference between revisions
No edit summary |
Steveice10 (talk | contribs) m →Request |
||
(3 intermediate revisions by one other user not shown) | |||
Line 6: | Line 6: | ||
|- | |- | ||
| 0 | | 0 | ||
| Header code [ | | Header code [0x000500C0] | ||
|- | |- | ||
| 1 | | 1-2 | ||
| u64, Title ID | |||
| | |||
|- | |- | ||
| 3 | | 3 | ||
Line 34: | Line 31: | ||
This triggers a FIRM [[PMApp:LaunchFIRMSetParams|launch]], where the title run by this FIRM is specified with the input titleID. The [[FIRM]] titleID-low is determined by the input application titleID. When the input TID is all-zero, the application is launched from the gamecard by the launched FIRM. | This triggers a FIRM [[PMApp:LaunchFIRMSetParams|launch]], where the title run by this FIRM is specified with the input titleID. The [[FIRM]] titleID-low is determined by the input application titleID. When the input TID is all-zero, the application is launched from the gamecard by the launched FIRM. | ||
Flags bit0 is set when launching a [[FIRM]] which requires an application title-info structure to be specified via [[FIRM]] parameters. Otherwise when | Flags bit0 is set when launching a [[FIRM]] which requires an application title-info structure to be specified via [[FIRM]] parameters. Otherwise when not specifying FIRM parameters, bit0 is clear. When flags bit1 is clear, NS will check certain [[Configuration Memory]] fields and will return an error if these checks fail. This [[Configuration Memory]] field checks seems to always pass on retail however. | ||
See [[APT:GetProgramInfo|here]] for how the FIRM programID-low is determined. |