Talk:NCSD - Revision history

Yellows8 at 02:58, 28 June 2013

2013-06-28T00:58:12Z

← Older revision		Revision as of 04:58, 28 June 2013
Line 33:		Line 33:
	\|}		\|}

	This CVer titleID/title-version is from the CVer [[CIA]] stored in the [[System Update CFA]]. ~~The 3DS~~ reads this 0x200-byte block from offset 0x200 in the NCSD image, however the CVer fields are not used.		This CVer titleID/title-version is from the CVer [[CIA]] stored in the [[System Update CFA]]. With newer NATIVE_FIRM versions the system reads this 0x200-byte block from offset 0x200 in the NCSD image, however the CVer fields are not used.

	:Old Version? Is this not present in new retail game dumps?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		:Old Version? Is this not present in new retail game dumps?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)

Yellows8 at 02:54, 28 June 2013

2013-06-28T00:54:33Z

← Older revision		Revision as of 04:54, 28 June 2013
Line 33:		Line 33:
	\|}		\|}

	This CVer titleID/title-version is from the CVer [[CIA]] stored in the [[System Update CFA]], however ~~these~~ fields ~~seem to be never~~ used ~~on 3DS~~.		This CVer titleID/title-version is from the CVer [[CIA]] stored in the [[System Update CFA]]. The 3DS reads this 0x200-byte block from offset 0x200 in the NCSD image, however the CVer fields are not used.

	:Old Version? Is this not present in new retail game dumps?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		:Old Version? Is this not present in new retail game dumps?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)

Yellows8 at 00:34, 13 June 2013

2013-06-12T22:34:46Z

← Older revision		Revision as of 02:34, 13 June 2013
Line 26:		Line 26:
	\| 0x320		\| 0x320
	\| 8		\| 8
	\| [[~~NVer~~]] Title ID (Only Present in retail .CCI)		\| [[CVer]] Title ID (Only Present in retail .CCI)
	\|-		\|-
	\| 0x328		\| 0x328
	\| 8		\| 8
	\| [[~~NVer~~]] Title Version (Only Present in retail .CCI)		\| [[CVer]] 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~~.		This CVer titleID/title-version is from the CVer [[CIA]] stored in the [[System Update CFA]], however these fields seem to be never used on 3DS.

	:Old Version? Is this not present in new retail game dumps?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		:Old Version? Is this not present in new retail game dumps?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)

3dsguy: sometimes I can sound like a retard :/

2013-04-10T22:46:19Z

sometimes I can sound like a retard :/

← Older revision		Revision as of 02:46, 11 April 2013
Line 1:		Line 1:
	The ExHeader Sha-256 hash and ExHeader Size for the NCSD header is always zero, why?--[[User:3dsguy\|3dsguy]] 07:33, 28 July 2012 (CEST)		The ExHeader Sha-256 hash and ExHeader Size for the NCSD header is always zero, why?--[[User:3dsguy\|3dsguy]] 07:33, 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)
	::"I'm also finding your updates not always accurate because you are working only with development files" Well, while I was making mods for 3DSExplorer specifically the NCSD module, I noticed that there was an extra section at 0x1000 bytes in the retail .CCI I had been testing by mods with. This had not been documented on 3DBrew, so to see what all this was about, I built a CCI with a developer CCI maker, BOTH retail and dev CCI followed the format of titleID, reserved(8), 'Initial data'(this section might be different to retail but uses the same amount of space.), reserved(c0), copied from executable NCCH, Reserved/not used(on retail CCIs this was filled with 'F's for the debug CCI I built, this was filled with '0's). So they were both 0x200 in size, if you ignore the filling out to offset 0x4000. Checking now, Nintendo Development CSU files, the card info header is bigger. But the point being I followed many retail .CCIs and one dev CCI(which was quite similar to retail format) for describing the format. After checking your fix up on the NCSD page, my documentation of the structure of the region 0x1000-0x1200 for retail was correct. --[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)
	~~::"I'm also finding your updates not always accurate because you are working only with development files" What else have I got wrong?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)~~

	Old version:		Old version:

3dsguy at 06:59, 29 July 2012

2012-07-29T04:59:49Z

