Skip to main content
NESdev Wiki
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

PPU memory map

PPU memory map

The PPU addresses a 14-bit (16kB) address space, $0000-$3FFF, completely separate from the CPU’s address bus. It is either directly accessed by the PPU itself, or via the CPU with memory mapped registers at $2006 and $2007.

Address rangeSizeDescriptionMapped by
$0000-$0FFF$1000Pattern table 0Cartridge
$1000-$1FFF$1000Pattern table 1Cartridge
$2000-$23BF$03c0Nametable 0Cartridge
$23C0-$23FF$0040Attribute table 0Cartridge
$2400-$27BF$03c0Nametable 1Cartridge
$27C0-$27FF$0040Attribute table 1Cartridge
$2800-$2BBF$03c0Nametable 2Cartridge
$2BC0-$2BFF$0040Attribute table 2Cartridge
$2C00-$2FBF$03c0Nametable 3Cartridge
$2FC0-$2FFF$0040Attribute table 3Cartridge
$3000-$3EFF$0F00UnusedCartridge
$3F00-$3F1F$0020Palette RAM indexesInternal to PPU
$3F20-$3FFF$00E0Mirrors of $3F00-$3F1FInternal to PPU

Hardware mapping

The NES has 2kB of RAM dedicated to the PPU, usually mapped to the nametable address space from $2000-$2FFF, but this can be rerouted through custom cartridge wiring. The mappings above are the addresses from which the PPU uses to fetch data during rendering. The actual devices that the PPU fetches pattern, name table and attribute table data from is configured by the cartridge.

  • $0000-1FFF is normally mapped by the cartridge to a CHR-ROM or CHR-RAM, often with a bank switching mechanism.
  • $2000-2FFF is normally mapped to the 2kB NES internal VRAM, providing 2 nametables with a mirroring configuration controlled by the cartridge, but it can be partly or fully remapped to ROM or RAM on the cartridge, allowing up to 4 simultaneous nametables.
  • $3000-3EFF is usually a mirror of the 2kB region from $2000-2EFF. The PPU does not render from this address range, so this space has negligible utility.
  • $3F00-3FFF is not configurable, always mapped to the internal palette control.

OAM

In addition, the PPU internally contains 256 bytes of memory known as Object Attribute Memory which determines how sprites are rendered. The CPU can manipulate this memory through memory mapped registers at OAMADDR ($2003), OAMDATA ($2004), and OAMDMA ($4014). OAM can be viewed as an array with 64 entries. Each entry has 4 bytes: the sprite Y coordinate, the sprite tile number, the sprite attribute, and the sprite X coordinate.

Address Low NibbleDescription
$0, $4, $8, $CSprite Y coordinate
$1, $5, $9, $DSprite tile #
$2, $6, $A, $ESprite attribute
$3, $7, $B, $FSprite X coordinate

Edit this page on GitHub