3dbrew

CCI: Difference between revisions

← Older editNewer edit →
Elisherer (talk | contribs)
399 edits
→CXI Table Theory: too big header
Elisherer (talk | contribs)
399 edits
update the table theory (it appeared to be correct)
Line 1: Line 1:
[[Category:File formats]]
This document is about the format of CTR cart images (CCI), which is also the format of 3DS ROM dumps.
This document is about the format of CTR cart images (CCI), which is also the format of 3DS ROM dumps.
This is a container format which holds [[CXI]] files inside.


=== Overview ===
=== Overview ===
CCI files start with a NCSD header, followed by up to a maximum of 8 NCCH blocks according to spec. The first block usually starts at 0x4000. In most carts the first block contains game code/data, the second block contains the download play "child" and the third block contains potential system updates. The exact contents of NCCH blocks can be determined by looking at the flags.
CCI files start with a NCSD header, followed by up to a maximum of 13 NCCH blocks according to spec. The first block usually starts at 0x4000. In most carts the first block contains game code/data, the second block contains the download play "child" and the third block contains potential system updates. The exact contents of NCCH blocks can be determined by looking at the flags.
 
The NCCH blocks are in the same format as [[CXI]] files.


=== NCSD header ===
=== NCSD header ===
Line 28: Line 29:
|  8
|  8
|  Title/Program ID
|  Title/Program ID
|-
|  0x110
|  16
|  Unknown
|-
|-
|  0x120
|  0x120
|  4
|  0x68=(4+4)*13
|  Offset to the first NCCH in media units
|  Offset & Length CXI table
|-
|  0x124
|  4
|  Size of the first NCCH
|-
|  0x130
|  4
|  Offset to the second NCCH
|-
|  0x134
|  4
|  Size of the second NCCH
|-
|  0x158
|  4
|  Offset to the third NCCH
|-
|  0x15C
|  4
|  Size of the third NCCH
|-
|-
|  0x188
|  0x188
|  8
|  8
|  NCCH Flags: byte[5]-byte[7] indicate content type ( system update, application, manual, ... ) size of media units ( 512*2^byte[6] ) and encryption.
|  CXI Flags: byte[5]-byte[7] indicate content type ( system update, application, manual, ... ) size of media units ( 512*2^byte[6] ) and encryption.
|-
|-
|  0x190
|  0x190
|  8
|  0x68=8*13
|  Partition ID of the first NCCH
|  CXI's Title ID table
|-
|  0x1A0
|  8
|  Partition ID of the second NCCH
|-
|-
|  0x1C8
|  0x1F8
|  8
|  8
|  Partition ID of the third NCCH
|  Unknown
|-
|-
|  0x200
|  0x200
|  4
|  4
|  Always 0xFFFFFFFF
|  Always 0xFFFFFFFF
|-
|  0x204
|  252
|  Padding?
|-
|-
|  0x300
|  0x300
|  4
|  4
|  Used ROM size in bytes
|  Used ROM size in bytes
|-
|  0x304
|  28
|  Padding
|-
|-
|  0x320
|  0x320
Line 88: Line 77:
Parts of the first NCCH block's header are found around 0x1000 for whatever reason.
Parts of the first NCCH block's header are found around 0x1000 for whatever reason.


CCI images may not include all three NCCH blocks. For example, Ghost Recon: Shadow Wars lacks the second NCCH. Entries at 0x130, 0x134 and 0x1A0 in its NCSD header are zero.
CCI can hold up to 13 CXI (i.e. Mario Kart 7 holds 4 CXIs, most we've seen so far)
 
=== CXI Table Theory ===
 
The 3 CXIs appear in some order.
 
if you take offset 0x120 and look at it as a table of {uint32 offset, uint32 length} it might be the CXI table
 
and at 0x190 starting the title_id table {uint64 title_id} of the same size as the table before.
 
Each CXI's information is on the same index on both tables...


In this method of reading CCIs can hold up to 13 CXIs.
CSU files are basicaly CCI files.
Retrieved from "https://www.3dbrew.org/wiki/CCI"