NCCH/Extended Header - Revision history

TimmSkiller: Use separate rows for Flag1 and Flag2 to avoid confusion

2025-11-06T16:56:01Z

Use separate rows for Flag1 and Flag2 to avoid confusion

← Older revision		Revision as of 19:56, 6 November 2025
Line 176:		Line 176:
	\|-		\|-
	\| <code>0xC</code>		\| <code>0xC</code>
	\| <code>~~0x2~~</code>		\| <code>0x1</code>
	\| [[#Flag1\|Flag1]] ~~and~~ [[#Flag2\|Flag2]] (~~both~~ implemented starting from [[8.0.0-18]]).		\| [[#Flag1\|Flag1]] (implemented starting from [[8.0.0-18]])
			\|-
			\| <code>0xD</code>
			\| <code>0x1</code>
			\| [[#Flag2\|Flag2]] (implemented starting from [[8.0.0-18]])
	\|-		\|-
	\| <code>0xE</code>		\| <code>0xE</code>

Kynex7510 at 23:20, 9 May 2025

2025-05-09T21:20:34Z

← Older revision		Revision as of 01:20, 10 May 2025
Line 31:		Line 31:
	\| <code>0x500</code>		\| <code>0x500</code>
	\| <code>0x100</code>		\| <code>0x100</code>
	\| NCCH ~~HDR~~ RSA-2048 ~~public key~~		\| NCCH header RSA-2048 modulus
	\|-		\|-
	\| <code>0x600</code>		\| <code>0x600</code>
Line 38:		Line 38:
	\|}		\|}

	The <code>AccessDesc</code> signature covers the NCCH ~~HDR public key~~ and second ACI. The <code>AccessDesc</code> public key is initialised by the boot ROM.		The <code>AccessDesc</code> signature covers the NCCH header modulus and second ACI. The <code>AccessDesc</code> public key is initialised by the boot ROM.

	When loading the exheader, [[FIRM\|Process9]] compares the exheader data with the data in the <code>AccessDesc</code> (note that not everything is compared here). When these don't match, an error is returned. The Process9 code handling this validation was updated with [[6.0.0-11\|v6.0]]; the only change in this function seems to be the check for the "Ideal processor" field.		When loading the exheader, [[FIRM\|Process9]] compares the exheader data with the data in the <code>AccessDesc</code> (note that not everything is compared here). When these don't match, an error is returned. The Process9 code handling this validation was updated with [[6.0.0-11\|v6.0]]; the only change in this function seems to be the check for the "Ideal processor" field.

TuxSH: /* ARM11 Kernel Capabilities */

2023-08-09T16:09:12Z

ARM11 Kernel Capabilities

← Older revision		Revision as of 20:09, 9 August 2023
Line 494:		Line 494:
	\|-		\|-
	\| <code>0b11111111100x</code>		\| <code>0b11111111100x</code>
	\| Map address range		\| Map IO/static address range
	\| Describes a memory mapping like the 0b111111111110 descriptor, but an entire range rather than a single page is mapped. Another 0b11111111100x descriptor must follow this one to denote the (exclusive) end of the address range to map.		\| Describes a memory mapping like the 0b111111111110 descriptor, but an entire range rather than a single page is mapped. Another 0b11111111100x descriptor must follow this one to denote the (exclusive) end of the address range to map. Bit20 on the first descriptor: map read-only (otherwise RW), bit20 on the second descriptor: map static (cacheable, otherwise IO if the bit is not set)
	\|-		\|-
	\| <code>0b111111111110</code>		\| <code>0b111111111110</code>
	\| Map memory page		\| Map IO memory page
	\| Bits 0-19: page index to map (virtual address >> 12; the physical address is determined per-page according to [[Memory layout]]); Bit 20: Map read-only (otherwise read-write)		\| Bits 0-19: page index to map (virtual address >> 12; the physical address is determined per-page according to [[Memory layout]]); Bit 20: Map read-only (otherwise read-write)
	\|}		\|}

0xadk: fix broken link

2023-03-11T17:41:34Z

fix broken link

