839
edits
Changes
Jump to navigation
Jump to search
Line 15:
Line 15: − + − + + + + +
→Applications ( any executable code )
.NSA - Archive used by several of the communication protocols in the 3DS.
.NSA - Archive used by several of the communication protocols in the 3DS.
.RSF - Descriptive data used when outputting a CCI/CXI file. Specifies options such as: title, save type, and so on.
.RSF - Descriptive data used when outputting a CCI/CXI file. Specifies options such as: title, save type, and so on.
.AXF - Pre-assembled ARM code. before being linked into a CCI/CXI format. They're practically ARM specific ELF files.
.DESC - Descriptive data used when outputting a CCI/CXI file. Like the .RSF format, but more complex (more complex in the options which it can specify).
.BSF - Descriptive data used when outputting ICN files. The .XBSF format used by CiTRUS is based on the concept of .BSF.
.AXF - Pre-assembled ARM code. Before being linked into the [[ExeFS]] '.code' format. They're practically ARM specific ELF files. The Plain Region found in the CXI is also obtain from this file.
.CDI - (CTR Development Image) CDI files are system processes which other types of applications depend on for access to various other lower level functions. CDI are normally the same titles as listed in a CXI header's dependency list, they are just compiled to a different format. The difference is that CDI is used for a different (test) environment. They're loaded into hardware debugger's memory, along with the 2 cores in order to execute.
.CDI - (CTR Development Image) CDI files are system processes which other types of applications depend on for access to various other lower level functions. CDI are normally the same titles as listed in a CXI header's dependency list, they are just compiled to a different format. The difference is that CDI is used for a different (test) environment. They're loaded into hardware debugger's memory, along with the 2 cores in order to execute.