← Older revision		Revision as of 08:59, 29 July 2012
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)
	::"I'm also finding your updates not always accurate because you are working only with development files" Well, while I was making mods for 3DSExplorer specifically the NCSD module, I noticed that there was an extra section at 0x1000 bytes in the retail .CCI I had been testing by mods with. This had not been documented on 3DBrew, so to see what all this was about, I built a CCI with a developer CCI maker, BOTH retail and dev CCI followed the format of titleID, reserved(8), 'Initial data'(this section might be different to retail but uses the same amount of space.), reserved(c0), copied from executable NCCH, Reserved/not used(on retail CCIs this was filled with 'F's for the debug CCI I built, this was filled with '0's). So they were both 0x200 in size, if you ignore the filling out to offset 0x4000. Checking now, Nintendo Development CSU files, the card info header is bigger. But the point being I followed many retail .CCIs and one dev CCI(which was quite similar to retail format) for describing the format. After checking your fix up on the NCSD page, my documentation of the region 0x1000-0x1200 for retail was correct. --[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		::"I'm also finding your updates not always accurate because you are working only with development files" Well, while I was making mods for 3DSExplorer specifically the NCSD module, I noticed that there was an extra section at 0x1000 bytes in the retail .CCI I had been testing by mods with. This had not been documented on 3DBrew, so to see what all this was about, I built a CCI with a developer CCI maker, BOTH retail and dev CCI followed the format of titleID, reserved(8), 'Initial data'(this section might be different to retail but uses the same amount of space.), reserved(c0), copied from executable NCCH, Reserved/not used(on retail CCIs this was filled with 'F's for the debug CCI I built, this was filled with '0's). So they were both 0x200 in size, if you ignore the filling out to offset 0x4000. Checking now, Nintendo Development CSU files, the card info header is bigger. But the point being I followed many retail .CCIs and one dev CCI(which was quite similar to retail format) for describing the format. After checking your fix up on the NCSD page, my documentation of the structure of the region 0x1000-0x1200 for retail was correct. --[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)
	::"I'm also finding your updates not always accurate because you are working only with development files" What else have I got wrong?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		::"I'm also finding your updates not always accurate because you are working only with development files" What else have I got wrong?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)

3dsguy at 01:50, 29 July 2012

2012-07-28T23:50:42Z

← Older revision		Revision as of 03:50, 29 July 2012
Line 4:		Line 4:
	: 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)
	::"I'm also finding your updates not always accurate because you are working only with development files" Well, while I was making mods for 3DSExplorer specifically the NCSD module, I noticed that there was an extra section at 0x1000 bytes in the retail .CCI I had been testing by mods with. This had not been documented on 3DBrew, so to see what all this was about, I built a CCI with a developer CCI maker, BOTH retail and dev CCI followed the format of titleID, reserved(8), 'Initial data'(this section might be different to retail but uses the same amount of space.), reserved(c0), copied from executable NCCH, Reserved/not used(on retail CCIs this was filled with 'F's for the debug CCI I built, this was filled with '0's). So they were both 0x200 in size, if you ignore the filling out to offset 0x4000. Checking now, Nintendo Development CSU files, the card info header is bigger. But the point being I followed many retail .CCIs and one dev CCI(which was quite similar to retail format) for describing the format. After checking your fix up on the NCSD page, my documentation of the region 0x1000-0x1200 for retail was correct. --[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		::"I'm also finding your updates not always accurate because you are working only with development files" Well, while I was making mods for 3DSExplorer specifically the NCSD module, I noticed that there was an extra section at 0x1000 bytes in the retail .CCI I had been testing by mods with. This had not been documented on 3DBrew, so to see what all this was about, I built a CCI with a developer CCI maker, BOTH retail and dev CCI followed the format of titleID, reserved(8), 'Initial data'(this section might be different to retail but uses the same amount of space.), reserved(c0), copied from executable NCCH, Reserved/not used(on retail CCIs this was filled with 'F's for the debug CCI I built, this was filled with '0's). So they were both 0x200 in size, if you ignore the filling out to offset 0x4000. Checking now, Nintendo Development CSU files, the card info header is bigger. But the point being I followed many retail .CCIs and one dev CCI(which was quite similar to retail format) for describing the format. After checking your fix up on the NCSD page, my documentation of the region 0x1000-0x1200 for retail was correct. --[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)
	::"I'm also finding your updates not always accurate you are working only with development files" What else have I got wrong?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		::"I'm also finding your updates not always accurate because you are working only with development files" What else have I got wrong?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)

	Old version:		Old version:

