Open bus behavior

When the CPU attempts to read from an address which has no devices active, the result is open bus behavior. The value that results from a read in such a region is undefined, but on specific hardware predictable results may appear.

Clone versions of the hardware, and flash cartridges like the PowerPak or Everdrive may differ in their open bus behavior from a standard NES.

CPU open bus

On a standard NES, reading open bus repeats the last value that was read from the bus before this read. Relevant cases:

• Absolute addressed instructions will read the high byte of the address (the last byte of the operand).
• Indexed addressing uses the high byte of the base address read from the instruction's operand; the index register does not yet apply when that value is read.
• Indirect addressing will fetch the high byte of the pointer last. The Y index does not yet apply. See below for an example.
• A DMC DMA may also alter the last value read if it interrupts an instruction.

Open bus can be limited to part of a byte. The controller ports ($4016, $4017) affect only bits 4-0. Bits 7-5 repeat the corresponding bits from the previous read, usually 010 from the high byte $40.

Few games rely on CPU open bus behavior. In most cases of commercial games that do, it seems to be unintentional due to a programming error.

A few games read the region $6000-7FFF but have no WRAM present here. This can be a problem for emulators, as the original iNES file format had no way to specify a lack of WRAM, leaving the emulator to provide WRAM behavior in that region by default. The NES 2.0 format corrects this with a WRAM size field.

Examples

• Low G Man: WRAM instead of open bus behavior may cause a crash in Chapter 1 Scene 3B a few seconds into the boss fight music, or graphical glitches when using the boomerang weapon.
• Battletoads & Double Dragon: At the end of the first level, reads a values from ~$600X when the Abobo boss finished destroying the wall. A value of $00 read here will crash the game.
• Paperboy: Relies on the controller port being exactly $41 for a button press to be recognized.
• Castlevania: Just after the introduction will read a few values from ~$7FFX before the first stage begins. (This is a benign bug: the value read appears to be inconsequential.)

Indirect indexed instruction example

This example will illustrate cycle by cycle the values read by the LDA (indirect), Y instruction.

LDA ($04), Y

• $05,$04 = $73FA
• Y = $31

Cycle	Operation	Read address	Value read
1	read opcode	PC	$B1
2	read operand	PC	$04
3	read low byte of indirection	$0004	$FA
4	read high byte of indirection	$0005	$73
5	read early indirect value	$732B	$73 (open bus)
6	read fixed indirect value	$742B	$73 (open bus)

Note from this example that the open bus behavior always returns the last value read on the data bus. Note that the last byte read before the open bus is the high byte of the indirection pointer. Even though the address of both subsequent reads are affected by Y, both times the open bus will read back the last read value.

PPU open bus

The PPU has two data buses: the I/O bus, used to communicate with the CPU, and the video memory bus. Their open bus behavior differs.

Writes to any PPU port, including the nominally read-only status port at $2002, load a value onto the PPU's I/O bus. Reading a value from $2004 or $2007 loads a byte from OAM, video memory, or the palette onto this bus. Reading the PPU's status port loads a value onto bits 7-5 of the bus, leaving the rest unchanged. Reading any PPU port, including write-only ports $2000, $2001, $2003, $2005, $2006, returns the PPU I/O bus's value.

Open bus on the video memory bus behaves differently. Video memory's data bus is multiplexed with the low byte of the address bus on pins 31 through 38. Thus a read from an address with no memory connected will usually return the low byte of the address. This was used as a limited form of copy protection by a few games using a configuration of CNROM.

Electrical basis

A data bus behaves as a dynamic latch. Once a low or high voltage is placed on each line of the bus, the capacitance of the long traces that make up the data bus allows it to "float" in place to be read again.

Each memory or I/O circuit has a set of pins for enables, or input signals that cause the circuit to take an action when all are in the correct state. For example, a RAM may have /CE1, CE2, and /OE. The / means it is active when the input is low (close to ground voltage); otherwise, it is active high (close to power voltage). Normally, the circuit's three-state outputs are held in a high impedance (hi-Z) state, effectively disconnected from the data bus. Only when all enables are in the correct state (in this case 0, 1, and 0 respectively) does the circuit output a value as voltages to the data bus, erasing the voltages already there.

A circuit called a decoder generates enable signals based on other signals, especially address signals. The 74LS139 decoder in the Control Deck (U3 in the Famicom schematic) decodes the cartridge ROM at $8000-$FFFF, primary work RAM at $0000-$1FFF, and PPU I/O at $2000-$3FFF, based on the CPU's clock divider output (M2) and CPU address bits 15-13. The CPU itself decodes reads of $4015 (APU status) and $4016-$4017 (controller read). But no circuit in the Control Deck decodes reads from $4000-$4014 or $4018-$7FFF. Cartridges with WRAM at $6000-$7FFF contain an additional circuit to decode WRAM, whether by itself or as part of an MMC. But when the CPU reads an address that no circuit decodes, all it sees on its data inputs is whatever was left to float on the data bus.

See also

• Bus conflict