CXI: Difference between revisions

Line 3:

== Overview ==

The ~~NCCH (~~CXI) format is ~~like~~ a ~~multipurpose~~ container. Generally ~~a NCCH file~~ will contain ~~the~~ executable code, which runs on a single ARM11 core. It can communicate through SVC calls with the other ARM11 core running the 'system' program code. For reasons of clarity, the ARM11 cores will sometimes be called the 'appcore' and 'syscore' respectively.

The CXI format is a specialization of an NCCH container. Generally the CXI will contain executable code, which runs on a single ARM11 core. It can communicate through SVC calls with the other ARM11 core running the 'system' program code. For reasons of clarity, the ARM11 cores will sometimes be called the 'appcore' and 'syscore' respectively.

~~Executable NCCH files are~~ structured in the following order:

The CXI format is structured in the following order:

* first a NCCH header,

* followed by an extended header,

Line 12:

* and finally followed by a read-only filesystem ([[RomFS]]) - (Used for external file storage).

There are NCCH ~~files~~ which are not executable, but are used in conjunction with ~~executable~~ NCCH files. For instance the DLP Child Container and the Home Menu App Manual. (There is a system update NCCH which follows this format, but is used by the 3DS rather than the Application NCCH, and only works when embedded in the [[CCI]] format because the nVer is kept in the header of retail [[CCI]] files instead of the application NCCH)

There are specializations of NCCH containers which are not executable, but are used in conjunction with CXI NCCH files. For instance the DLP Child Container and the Home Menu App Manual. (There is a system update NCCH which follows this format, but is used by the 3DS rather than the Application NCCH, and only works when embedded in the [[CCI]] format because the nVer is kept in the header of retail [[CCI]] files instead of the application NCCH)

Non-Executable NCCH files are structured in the following order:

@@ Line 3: / Line 3: @@
 == Overview ==
-The NCCH (CXI) format is like a multipurpose container. Generally a NCCH file will contain the executable code, which runs on a single ARM11 core. It can communicate through SVC calls with the other ARM11 core running the 'system' program code. For reasons of clarity, the ARM11 cores will sometimes be called the 'appcore' and 'syscore' respectively.
+The CXI format is a specialization of an NCCH container. Generally the CXI will contain executable code, which runs on a single ARM11 core. It can communicate through SVC calls with the other ARM11 core running the 'system' program code. For reasons of clarity, the ARM11 cores will sometimes be called the 'appcore' and 'syscore' respectively.
-Executable NCCH files are structured in the following order:
+The CXI format is structured in the following order:
 * first a NCCH header,
 * followed by an extended header,
@@ Line 12: / Line 12: @@
 * and finally followed by a read-only filesystem ([[RomFS]]) - (Used for external file storage).
-There are NCCH files which are not executable, but are used in conjunction with executable NCCH files. For instance the DLP Child Container and the Home Menu App Manual. (There is a system update NCCH which follows this format, but is used by the 3DS rather than the Application NCCH, and only works when embedded in the [[CCI]] format because the nVer is kept in the header of retail [[CCI]] files instead of the application NCCH)
+There are specializations of NCCH containers which are not executable, but are used in conjunction with CXI NCCH files. For instance the DLP Child Container and the Home Menu App Manual. (There is a system update NCCH which follows this format, but is used by the 3DS rather than the Application NCCH, and only works when embedded in the [[CCI]] format because the nVer is kept in the header of retail [[CCI]] files instead of the application NCCH)
 Non-Executable NCCH files are structured in the following order: