NAND - Revision history

PoroCYon at 17:11, 18 December 2022

2022-12-18T16:11:30Z

← Older revision		Revision as of 19:11, 18 December 2022
Line 10:		Line 10:
	\| 0 \|\| 0x200 \|\| PC-style Master Boot Record (MBR), encrypted with a per-console key		\| 0 \|\| 0x200 \|\| PC-style Master Boot Record (MBR), encrypted with a per-console key
	\|-		\|-
	\| 0x200 \|\| 0x200 \|\| Stage 2 info block 1 (see [[~~Bootloader~~]])		\| 0x200 \|\| 0x200 \|\| Stage 2 info block 1 (see [[stage2]])
	\|-		\|-
	\| 0x400 \|\| 0x200 \|\| Stage 2 info block 2		\| 0x400 \|\| 0x200 \|\| Stage 2 info block 2

Nocash at 13:52, 16 July 2013

2013-07-16T11:52:51Z

← Older revision		Revision as of 15:52, 16 July 2013
Line 8:		Line 8:
	! Offset !! Size !! Description		! Offset !! Size !! Description
	\|-		\|-
	\| 0 \|\| 0x200 \|\| PC-style MBR, encrypted with a per-console key		\| 0 \|\| 0x200 \|\| PC-style Master Boot Record (MBR), encrypted with a per-console key
	\|-		\|-
	\| 0x200 \|\| 0x200 \|\| Stage 2 info block 1 (see ~~below~~)		\| 0x200 \|\| 0x200 \|\| Stage 2 info block 1 (see [[Bootloader]])
	\|-		\|-
	\| 0x400 \|\| 0x200 \|\| Stage 2 info block 2		\| 0x400 \|\| 0x200 \|\| Stage 2 info block 2

Neimod at 21:58, 2 September 2009

2009-09-02T19:58:24Z

← Older revision		Revision as of 23:58, 2 September 2009
Line 1:		Line 1:
	The DSi uses a 256MB Samsung moviNAND flash chip, which is a NAND flash chip with a built-in controller that implements a MMC (SDIO) interface. In many ways, it's like an SD card in BGA packaging, and some people have successfully read it with modified SD card readers.		The DSi uses a 256MB Samsung moviNAND flash chip, which is a NAND flash chip with a built-in controller that implements a MMC (SDIO) interface. In many ways, it's like an SD card in BGA packaging, and some people have successfully read it with modified SD card readers. The last 16MB is used for wear-leveling purposes (such as replacing bad blocks), while the first 240MB is used for storing actual data.

	Addressing is done in terms of 512-bytes sectors. All wear-levelling and bad-block-mapping is handled transparently inside the chip by the controller. Most sectors are encrypted with a per-console key.		Addressing is done in terms of 512-bytes sectors. All wear-levelling and bad-block-mapping is handled transparently inside the chip by the controller. Most sectors are encrypted with a per-console key.

Scanlime: Add partition starts, note that diag area is blank straight from factory.

2009-08-31T18:15:51Z

Add partition starts, note that diag area is blank straight from factory.

← Older revision		Revision as of 22:15, 31 August 2009
Line 22:		Line 22:
	\| 0x4E800 \|\| ? \|\| Unused (all 00)		\| 0x4E800 \|\| ? \|\| Unused (all 00)
	\|-		\|-
	\| 0xffa00 \|\| 0x400 \|\| ~~Factory test~~ area (often contains build date of device in plaintext)		\| 0xffa00 \|\| 0x400 \|\| Diagnostic area. (often contains build date of device in plaintext) Blank in never-before-booted DSi. Might be written to during firmware updates.
	\|-		\|-
	\| 0x10ee00 \|\| ? \|\| ~~start~~ of ~~per~~-~~console unique encrypted data~~		\| 0x10ee00 \|\| ? \|\| First sector of main FAT32 partition
			\|-
			\| 0xcf09a00 \|\| ? \|\| First sector of photo FAT32 partition
	\|}		\|}

Bushing: page creation

2009-08-31T18:00:38Z

page creation

New page

The DSi uses a 256MB Samsung moviNAND flash chip, which is a NAND flash chip with a built-in controller that implements a MMC (SDIO) interface. In many ways, it's like an SD card in BGA packaging, and some people have successfully read it with modified SD card readers.

Addressing is done in terms of 512-bytes sectors. All wear-levelling and bad-block-mapping is handled transparently inside the chip by the controller. Most sectors are encrypted with a per-console key.

Layout:

{| border="1" cellpadding="3" cellspacing="0"
! Offset !! Size !! Description
|-
| 0 || 0x200 || PC-style MBR, encrypted with a per-console key
|-
| 0x200 || 0x200 || Stage 2 info block 1 (see below)
|-
| 0x400 || 0x200 || Stage 2 info block 2
|-
| 0x600 || 0x200 || Stage 2 info block 3
|-
| 0x800 || 0x4DC00 || Stage 2 bootloader (encrypted with a universal key)
|-
| 0x4E400 || 0x400 || Stage 2 footer -- unknown format, but first 10 bytes are build number of Stage 2 bootloader
|-
| 0x4E800 || ? || Unused (all 00)
|-
| 0xffa00 || 0x400 || Factory test area (often contains build date of device in plaintext)
|-
| 0x10ee00 || ? || start of per-console unique encrypted data
|}