6,263
edits
Changes
Jump to navigation
Jump to search
Line 5:
Line 5: − +
no edit summary
A structural example of a FIRM file (created using the specs in [https://github.com/3dshax/ctr ctrtool]) can be found [http://depositfiles.com/files/lzpo8yqyo here] (Note it does not contain any ARM code, it's just a structural example)
A structural example of a FIRM file (created using the specs in [https://github.com/3dshax/ctr ctrtool]) can be found [http://depositfiles.com/files/lzpo8yqyo here] (Note it does not contain any ARM code, it's just a structural example)
The ARM9 section contains the ARM9 kernel and the ARM9 process. The ARM11 section(s) contains the ARM11 kernel, and the ARM11 process(es). For NATIVE_FIRM/SAFE_MODE_FIRM these ARM11 processes are sm, fs, pm, loader, and pxi. Normally the 4th section is not used. The code loaded from FIRM is constantly running on the system until another FIRM is launched.
The ARM9 section contains the ARM9 kernel and the ARM9 process(exheader process name is "Process9"). The ARM11 section(s) contains the ARM11 kernel, and the ARM11 process(es). For NATIVE_FIRM/SAFE_MODE_FIRM these ARM11 processes are sm, fs, pm, loader, and pxi. Normally the 4th section is not used. The code loaded from FIRM is constantly running on the system until another FIRM is launched. The ARM11 kernel is hard-coded to always decompress the FIRM ARM11 modules ExeFS .code, the exheader compression bit is not checked.
== FIRM Header ==
== FIRM Header ==