Platforms

Where each console toolchain stands, which ones are practical today, and which ones are still research.

These pages explain the console toolchains.

They are not all at the same maturity level. Some are practical starting points. Some are useful examples. Some are research projects that teach us about the next version of the tooling.

If you are trying your first port, start with the strongest path.

The strongest paths

• PlayStation. The gold-standard framework today. It has the clearest end-to-end path, a strong runtime, and the best example of how this ecosystem should feel.
• SNES. The silver-standard framework. It has strong results and very useful lessons, especially around assembly-heavy games and community disassemblies.

Useful but earlier

• NES. A compact cartridge system where code discovery and mapper handling are the main lessons.
• Game Boy Advance. Experimental. Able to run games with enhancements, but still needs refinement.
• Sega Genesis. Experimental two-CPU target. Useful for native 68000 work plus Z80 sound work.
• Master System and Game Gear. Experimental Z80 target. Useful for timing work, but not the first place to start.
• Nintendo DS. Early and experimental. Able to run commercial titles, but still needs optimization and refinement.

Research

• CD-i. Research path around full system ROM behavior, not a normal game-port route.
• Virtual Boy. Focused experimental target for one narrow runtime.

How should I read these pages?

Read each page as a maturity snapshot, not a guarantee.

A console page can tell you what the framework is trying to do, what makes that console hard, and what kind of files a project may ask for. It cannot promise that every game on that console is ready.

For the general workflow, start with How do I recomp my own game?. For exact status words, use Status vocabulary.