CXI: Difference between revisions

(6 intermediate revisions by 2 users not shown)

Line 1:

#REDIRECT [[NCCH#CXI]]

[[Category:File formats]]

The following text tries to document the structure of the CTR Executable Image (CXI) format.

== Overview ==

The CXI format is ~~like~~ a ~~multipurpose~~ container. Generally a CXI ~~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~~ CXI ~~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,

* followed by a plain binary region,

* followed by an embedded executable filesystem ([[ExeFS]]) - (contains ARM11 code, Home menu icn/bnr and logo),

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

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

There are ~~CXI files~~ which are not executable, but are used in conjunction with ~~executable~~ CXI files. For instance the DLP Child ~~CXI~~ and the Home Menu App Manual. (There is a system update ~~CXI~~ which follows this format, but is used by the 3DS rather than the Application ~~CXI~~, 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 ~~CXI~~)

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 ~~CXI~~ files are structured in the following order:

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

* first a NCCH header,

* followed by a read-only filesystem (RomFS)

* followed by a read-only filesystem ([[RomFS]])

Non-Executable ~~CXI~~ file examples(Includes Decrypted RomFS):

Non-Executable NCCH file examples(Includes Decrypted [[RomFS]]):

[http://depositfiles.com/files/d8ej64571 ~~DLPChild~~]

[http://depositfiles.com/files/d8ej64571 DLPChildContainer]

[http://depositfiles.com/files/en9g37b0j Manual]

@@ Line 1: / Line 1: @@
+#REDIRECT [[NCCH#CXI]]
 [[Category:File formats]]
 The following text tries to document the structure of the CTR Executable Image (CXI) format.
 == Overview ==
-The CXI format is like a multipurpose container. Generally a CXI 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 CXI 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,
 * followed by a plain binary region,
 * followed by an embedded executable filesystem ([[ExeFS]]) - (contains ARM11 code, Home menu icn/bnr and logo),
-* and finally followed by a read-only filesystem (RomFS) - (Used for external file storage).
+* and finally followed by a read-only filesystem ([[RomFS]]) - (Used for external file storage).
-There are CXI files which are not executable, but are used in conjunction with executable CXI files. For instance the DLP Child CXI and the Home Menu App Manual. (There is a system update CXI which follows this format, but is used by the 3DS rather than the Application CXI, 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 CXI)
+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 CXI files are structured in the following order:
+Non-Executable NCCH files are structured in the following order:
 * first a NCCH header,
-* followed by a read-only filesystem (RomFS)
+* followed by a read-only filesystem ([[RomFS]])
-Non-Executable CXI file examples(Includes Decrypted RomFS):
+Non-Executable NCCH file examples(Includes Decrypted [[RomFS]]):
-[http://depositfiles.com/files/d8ej64571 DLPChild]
+[http://depositfiles.com/files/d8ej64571 DLPChildContainer]
 [http://depositfiles.com/files/en9g37b0j Manual]