Concept A note on reality: re8 isn't a real product — not yet, anyway. It's a detailed design exercise, and none of this hardware has been built. The partnership shown here is imagined: the companies named have no knowledge of, or involvement in, this project, and all trademarks remain theirs.
the machine · rev 2026
re8 logo

the re8 console

A boutique, ground-up 2D console that marries the zero-emulation, deterministic architecture of the 8-bit era with the pixel-pushing muscle of early-90s arcade silicon — designed around factory-fresh components and one custom chip.

7.16 MHzw65c02s
320×224hi-res mode
128sprites
64colors
16audio voices
130 nmcustom silicon
prog8planned sdk
re8 console, three-quarter view with cartridge inserted
fig. 01 — re8 console with neon drift cartridge seated3/4 view
01

Built like an 8-bit machine. Pushes like an arcade board.

re8 sits deliberately between two eras: the lean, fully-understood bus architecture of the NES and PC Engine, and the raw pixel-pushing muscle of a 1990s arcade PCB. Its design rule is a factory-fresh bill of materials rather than dwindling New Old Stock. Exact ordering codes and lifecycle evidence are still open qualification work for part of that bill of materials.

Zero-emulation

A bare-metal 6502-family core and discrete custom silicon — no soft-cores, no interpretation layer between your code and the hardware.

Factory-fresh BOM target

The console is specified around newly manufactured parts rather than vintage stock. The specification tracks the remaining orderability and lifecycle evidence instead of treating it as settled.

Do it in hardware

Text, the mouse pointer, hit-testing, controller protocols, keyboard decoding — all handled by the chip, so the CPU stays free for your game.

Modern SDK plan

The planned prog8 library, hardware debug probe and WASM emulator bring 2020s ergonomics to an 8-bit bus once their published validation gates close.

02

What's in the box

A quick look at what re8 puts on your screen, through your speakers, and in your hands — no engineering degree required.

a

Graphics

  • Two native resolutions — 256×224 and 320×224 — both progressive 240p at 60Hz.
  • 64 on-screen colors at once, chosen from a 4,096-color master palette.
  • Two independent scrolling backgrounds plus 128 sprites (up to 32 per scanline, also subject to a pattern-fetch budget), with hardware collision detection built into the chip.
  • A mini-blitter for full-screen effects, destructible terrain and procedural graphics.
  • A dedicated text layer floats above the game — crisp menus, dialogue and HUDs that cost you no sprites at all.
b

Sound

  • 16 voices, all playing at once — far beyond a classic chiptune console.
  • 4 enhanced PSG channels (3 pulse + noise) with envelopes and sweep for classic bite.
  • 8 wavetable voices for rich, evolving instruments you design yourself.
  • 4 sample channels — real drums, speech and stingers streamed straight from the cartridge.
  • Designed for 48 kHz stereo digital A/V and a real 1 Vrms analog line-out — 3.5 mm, RCA and SCART. The digital-audio resampler remains an open implementation gate.
c

Play it your way

  • Two front DB9 ports for two-player action, compatible with Sega Genesis / Mega Drive pads — 3-button and 6-button, vintage or modern clones.
  • Plug in a PS/2 keyboard through a simple passive adaptor. Every existing joystick game becomes keyboard-playable automatically — the console maps the keys for you.
  • Plug in a PS/2 mouse and the console draws and moves the pointer itself, in hardware. Strategy, simulation and point-and-click games finally have a home on a machine like this.
  • Gamepads are acquired about every 2.5 ms; keyboard and mouse events follow their PS/2 device-report cadence.
d

Cartridges & saves

  • Real parallel flash cartridges up to 1 MB — code executes in place, with no mandatory ROM-to-RAM preload.
  • Battery-free saves. Saving carts use FRAM, so your progress doesn't die with a coin cell in fifteen years.
  • An optional SD cartridge plays digitally-distributed games and carries firmware updates.
  • The two-stage firmware design covers the logo, self-test, cartridge validation and recovery from a missing or damaged cartridge.
re8 console, cartridge and debug probe together
fig. 02 — the complete system: console, game cartridge, developer debug probefamily
03

A whole machine you can hold in your head

