Skip to content

Triforce (Sega / Nintendo / Namco)

A rare joint venture (2002): Sega + Nintendo + Namco around a GameCube motherboard (Japanese DOL-001) + a NAOMI-style media system. Mario Kart Arcade GP, F-Zero AX, Virtua Striker… Long hard to preserve — until Triforce support in Dolphin.

Identification

Field Value
Manufacturers Sega + Nintendo + Namco (joint venture)
Year 2002
Base Nintendo GameCube (NTSC-J DOL-001 motherboard, modified IPL)
Media GD-ROM (DIMM variant) loaded into RAM; cartridge variants
I/O JVS

Architecture (≈ GameCube)

Block Chip Role
CPU PowerPC Gekko GameCube base
GPU ATI/ArtX Flipper 3D rendering
Media media board (DIMM) + GD-ROM data loaded into RAM on first boot
Boot modified IPL (arcade) starts the arcade system
I/O JVS arcade controls

Most games target the DIMM variant: the game ships on GD-ROM and loads into RAM on first boot. Sega designed the board to reuse its arcade GD-ROM drives (a generic SCSI connector, like NAOMI/Chihiro).

Security & preservation

  • Media board (DIMM): hardware pairing + battery, logic close to the NAOMI.
  • Emulation: Dolphin (the GameCube/Wii emulator) has added Triforce support — a major advance, preservation directly benefiting from the GameCube ecosystem.
  • Priority: image the GD-ROMs and back up the media board's data.

Notable games

Mario Kart Arcade GP (1/2, with Namco/Bandai), F-Zero AX (2003), Virtua Striker 2002 / Virtua Striker 4, Gekitou Pro Yakyuu, The Key of Avalon (1/2)…

The F-Zero AX ↔ GX bridge

F-Zero GX (GameCube) and F-Zero AX (Triforce) are twins: plugging a GameCube controller + memory card into an AX cabinet unlocks content in GX (and vice versa) — a perfect illustration of the hardware kinship.

Faults & repair

GameCube-class hardware → GameCube repairs apply + arcade specifics:

Symptom Likely cause Lead
Won't boot media/DIMM board, battery, IPL Media-board diagnosis; image
GD not read Worn GD-ROM drive Repair/image; SD solutions
Reboots PSU capacitors Recap
Dead controls JVS I/O / harness JVS diagnosis

Modernisation & mods

The common ground for every JAMMA board

Video, power, control panel and upscalers depend on the cabinet rather than the board: everything is centralised in Modernising a cabinet. To run the board outside a cabinet (at home, on a display): supergun.

  • Battery 🟢: a save battery is fitted (settings/counters/RTC). A leaking battery corrodes traces — check and replace it before it leaks → save batteries.
  • Optical storage 🟡: the drive is the number-one wear part. Modern routes: an ODE, netboot, or replacement by flash storage depending on the platform → PCB preservation hub.
  • Scan rate 📺: derived from a home console (see the architecture above): 480i/480p output, i.e. ~15.7 kHz interlaced and ~31.5 kHz progressive. ⚠️ A 15 kHz chassis only covers the interlaced mode — plan for a tri-sync. (Derived from the platform, not measured from MAME.)tri-sync and upscalers.
  • FPGA / emulation: see the Emulation & FPGA section below.

Repair (technician)

  • GameCube base (DOL-001): the same faults as a GameCube (recap, PSU, DOL chip).
  • DIMM board: content loaded into RAM on first boot (battery → reload); media board.
  • GD-ROM: drive/laser → ODE mods.
  • Capacitors: recap.

Methods: PCB fault-finding · Recap · Backup batteries · Traces & vias

Emulation & FPGA

  • Emulation: Dolphin (Triforce support) — the preservation route.
  • FPGA / MiSTer: no core (a full GameCube, out of budget).
  • Preservation & modernisation (GD-ROM/netboot, no-battery).

Lineage

A console-based cousin of the Chihiro (Xbox); on the console side, see the GameCube. Contemporary with the NAOMI.

Photos / assets

(To add: Triforce board, media/DIMM board, GD-ROM drive, JVS I/O.)

Sources & attribution

Review & corrections

How this space is used

Spotted a wrong value, an outdated procedure, a chip reference that does not match your board? Say so here, with what you observed (model, board revision, serial number, measurement). Every report is cross-checked against a source before anything changes — an unverifiable correction is published as “reported by …, not cross-checked” rather than silently applied.

Reading is open to everyone; posting requires signing in with Discord. Reports from the wiki's declared reviewers are handled first; anyone else's are read too, but go through a human before anything is changed.