Difference between revisions of "Talk:NCSD"
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
@Neimod, then what exists between 0x1000 and 0x4000 and what would you call it?--[[User:3dsguy|3dsguy]] 17:09, 28 July 2012 (CEST) | @Neimod, then what exists between 0x1000 and 0x4000 and what would you call it?--[[User:3dsguy|3dsguy]] 17:09, 28 July 2012 (CEST) | ||
: It's called the card info header, returned by gamecards when reading the header. I'm also finding your updates not always accurate because you are working only with development files, which differ sometimes greatly with retail files. If you look closely, you'll see that retail card info header is 0x200 bytes, while the development card info header is much much bigger. --[[User:Neimod|Neimod]] 20:46, 28 July 2012 (CEST) | : It's called the card info header, returned by gamecards when reading the header. I'm also finding your updates not always accurate because you are working only with development files, which differ sometimes greatly with retail files. If you look closely, you'll see that retail card info header is 0x200 bytes, while the development card info header is much much bigger. --[[User:Neimod|Neimod]] 20:46, 28 July 2012 (CEST) | ||
| + | |||
| + | Old version: | ||
| + | {| class="wikitable" border="1" | ||
| + | |- | ||
| + | ! Offset | ||
| + | ! Size | ||
| + | ! Description | ||
| + | |- | ||
| + | | 0x200 | ||
| + | | 4 | ||
| + | | Always 0xFFFFFFFF | ||
| + | |- | ||
| + | | 0x204 | ||
| + | | 252 | ||
| + | | Padding? | ||
| + | |- | ||
| + | | 0x300 | ||
| + | | 4 | ||
| + | | Used ROM size in bytes | ||
| + | |- | ||
| + | | 0x304 | ||
| + | | 28 | ||
| + | | Padding | ||
| + | |- | ||
| + | | 0x320 | ||
| + | | 8 | ||
| + | | [[NVer]] Title ID (Only Present in retail .CCI) | ||
| + | |- | ||
| + | | 0x328 | ||
| + | | 8 | ||
| + | | [[NVer]] Title Version (Only Present in retail .CCI) | ||
| + | |} | ||
| + | |||
| + | The region-specific NVer title for this NCSD presumably must exist on NAND. The NVer title version may also be used to check whether a system update is required before running the app. | ||
Revision as of 21:48, 28 July 2012
The ExHeader Sha-256 hash and ExHeader Size for the NCSD header is always zero, why?--3dsguy 07:33, 28 July 2012 (CEST)
@Neimod, then what exists between 0x1000 and 0x4000 and what would you call it?--3dsguy 17:09, 28 July 2012 (CEST)
- It's called the card info header, returned by gamecards when reading the header. I'm also finding your updates not always accurate because you are working only with development files, which differ sometimes greatly with retail files. If you look closely, you'll see that retail card info header is 0x200 bytes, while the development card info header is much much bigger. --Neimod 20:46, 28 July 2012 (CEST)
Old version:
| Offset | Size | Description |
|---|---|---|
| 0x200 | 4 | Always 0xFFFFFFFF |
| 0x204 | 252 | Padding? |
| 0x300 | 4 | Used ROM size in bytes |
| 0x304 | 28 | Padding |
| 0x320 | 8 | NVer Title ID (Only Present in retail .CCI) |
| 0x328 | 8 | NVer Title Version (Only Present in retail .CCI) |
The region-specific NVer title for this NCSD presumably must exist on NAND. The NVer title version may also be used to check whether a system update is required before running the app.