One CPU, one custom chip, and memory you can count on your fingers. The point of re8 isn't scale — it's that a single developer can understand every cycle, every byte and every wire, and still ship something that looks and sounds like an arcade board.

7.16 MHz

W65C02S, synchronous by design

A fully-static CMOS 6502-family CPU clocked at exactly one third of the master clock, so every scanline is an exact 455 CPU cycles. Deterministic timing you can actually plan against.

16 KB

System RAM

Fast asynchronous SRAM on the CPU bus. Small on purpose: the planned SDK build enforces the declared budget at compile time.

128 KB

Video RAM

On a private bus straight into oito, so graphics fetches never fight the CPU for the main bus.

Cartridges that behave like memory

Games live on parallel NOR flash and execute in place — there is no mandatory preload or decompression stage before code can run. A console-side mapper gives you a fixed 16 KB window for your engine and a switchable window for everything else, up to 1 MB per cartridge.

Because the mapper lives in the console rather than the cartridge, a plain retail board needs only the NOR flash and one small inverter. Saving cartridges add FRAM.

Saves that outlive the hardware

Saving cartridges carry FRAM — nonvolatile, effectively unlimited write cycles, and no battery. The classic retro failure, where a dead coin cell takes a childhood save file with it, simply cannot happen here.

Digital titles on the SD cartridge write their saves to the card instead, so both distribution routes behave the same way to the player.

04

Meet oito — the chip that does the work

Every distinctive thing about re8 lives in one custom ASIC targeted to an open 130 nm process. oito is the graphics processor, the sound chip, the cartridge mapper, the input controller and the system glue — and it deliberately takes on jobs that other machines leave to the CPU.

the oito custom ASIC
fig. 03 — oito: one chip for graphics, sound, mapping and inputcustom silicon

Two background planes + 128 sprites

Two independently scrolling 512×256 playfields with per-tile priority and flipping, plus 128 hardware sprites in sizes from 8×8 to 64×64. A line admits up to 32 sprites within a mode-and-scroll-dependent pattern budget of at most 512 bytes. Sprites carry their own priority, so foreground detail can pass in front of one plane and behind another.

Hardware collision

oito compares opaque sprite pixels as it draws the line and reports the exact pair that touched — no bounding boxes, no per-frame CPU sweeps, no false positives on transparent pixels.

A text layer, free of charge

A dedicated character layer composites above everything else, with its own font in the chip. Menus, dialogue boxes, subtitles and debug overlays cost zero sprites and zero tile budget — and a game can load its own typeface. 40 columns, or 80 in condensed mode.

A mouse pointer drawn in silicon

Give oito a cursor graphic once and it owns the rest: reading the mouse, moving the pointer, clamping it to the screen and compositing it above every layer. Your game just receives move and click events.

Ask what's under the pointer

Hardware hit-testing reports which sprite and which background tile sit beneath the cursor. What would be a per-click search loop on other machines is a register read here — the difference between a sluggish strategy game and a responsive one.

16-voice audio unit

PSG, wavetable and sampled voices on one die, mixed internally at 47,940.3 Hz. Samples stream directly from the cartridge, so speech and real drums do not consume system RAM; conversion to nominal 48 kHz belongs only to the digital output path.

Mini-blitter

A VRAM-to-VRAM engine for copies, fills and masked draws that runs alongside the display, enabling destructible terrain and procedural graphics without hand-rolled CPU loops.

Input, protocols included

The Sega 6-button handshake and the PS/2 keyboard and mouse protocols are all implemented in hardware. Game code reads buttons, characters and pointer coordinates — never wire protocols.

oito is specified for an open-source flow against the SkyWater 130 nm PDK and a custom-pad-ring LQFP-176 package. It has not been fabricated. Full register map, data formats and timing →

05

Every screen, every era — at the same time

The design fans one video pipeline out to every output simultaneously. No mode switch or re-plugging is intended: an analog display and a compatible 1080p60 digital display can be connected at once.