← Older revision		Revision as of 20:41, 11 March 2023
Line 9:		Line 9:
	All values are little endian unless otherwise specified.		All values are little endian unless otherwise specified.

	See also: [https://github.com/~~profi200~~/Project_CTR/blob/~~master~~/ctrtool/exheader.h]		See also: [https://github.com/3DSGuy/Project_CTR/blob/20f708450b9c6e7f64eafa6c2a8eeb25a630c69a/ctrtool/exheader.h]

	{\| class="wikitable" border="1"		{\| class="wikitable" border="1"

Yuriks: Undo revision 18301 by Neobrain (talk)

2017-05-06T18:54:52Z

Undo revision 18301 by Neobrain (talk)

← Older revision		Revision as of 22:54, 6 May 2017
Line 495:		Line 495:
	\| <code>0b11111111100x</code>		\| <code>0b11111111100x</code>
	\| Map address range		\| Map address range
	\| Describes a memory mapping like the 0b111111111110 descriptor, but an entire range rather than a single page is mapped. ~~Usually, another~~ 0b11111111100x descriptor ~~follows~~ this one to denote the (exclusive) end of the address range to map~~, but it has been observed that sometimes the range is not explicitly closed, which presumably indicates a single-page mapping~~.		\| Describes a memory mapping like the 0b111111111110 descriptor, but an entire range rather than a single page is mapped. Another 0b11111111100x descriptor must follow this one to denote the (exclusive) end of the address range to map.
	\|-		\|-
	\| <code>0b111111111110</code>		\| <code>0b111111111110</code>

Profi200: /* System Control Info */

2017-01-28T16:25:44Z

System Control Info

← Older revision		Revision as of 19:25, 28 January 2017
Line 51:		Line 51:
	\| <code>0x0</code>		\| <code>0x0</code>
	\| <code>0x8</code>		\| <code>0x8</code>
	\| Application title (default ~~seems to be~~ "CtrApp")		\| Application title (default is "CtrApp")
	\|-		\|-
	\| <code>0x8</code>		\| <code>0x8</code>

Hiccup: /* System Control Info */

2017-01-28T15:59:26Z

System Control Info

← Older revision		Revision as of 18:59, 28 January 2017
Line 51:		Line 51:
	\| <code>0x0</code>		\| <code>0x0</code>
	\| <code>0x8</code>		\| <code>0x8</code>
	\| Application title		\| Application title (default seems to be "CtrApp")
	\|-		\|-
	\| <code>0x8</code>		\| <code>0x8</code>

Neobrain: /* ARM11 Kernel Capabilities */

2016-09-26T07:44:15Z

ARM11 Kernel Capabilities

← Older revision		Revision as of 11:44, 26 September 2016
Line 495:		Line 495:
	\| <code>0b11111111100x</code>		\| <code>0b11111111100x</code>
	\| Map address range		\| Map address range
	\| Describes a memory mapping like the 0b111111111110 descriptor, but an entire range rather than a single page is mapped. ~~Another~~ 0b11111111100x descriptor ~~must follow~~ this one to denote the (exclusive) end of the address range to map.		\| Describes a memory mapping like the 0b111111111110 descriptor, but an entire range rather than a single page is mapped. Usually, another 0b11111111100x descriptor follows this one to denote the (exclusive) end of the address range to map, but it has been observed that sometimes the range is not explicitly closed, which presumably indicates a single-page mapping.
	\|-		\|-
	\| <code>0b111111111110</code>		\| <code>0b111111111110</code>

Neobrain: The VAddr->PAddr translation is different for non-IO memory

2016-08-22T07:40:18Z

The VAddr->PAddr translation is different for non-IO memory

← Older revision		Revision as of 11:40, 22 August 2016
Line 499:		Line 499:
	\| <code>0b111111111110</code>		\| <code>0b111111111110</code>
	\| Map memory page		\| Map memory page
	\| Bits 0-19: page index to map (virtual address >> 12; the physical address is determined ~~by subtracting 0x0EB00000~~); Bit 20: Map read-only (otherwise read-write)		\| Bits 0-19: page index to map (virtual address >> 12; the physical address is determined per-page according to [[Memory layout]]); Bit 20: Map read-only (otherwise read-write)
	\|}		\|}

Neobrain: This stuff isn't limited to IO, but is also e.g. used to map VRAM

2016-08-22T07:13:04Z

This stuff isn't limited to IO, but is also e.g. used to map VRAM

← Older revision		Revision as of 11:13, 22 August 2016
Line 494:		Line 494:
	\|-		\|-
	\| <code>0b11111111100x</code>		\| <code>0b11111111100x</code>
	\| Map IO address range		\| Map address range
	\| ~~Bits 0-19: index of~~ the ~~first IO~~ page ~~to map; Bit 20: Map read-only (otherwise read-write)~~. Another 0b11111111100x must follow this one to denote the (exclusive) end of the IO range to map.		\| Describes a memory mapping like the 0b111111111110 descriptor, but an entire range rather than a single page is mapped. Another 0b11111111100x descriptor must follow this one to denote the (exclusive) end of the address range to map.
	\|-		\|-
	\| <code>0b111111111110</code>		\| <code>0b111111111110</code>
	\| Map ~~single IO~~ page		\| Map memory page
	\| Bits 0-19: IO page index to map; Bit 20: Map read-only (otherwise read-write)		\| Bits 0-19: page index to map (virtual address >> 12; the physical address is determined by subtracting 0x0EB00000); Bit 20: Map read-only (otherwise read-write)
	\|}		\|}