225. Ppu write register
Add PPU.write_register(addr, value).
Lesson 225 of 356 · tests/chapter_03_ppu_memory_and_graphics_data/test_225_ppu_write_register.py
File to update
emulator/ppu/ppu.pyMethod to implement
PPU.write_register(addr: int, value: int) -> NoneWhy this step exists
The CPU writes to PPU registers through memory-mapped I/O. When the CPU writes to address $2000, it is not writing RAM; it is updating the PPUCTRL register.
For this step, PPU.write_register receives normalized PPU register addresses in the range $2000-$2007. CpuBus mirroring for $2008-$3FFF will be implemented in a later step.
Writable registers for this simplified stage
$2000 -> ctrl
$2001 -> mask
$2003 -> oam_addr
$2004 -> oam_data / OAMDATA port
$2005 -> scroll
$2006 -> addr
$2007 -> dataNotice that $2002 is intentionally missing.
Why $2002 is not writable: $2002 is PPUSTATUS. From the CPU side, it is read-only. Tests may directly set ppu.status when they need to simulate a status value, but write_register($2002, value) should fail.
One-byte policy
PPU registers are 8-bit. For now, writes should keep only the low byte of the value. This means writing 0x123 stores 0x23.
Suggested implementation pseudocode
def write_register(self, addr: int, value: int) -> None:
value = value & 0xFF
match addr:
case 0x2000:
self.ctrl = value
case 0x2001:
self.mask = value
case 0x2003:
self.oam_addr = value
case 0x2004:
self.oam_data = value
case 0x2005:
self.scroll = value
case 0x2006:
self.addr = value
case 0x2007:
self.data = value
case _:
raise ValueError(...)Future note
Later, $2004/OAMDATA becomes a port into internal OAM sprite memory. At that point, writing $2004 may also increment oam_addr. This early test should not require oam_addr to stay unchanged after an OAMDATA write.
Run this lesson
uv run pytest tests/chapter_03_ppu_memory_and_graphics_data/test_225_ppu_write_register.py -v