Digital-output status. The design targets a licensed HDMI 1.4b source, but adopter registration, compliance testing, CH7035B qualification and the 47,940.3→48,000 Hz audio-resampler design are still open gates. Until they close, digital picture and sound are design targets rather than demonstrated product capabilities.
OutputConnectorBest for
Digital A/V19-pin Type-AA compatible 1080p60 TV or monitor — fixed 1080p60 nearest-neighbour video, targeting licensed HDMI 1.4b with 48 kHz stereo sound on the same cable once the open gates above close.
RGB SCARTEuro-SCARTEuropean CRTs, PVMs and premium upscalers — the enthusiast's choice.
Analog RGBHVDE-1515 kHz-capable monitors and upscalers such as the OSSC or RetroTINK. Not standard VGA timing.
S-Video4-pin mini-DINA noticeably sharper picture on any classic set that supports it.
CompositeRCAPlugs into essentially any television ever made.
Analog audio3.5 mm + RCA + SCART1 Vrms line-out through a 3rd-order active reconstruction filter, on a 3.5 mm line-output connector, an RCA pair and the SCART audio pins. It is not a headphone output.
re8 rear-panel concept showing the video connectors and DC input
fig. 04 — rear-panel concept: digital A/V, RGB 15kHz, RGB SCART, S-Video, composite and DC input; the current analog-audio connector layout is not represented in this renderrear panel

60Hz everywhere

re8 runs at 60Hz worldwide. There is no PAL slowdown, no region-locked timing, and no 50Hz version of a game that plays 17% slower than the developer intended.

Pixel-art-first scaling

The digital-output requirement is nearest-neighbour with no interpolation. Integer factors are preferred, but a non-integer nearest-neighbour scale is permitted if the selected scaler needs it.

240p, properly

Progressive 240p — never interlaced — so scrolling stays rock-solid on a CRT and clean through a modern upscaler.

06

Pads, keyboards and mice — all on two ports

re8 is designed for ordinary Sega Genesis controllers, and the same two ports accept a PS/2 keyboard or mouse through a passive adaptor — no powered dongle, no USB stack, no firmware to flash. It's what turns a console into a machine that can also run strategy games, simulations and text adventures.

Genesis pads, both kinds

3-button and 6-button pads, vintage or modern reproductions. The console performs the full 6-button handshake itself and tells the game which pad it found.

Keyboard, and every game supports it

The console maps arrow keys and letters onto the joypad registers below the game — so titles written years earlier become keyboard-playable with no patch and no cooperation from the developer.

Mouse, drawn by the console

The pointer is composited by oito above every layer. Games get coordinates and clicks; nobody spends sprites or CPU time drawing a cursor.

The re8 edition accessories

Three imagined re8 editions based on 8BitDo accessories, finished in the re8 palette. Each concept includes a 2.4G wireless receiver shaped as a Genesis-style plug — it drops into either controller port, and for the keyboard and mouse it speaks the console's native PS/2 protocol, so oito handles the device directly in hardware.

Imagined partnership. 8BitDo has no involvement in this project and has not been approached. These are concept renders, not products.
M30 2.4G re8 edition gamepad, front and side views
fig. 05M30 2.4G re8 edition · six-button Genesis layout, 2.4G wireless, re8 mark above Startgoogle gemini · from original product photos
8BitDo Retro Keyboard re8 edition with its Genesis-plug 2.4G receiver
fig. 068BitDo Retro Keyboard re8 edition · mechanical TKL with A/B keys; the 2.4G receiver is a Genesis plug speaking PS/2google gemini · from original product photos
8BitDo Retro Mouse re8 edition
fig. 078BitDo Retro Mouse re8 edition · scroll wheel and thumb buttons; same Genesis-plug PS/2 receivergoogle gemini · from original product photos

One receiver, either port

The dongle is a Genesis-shaped plug, so it goes into the same DB9 port a pad would use. No adaptor, no console-side setting beyond choosing the port's mode.

Wireless, but native

The receiver presents the keyboard or mouse to the console exactly as a wired PS/2 device would — so oito decodes scancodes and moves the pointer in hardware, with no device-protocol driver in game code.

Finished in re8 colours

Cream shells with brand-teal accents, matched to the console. The pixel-eight mark sits above Start on the pad, and on the shell of every receiver.

Why this matters

Genres that never fitted an 8-bit console — 4X and grand strategy, city and colony builders, point-and-click adventures, tycoon and management games, even a BASIC-style prompt — need a pointer and a text field far more than they need sprites.

