Changes

No change in size ,  06:12, 19 July 2012
m
no edit summary
Line 7: Line 7:  
== CXI ==  
 
== CXI ==  
   −
The CXI (CTR Executable Image) specialisation of NCCH containers, contains 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 (CTR Executable Image) specialisation of the NCCH container, contains 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 structured in the following order:
 
The CXI format is structured in the following order:
Line 21: Line 21:  
== CFA ==
 
== CFA ==
   −
The CFA (CTR File Archive), specialisation of NCCH containers that are not executable, but are used in conjunction with CXI 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)
+
The CFA (CTR File Archive) specialisation of the NCCH container, is not executable, but are used in conjunction with CXI 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)
    
CFA files are structured in the following order:
 
CFA files are structured in the following order:
839

edits