Changes

Jump to navigation Jump to search
942 bytes added ,  18:39, 9 August 2020
m
Line 9: Line 9:     
.[[SD Filesystem#title|APP]] - The per-console encrypted form of a NCCH file, used with installed titles, like eShop and CDN downloads.
 
.[[SD Filesystem#title|APP]] - The per-console encrypted form of a NCCH file, used with installed titles, like eShop and CDN downloads.
 +
 +
.CAA - A CXI which uses a raw ELF for the [[ExeFS]] .code section. Also has no plain region.
    
== [[NCSD]] ==
 
== [[NCSD]] ==
Line 24: Line 26:  
.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.  
   −
.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).
+
.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). The signed NCCH RSA-2048 key pair is taken from this file.
    
== [[ExeFS]] Related File Formats ==
 
== [[ExeFS]] Related File Formats ==
      −
.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.
+
.AXF - Pre-assembled ARM code. Before being linked into the [[ExeFS]] '.code' format. These are ARM specific ELF files. The Plain Region found in the CXI is also obtained from this file.
   −
.BNR - Simply contains a .[[CBMD]] and a .[[BCWAV]], in that order with padding in between the two files to make sure the .[[BCWAV]] is aligned to 0x10 bytes. It contains nothing else.
+
.BNR - Simply contains a .[[CBMD]] and a .[[BCWAV]]. The .[[CBMD]] has added padding, to make sure the .[[BCWAV]] is aligned to 0x10 bytes. It contains nothing else.(The .[[CBMD]] file's header is edited to reflect its new size)
    
.[[SMDH|ICN]] - Contains icons, names and flags for an application
 
.[[SMDH|ICN]] - Contains icons, names and flags for an application
 +
 +
== [[RomFS]] Related File Formats ==
 +
 +
.[[ARC]] - Archive. A container of files, all compressed with LZ-10.
 +
 +
.[[ARC|BCMA]] - CTR Manual (an ARC file).
 +
 +
.[[SARC]] - Simple(?) Archive. A container of uncompressed files.
 +
 +
.[[BCFNT]] - CTR Font File (version 3).
 +
 +
.[[BCFNT|BFFNT]] - CTR Font File (version 4).
 +
 +
== [[Title Data Structure|Title Installation Related File Formats]] ==
 +
 +
.[[CIA]] - CTR Importable Archive - This format allows the installation of titles to the 3DS. CIA files can contain [[NCCH]] files for installation to either the [[SD Filesystem|SDMC]] or CTR NAND. CIA files can also contain .SRL files (format for DS(i) executable images) for installation to the TWL NAND of the 3DS. Anything distributed over Download Play (including card software) is created with this format as well.
 +
 +
.[[TMD]] - Title Meta Data - The format is used with installed/installable titles. Notably they are found in .[[CIA]] files (plain text), on the [[SD Filesystem#title|SD card]] (encrypted), NAND (encrypted) and on Nintendo's CDN (plain text).
 +
 +
.[[Title Data Structure|CMD]] - Content Meta Data - The format is used to index installed .app files for installed titles. It is encrypted with a console unique [[AES|keyslot]].
 +
 +
.[[Title Data Structure|CTX]], Content Transfer: When beginning eShop app downloads, this file is created. Later this file is written with actual data. When the download is completed, the file is deleted from SD card.  (This might then be moved to NAND.) This is encrypted with a per-console key. It contains a signed cert followed by unknown data. It is only 1.50kbyte. Here is an example.[http://dl.dropbox.com/u/37418652/00000000.ctx]
    
== Audio File Formats ==
 
== Audio File Formats ==
    
.[[BCWAV|(B)CWAV]] - CTR waveform file format
 
.[[BCWAV|(B)CWAV]] - CTR waveform file format
 +
 +
.[[BCSTM|(B)CSTM]] - CTR stream file format
 +
 +
.[[BCSAR|(B)CSAR]]- CTR adaptation of BRSAR.
    
== Graphics File Formats ==
 
== Graphics File Formats ==
   −
.[[CBMD]] - CTR binary banner model - Archive file before being made into a CTR banner for games or other applications.
+
.[[CBMD]] - CTR Basic Model Data - Archive file before being made into a CTR banner for games or other applications.
   −
.CTPK - CTR Texture PacKage
+
.[[CTPK]] - CTR Texture PacKage
    
.CMDL - CTR MoDeL data
 
.CMDL - CTR MoDeL data
    
.CTEX - CTR TEXture data
 
.CTEX - CTR TEXture data
 +
 +
.CCAD - CTR Celluloid Animation Data
    
.CSKA / .CSKLA - CTR SKeLetal Animation data
 
.CSKA / .CSKLA - CTR SKeLetal Animation data
Line 69: Line 99:  
== Other File Formats ==
 
== Other File Formats ==
   −
.[[CIA]] - CTR Importable Archive - This format allows the installation titles to the 3DS. CIA files can contain [[NCCH]] files for installation to either the [[SD Filesystem|SDMC]] or CTR NAND. CIA files can also contain .SRL files (format for DS(i) executable images) for installation to the TWL NAND of the 3DS.
+
.NSA - Archive used by several of the communication protocols in the 3DS.
   −
.[[TMD]] - Title Metadata - The format is used with installed/installable titles. Notably they are found in .[[CIA]] files (plain text), on the [[SD Filesystem#title|SD card]] (encrypted), NAND (encrypted) and on Nintendo's CDN (plain text).
+
.[[CRO0|CRO]] - This is a CTR "DLL".
   −
.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.  
+
.[[CRO0|CRS]] - This is a special CRO format file which contains symbols for .code (the "static module").
   −
.NSA - Archive used by several of the communication protocols in the 3DS.
+
.[[CRR0|CRR]] - This contains data for verifying CRO files.
   −
.CIP - (CTR Initial Process)
+
.[[MPO]] - Multi-Picture Object Format - Document describing the file format used in mpo files: http://www.cipa.jp/english/hyoujunka/kikaku/pdf/DC-007_E.pdf
   −
.[[SD Filesystem#title|CTX]] - When beginning eShop app downloads, this file is created. Later this file is written with actual data. When the download is completed, the file is deleted from SD card.(This might then be moved to NAND) This is encrypted with a per-console key. It contains a signed cert followed by unknown data. It is only 1.50kbyte. Here is an example.[http://dl.dropbox.com/u/37418652/00000000.ctx]
+
.CGRP - CTR GRouP - Used to package several formats like (CWAR, CWAV, CWSD, CBNK, CSEQ, etc...) sort of like the Wii's MRG format. (They aren't the same structures but both package together several formats.)
 
  −
.[[MPO]] - Multi-Picture Object Format - Document describing the file format used in mpo files: http://www.cipa.jp/english/hyoujunka/kikaku/pdf/DC-007_E.pdf
      
== Filesystem ==
 
== Filesystem ==
    
The 3DS filesystem requires absolute paths. It can handle either short (8.3) and long (255 char maximum) file names.
 
The 3DS filesystem requires absolute paths. It can handle either short (8.3) and long (255 char maximum) file names.
3

edits

Navigation menu