Difference between revisions of "PPU"

From Nesdev wiki
Jump to: navigation, search
m
m
Line 13: Line 13:
  
 
=== Hardware behaviors ===
 
=== Hardware behaviors ===
* [[PPU_ntsc_pal_difference|NTSC/PAL differences]]
+
* [[PPU_frame_timing|Frame timing]]
 
* [[PPU_power_up_state|Power up state]]
 
* [[PPU_power_up_state|Power up state]]
 
* [[NMI|NMI]]
 
* [[NMI|NMI]]
 +
* [[PPU_ntsc_pal_difference|NTSC/PAL differences]]
  
  
 
=== Notes ===
 
=== Notes ===
 
* The NTSC video signal is made up of 262 scanlines, and 20 of those are spent in vblank state. After the program has received an NMI, it has about 2270 cycles to update the palette, sprites, and nametables as necessary before rendering begins.
 
* The NTSC video signal is made up of 262 scanlines, and 20 of those are spent in vblank state. After the program has received an NMI, it has about 2270 cycles to update the palette, sprites, and nametables as necessary before rendering begins.

Revision as of 07:58, 11 June 2009

The NES PPU, or Picture Processing Unit, generates a composite video signal with 240 lines of pixels, designed to be received by a television. When the Famicom chipset was designed in the early 1980s, it was considered quite an advanced 2D picture generator for video games.

It has its own address space, which typically contains 10 kilobytes of memory: 8 kilobytes of ROM or RAM on the Game Pak (possibly more with one of the common Mappers) to store the shapes of background and sprite tiles, plus 2 kilobytes of RAM in the console to store a map or two. Two separate, smaller address spaces hold a palette, which controls which colors are associated to various indices, and OAM (Object Attribute Memory), which stores the position, orientation, shape, and color of the sprites, or independent moving objects. These are internal to the PPU itself and use dynamic memory (which will slowly decay if the PPU is not rendering data).


Programmer's reference (printer friendly)

Hardware behaviors


Notes

  • The NTSC video signal is made up of 262 scanlines, and 20 of those are spent in vblank state. After the program has received an NMI, it has about 2270 cycles to update the palette, sprites, and nametables as necessary before rendering begins.