3dsguy at 01:48, 29 July 2012

2012-07-28T23:48:33Z

← Older revision		Revision as of 03:48, 29 July 2012
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)
			::"I'm also finding your updates not always accurate because you are working only with development files" Well, while I was making mods for 3DSExplorer specifically the NCSD module, I noticed that there was an extra section at 0x1000 bytes in the retail .CCI I had been testing by mods with. This had not been documented on 3DBrew, so to see what all this was about, I built a CCI with a developer CCI maker, BOTH retail and dev CCI followed the format of titleID, reserved(8), 'Initial data'(this section might be different to retail but uses the same amount of space.), reserved(c0), copied from executable NCCH, Reserved/not used(on retail CCIs this was filled with 'F's for the debug CCI I built, this was filled with '0's). So they were both 0x200 in size, if you ignore the filling out to offset 0x4000. Checking now, Nintendo Development CSU files, the card info header is bigger. But the point being I followed many retail .CCIs and one dev CCI(which was quite similar to retail format) for describing the format. After checking your fix up on the NCSD page, my documentation of the region 0x1000-0x1200 for retail was correct. --[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)
			::"I'm also finding your updates not always accurate you are working only with development files" What else have I got wrong?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)

	Old version:		Old version:
Line 37:		Line 39:

	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.		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.

			:Old Version? Is this not present in new retail game dumps?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)

Neimod at 19:48, 28 July 2012

2012-07-28T17:48:34Z

← Older revision		Revision as of 21:48, 28 July 2012
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.

Neimod at 19:23, 28 July 2012

2012-07-28T17:23:03Z

← Older revision		Revision as of 21:23, 28 July 2012
Line 2:		Line 2:

	@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. --[[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)

Neimod at 18:52, 28 July 2012

2012-07-28T16:52:09Z

← Older revision		Revision as of 20:52, 28 July 2012
Line 2:		Line 2:

	@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. --[[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. --[[User:Neimod\|Neimod]] 20:46, 28 July 2012 (CEST)

← Older revision		Revision as of 08:59, 29 July 2012
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)
	::"I'm also finding your updates not always accurate because you are working only with development files" Well, while I was making mods for 3DSExplorer specifically the NCSD module, I noticed that there was an extra section at 0x1000 bytes in the retail .CCI I had been testing by mods with. This had not been documented on 3DBrew, so to see what all this was about, I built a CCI with a developer CCI maker, BOTH retail and dev CCI followed the format of titleID, reserved(8), 'Initial data'(this section might be different to retail but uses the same amount of space.), reserved(c0), copied from executable NCCH, Reserved/not used(on retail CCIs this was filled with 'F's for the debug CCI I built, this was filled with '0's). So they were both 0x200 in size, if you ignore the filling out to offset 0x4000. Checking now, Nintendo Development CSU files, the card info header is bigger. But the point being I followed many retail .CCIs and one dev CCI(which was quite similar to retail format) for describing the format. After checking your fix up on the NCSD page, my documentation of the region 0x1000-0x1200 for retail was correct. --[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		::"I'm also finding your updates not always accurate because you are working only with development files" Well, while I was making mods for 3DSExplorer specifically the NCSD module, I noticed that there was an extra section at 0x1000 bytes in the retail .CCI I had been testing by mods with. This had not been documented on 3DBrew, so to see what all this was about, I built a CCI with a developer CCI maker, BOTH retail and dev CCI followed the format of titleID, reserved(8), 'Initial data'(this section might be different to retail but uses the same amount of space.), reserved(c0), copied from executable NCCH, Reserved/not used(on retail CCIs this was filled with 'F's for the debug CCI I built, this was filled with '0's). So they were both 0x200 in size, if you ignore the filling out to offset 0x4000. Checking now, Nintendo Development CSU files, the card info header is bigger. But the point being I followed many retail .CCIs and one dev CCI(which was quite similar to retail format) for describing the format. After checking your fix up on the NCSD page, my documentation of the structure of the region 0x1000-0x1200 for retail was correct. --[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)
	::"I'm also finding your updates not always accurate because you are working only with development files" What else have I got wrong?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)		::"I'm also finding your updates not always accurate because you are working only with development files" What else have I got wrong?--[[User:3dsguy\|3dsguy]] 03:48, 29 July 2012 (CEST)