re8 provides both in hardware, so those games are natural to write rather than heroic.

Honest limits

There are two ports, so a keyboard or mouse occupies one of them: joystick + keyboard, joystick + mouse, or keyboard + mouse — not all three at once.

Devices are PS/2, not USB. The adaptor is passive wiring, and a port is set to keyboard or mouse mode from the console's own settings screen.

07

A window into the running machine

An unpopulated 42-pin header on the planned board exposes the entire CPU bus and the chip's JTAG interface. With the connector fitted, the re8 debug probe is designed to turn a console with no operating system into something you can single-step.

the re8 debug probe
fig. 08 — the re8 debug probe: USB-C to the host, ribbon cable to the expansion headerdebug probe

Hardware breakpoints

The probe watches the address bus and halts the CPU on the instruction you named — no debug code in your ROM, no performance cost, and the game runs at full speed right up to the moment it stops.

Single-step a static CPU

Because the 65C02 is fully static, the clock can be stopped entirely and advanced one cycle at a time with the machine's state perfectly preserved.

Develop without burning ROM

A writable dev cartridge is filled directly by the probe over the header; tiny test programs can instead run from system RAM. Neither path requires burning a production cartridge.

08

Write structured code. Ship native 6502.

The planned re8 SDK uses prog8 — a structured, Python-flavoured language for the 6502 family that compiles to assembly with static allocation and no garbage collector. The planned library above it is event-driven, while the hardware underneath it removes much of the protocol and rendering work that makes 8-bit development tedious.

SDK status. prog8 can emit 65C02 code, but re8's ROM-resident multi-bank build, initialised-data transformation, IRQ-safety analysis, debug-information path and conformance fixtures are not implemented or validated yet. The examples below show the intended API, not a released SDK.

Static by design

No heap, no dynamic arrays, no garbage collector. Every variable has a fixed address at compile time, and the build fails if you exceed the RAM budget — you learn at build time, not at 3am.

Zero-overhead calls

Arguments live in static cells rather than on a stack, so a call often compiles to a single STA. Ordinary subroutines are non-reentrant as a result — an honest reflection of what the silicon does.

Dead-code elimination

Unused library routines never reach the ROM. Link only the input handlers and you pay only for the input handlers.

main.prg

The hardware does the boring parts

Three things that normally consume weeks of an 8-bit project are handled by oito, and reach your code as ordinary events.

Text without a tile engine

Print to a character layer that floats above the game. No font blitting, no tile allocation, no sprite budget — and dialogue boxes are a rectangle of opaque cells, drawn by the chip.

A cursor you never draw

Set the pointer graphic once. oito reads the mouse, moves the pointer, clamps it and composites it. You handle on_move and on_button — nothing else.

Click-to-object, for free

Hardware hit-testing tells you which sprite and which map tile are under the pointer. No coordinate maths, no scroll compensation, no per-object loop.

strategy.prg
events.prg

A debugger plan for a machine with no OS

the re8 VS Code extension debugging a running game
fig. 09 — paused at a collision breakpoint: code, variables, VRAM inspector and emulator in one viewvs code

console.log(), for real hardware

Address $4FFF is a write-only "ghost port" with no backing memory. Writing to it costs 4 cycles and does nothing unless a probe or the emulator is listening — so debug logging can ship in production builds while streaming live text to your editor during development.

Source-level debugging

The planned toolchain turns listing and symbol data into the information VS Code needs for breakpoints and stepping against original prog8 source lines; its exact debug-info path remains a validation gate.

Live VRAM inspector

The planned inspector presents a scrollable grid of loaded tiles, palette overlays, sprite state and active-scanline highlighting through the emulator or physical probe.

Emulator in the editor

The planned hot-reloading WASM emulator runs inside a VS Code panel and shares debug hooks with the physical probe; an immediate console can inspect or change a halted machine.

the re8 system family

Build for hardware that respects the constraint.

re8 is a manufacturability-driven console design, not manufactured hardware. It combines a factory-fresh BOM target, an open-process custom chip and a planned toolchain so an 8-bit machine need not feel like 1985 to develop for.