Nintendo 64's Hidden Memory: Unveiling the Secret 9th Bit

The Nintendo 64's Hidden Memory Capacity

The Nintendo 64 (N64) has long been known for its 4 MB of RAM, expandable to 8 MB with the Expansion Pak. However, a fascinating discovery reveals that the console actually possesses 4.5 MB of RAM, or 9 MB with the Expansion Pak. This extra half-megabyte of memory is hidden within a secret 9th bit, invisible to most developers and users.

Understanding the 9th Bit

Unlike most computers that use 8-bit memory cells, the N64's memory cells hold 9 bits of information. This additional bit is typically inaccessible to code running on the machine, but it can be utilized through specific hardware quirks.

Why SGI Added the 9th Bit

SGI, the company that designed the N64 hardware, included this extra bit primarily for rendering purposes. The N64's CPU and GPU share the entire memory, and when rendering pixels, the console combines two bytes to form one pixel for TV output.

The Role in Anti-Aliasing

When rendering a triangle onto the screen, the N64 computes the percentage of the screen pixel that the triangle covers. This coverage percentage is stored in two hidden bits and one visible bit, allowing for anti-aliasing by blending the color of previously rendered geometry with the new triangle pixel's color.

Pixel Composition

A single pixel on the N64 contains:

• 5 bits for red
• 5 bits for green
• 5 bits for blue
• 3 bits for coverage

This totals 18 bits per pixel, explaining the presence of the 9th bit in each byte of memory.

Accessing the Hidden Memory

Accessing this hidden memory is not straightforward, but there are methods to read and write to these extra bits.

Reading the Hidden Bits

One method involves using a render mode that utilizes the coverage bits to render a pixel. By reading the rendered pixel, one can deduce the values of the coverage bits. This method is slow but possible.

Writing to the Hidden Bits

Writing to the hidden bits is more complex. One approach involves rendering invisible geometry that only affects the lower two bits of coverage without changing the pixel color. This method is theoretically possible but challenging to implement and may not be supported by most emulators.

The EBUS Mode

A more practical method uses the EBUS mode, typically employed by the RDP and VI when reading or writing 4-byte values. In this mode, the four lowest bits of 4-byte values are mapped onto the four extra bits of memory.

Reading with EBUS

Reading with EBUS is straightforward:

1. Activate EBUS mode
2. Read the value
3. Extract the lower four bits

This method is fast, reliable, and doesn't interfere with other system operations.

Writing with EBUS

Writing with EBUS is more complicated, as it overrides both the hidden and visible bits. This method sacrifices 64 easily accessible bits to gain 8 slower, hidden bits, which is generally impractical.

The CPU Writing Technique

A more useful technique involves writing every other bit of hidden extra memory, allowing access to half a megabyte of extra storage. This method works as follows:

1. Read a two-byte value from memory
2. Set the least significant bit to the desired value
3. Restore the second byte of memory to its original value

This technique successfully sets one bit of extra hidden memory in the first hidden bit of the two bytes.

Practical Applications and Limitations

While the existence of this hidden memory is fascinating, its practical applications are limited due to several factors:

Memory Corruption

The same mechanism that allows access to the hidden bits also leads to potential corruption when reading or writing memory. To use these bits effectively, developers must either carefully restore the state after writing to memory or use read-only memory regions.

Code Storage

One practical application is storing data in the code section of memory, which rarely changes during runtime. This approach prevents corruption of the hidden bits and provides a stable storage solution.

Performance Considerations

Both reading and writing to these hidden areas are slower than accessing normal memory. Therefore, this technique is best suited for data that is infrequently accessed, such as dialogue, save data, or event-triggered information.

Emulator Compatibility

Perhaps the most significant limitation is that no currently released emulator can accurately emulate this behavior. This means that games utilizing this technique would only be playable on original N64 hardware, severely limiting their audience.

Potential Impact on Game Development

For most N64 games, the additional memory provided by this technique may not be necessary. Many games have unused memory space or could be optimized through other means. However, for games that were close to memory bottlenecks, this extra capacity could have been valuable.

Case Study: Donkey Kong 64

Donkey Kong 64 famously required the Expansion Pak due to memory constraints. While the exact reason for this requirement is debated, the additional hidden memory could theoretically have helped with issues like storing multiple vertex lists for dynamic lighting effects.

However, given that Donkey Kong 64 uses more than 7 MB of the N64's memory, the hidden bit technique alone would not have been sufficient to eliminate the need for the Expansion Pak.

Future Implications

While this hidden memory technique is fascinating from a technical standpoint, its practical use in modern N64 development is limited due to emulator incompatibility. However, it showcases the ingenuity of developers and hardware designers in pushing the boundaries of console capabilities.

As emulation technology advances, it's possible that future emulators or FPGA-based systems like the Analogue 3D might accurately replicate this behavior, opening up new possibilities for N64 homebrew development and game preservation.

Conclusion

The discovery of the Nintendo 64's hidden 9th bit memory is a testament to the console's complex architecture and the ongoing efforts of the retro gaming community to uncover its secrets. While the practical applications of this technique are limited in today's emulation-heavy environment, it provides valuable insights into the N64's design and the potential for squeezing every last bit of performance out of classic hardware.

For developers and enthusiasts working directly with N64 hardware, this hidden memory could offer new avenues for optimization and creative problem-solving. As our understanding of retro consoles continues to evolve, we may yet uncover more hidden features and capabilities in the systems that defined gaming history.

The story of the N64's hidden memory serves as a reminder of the importance of hardware exploration and the enduring fascination with pushing technology to its limits. It's a small but significant piece of gaming history that continues to inspire and educate the next generation of developers and hardware enthusiasts.

Article created from: https://youtu.be/DotEVFFv-tk?si=LNNhqrVvNzP4IwV8