NCCH: Difference between revisions

No edit summary
No edit summary
Line 45: Line 45:
All of the hashes stored in this NCCH header are over the cleartext data. The ExeFS/RomFS superblock starts at offset 0x0 in the ExeFS/RomFS, and the size is specified by the hash region fields.
All of the hashes stored in this NCCH header are over the cleartext data. The ExeFS/RomFS superblock starts at offset 0x0 in the ExeFS/RomFS, and the size is specified by the hash region fields.


As of [[5.0.0-11]] the application [[ExeFS]]:/.logo can be loaded from the plaintext region between the access descriptor and the plain region, all applications built since [[5.0.0-11]] likely store the logo here. Normally the size of this logo 0x2000-bytes.
As of [[5.0.0-11]] the application [[ExeFS]]:/.logo can be loaded from the plaintext region between the access descriptor and the plain region, all applications built since [[5.0.0-11]] store the logo here. Normally the size of this logo 0x2000-bytes.
 
The plain region mainly contains tags for each SDK library used when building the CXI. The version used for the "FIRMWARE" tag is the kernel/FIRM [[Configuration_Memory|version]], this version can also be stored in the exheader "kernel release version" ARM11 kernel descriptor field.


=== NCCH Header ===
=== NCCH Header ===
Line 96: Line 98:
| 0x130
| 0x130
| 0x20
| 0x20
| For [[5.0.0-11]]+ applications, this is a SHA-256 of the logo located between the access-desc and palin region.
| For [[5.0.0-11]]+ applications, this is a SHA-256 hash of the logo located between the access-desc and palin region.
|-
|-
|  0x150
|  0x150