I'm specifically interested in the Sega Mega Drive/Genesis, which used a 68000 CPU, but also a Z80, mainly used to control the sound hardware and provide backward compatibility with the Master System.

There was also the Atari Jaguar, with it's Tom and Jerry RISC chips, the Sega Saturn, Featuring a total of eight processors, and probably a lot more.

When writing code (assuming ASM), how would these additional processors be used/accessed? Did one write regular 68000 code (even for sound) and the 68000 itself handled talking to the Z80? Did one need to write two different programs, one for each CPU? If yes, how did they communicate with each other? Or is memory mapping used, which would require a binary that has both 68000 and Z80 instructions in them, making sure that the Z80 code is in a specific memory region?

(This isn't about "regular" multi-processing, like on newer consoles with multi-core CPUs that are all the same. This is about consoles with a main CPU and specialized co-processors for e.g., Sound. Basically, the Sega Genesis, though I'm looking at building my own custom system, so I'm more interested in the basic principles.)

  • 4
    "CPU" probably isn't the best term here, though I'm not certain what the idiomatic one of the time is; while you could have a 68k and a Z80, it was also common to see more specialized support chips. The general concept is called asymmetric multiprocessing. Commented Mar 29, 2019 at 3:29
  • 1
    Although not a console, in the 1980's, the ATR8000 was a Z80 CP/M system that had an option of replacing the socketed Z80 with a socketed small board that contained a Z80 and a 8088 and 512KB of ram. The 8088 could run MSDOS 2.11, using the Z80 to interface with the peripherals, floppy disks, serial port, printer, and a second serial port used for the ASCII terminal. In CP/M mode, the 512KB of ram could be used as a ramdisk. There was an 8 bit bus used to communicate between the Z80 and the 8088.
    – rcgldr
    Commented Mar 29, 2019 at 8:59
  • 1
    The ATR8000 could also be used with an 8 bit Atari 400/800/65XE/130XE, with the Atari used as a terminal, or with the ATR8000 used as a peripheral controller for the Atari, adding a 6502 cpu into the mix, although even if present, the 8088 would not be used if using the ATR8000 as an Atari controller.
    – rcgldr
    Commented Mar 29, 2019 at 9:05
  • 1
    Fun fact: New Phones have a similar model; they have a set of several processors of varying power needs/capabilities (at face value, to keep lower-need tasks on lower-power cores to save battery life). Could be worth looking into those for a modern approach to the given problem. IIRC in phones' case, though, it's all handled by the OS.
    – Delioth
    Commented Mar 29, 2019 at 20:58
  • 4
    @Delioth While new phones have multiple cores of different speed (i.e. big.LITTLE), they all run the exact same ISA and are completely coherent, so it is transparent to the programmer. The modern equivalent to this problem is more like GPU vs CPU computing.
    – user71659
    Commented Mar 30, 2019 at 7:03

2 Answers 2


It varies machine to machine; at the simplest end is the Neo Geo — its 68000 and Z80 have completely independent buses. You write one program for the 68000 and one for the Z80 and a single pipe of communication joins the two: post a byte to the Z80 and it'll trigger an NMI; the Z80 can read the command byte from a certain port and write a response to another, the 68000 can poll for the response. Neo Geo also supplied a sample set of Z80 code so you could just treat it as an advanced sound generator and not worry about the implementation if you prefer.

The Mega Drive has a more complicated system of shared buses; the Z80 has some memory on a private bus but the cartridge bus is a shared resource and I think the Z80 can also share some RAM. In that system the VDP can also act as a bus master so in net it's the Z80 getting access to the shared resources only when nobody else is attempting an access, the 68000 having priority only when it doesn't chose to start a VDP transfer, and the VDP having top priority for those periods when the 68000 has command it to do something.

If you ever hear scratchy sampled audio in a Mega Drive game then it's likely to be the Z80 trying to stream from the cartridge but frequently losing out on access slots.

The Saturn is like a more advanced Mega Drive except that the main CPUs have caches that can also be configured as small local memory pools. So if you're careful you can mostly keep them off the shared bus, gaining a significant performance benefit — Virtua Fighter 2 manages to keep most of the data for each player local to a single CPU for most of a frame, the laziest PlayStation ports do nothing in particular and either end up only using a single CPU or effectively doing so as a result of collection.

The Jaguar is supposed to work similarly to the Saturn but, quelle surprise, Atari rushed it to market so there's a significant bug affecting the RISC CPU's accesses to RAM when performing certain types of jump. That's how it often ends up being treated as a machine with a 68000 central processor when really the 68000 was intended just to be an intelligent scheduler.

So: across these systems one generally writes a different program for each processor, and either nominates one as a coordinator or uses a series of ad hoc means of point-to-point communication.

If it sounds hard to get right, that's because it is — programmers much prefer systems like the original PlayStation with a single CPU that just goes quickly.

  • Thank you for pointing out the Neo Geo, I found this article about the communication and this makes a lot of sense - basically two independent CPUs, with the 68k in the drivers seat, and literally different ROMs for each CPU. This looks more elegant than the shared memory approach that e.g., the C64 used, though I'm still doing research. Commented Mar 31, 2019 at 5:02
  • 1
    Yeah — if you check out the connector on a Neo Geo cartridge e.g. hit930.sakura.ne.jp/hitjapan/NeoGeoAES2/17011308023.jpg you'll notice it has two exposed PCBs rather than the usual one; that's because of the three independent buses in the system (the video system being the third) so there's a lot more than usual to connect.
    – Tommy
    Commented Mar 31, 2019 at 18:46

There are two basic techniques: shared memory and dedicated communication ports.

Shared memory simply allows both processors to access the same memory bus. There are some issues, as the bus has to be shared and one CPU has to get priority so code must be designed to take unpredictable extra delays into account. The Megadrive is a good example of that, with the Z80 CPU losing cycles to the 68000 and the graphics subsystem.

It's actually a quite awkward system but they wanted the Z80 for backwards compatibility with Master System games. The system has a dedicated sound chip and the overhead for playing back music and sound effects is so low that there is little benefit to offloading it from the 68000.

The other issue with shared memory is that if one CPU is writing to it while the other is reading it, the reading CPU can end up with corrupt data. Therefore some kind of arbitration is needed, often based on atomic update operations.

Communication ports allow two CPUs on separate buses to communicate. Each CPU has its own bus, its own RAM, its own peripherals and a single I/O port that lets it communicate with the other CPU(s). The port usually allows commands and small amounts of data to be sent, often one way, from one CPU to another and an acknowledgement to be sent back. The Neo Geo is an example of a system that works that, or more common in the west was BBC Micro with its optional second processor via the "tube".

Software for each CPU was written and debugged separately.

  • Wouldn't having a separate CPU for audio simplify the creation of an engine, though? Just write to the shared memory from the 68k when you want the Z80 to play a sound, and let the Z80's program handle it from there. Versus trying to manage graphics without letting the audio hang on a single CPU (lots of juggling).
    – Wyatt Ward
    Commented Oct 16, 2019 at 0:51
  • @Wyatt8740 depends on the sound hardware. With a decent sound chip it doesn't need much to program it, and most later machines did in fact use such hardware with a single CPU. Sega had been using the dual-CPU setup for years in their arcade systems because early arcade sound hardware benefited from having the CPU assist since it was very simple and limited on its own. Since they needed the Z80 anyway they just went with it.
    – user
    Commented Oct 16, 2019 at 13:57
  • eh, I've programmed on the NES. It's quite hard to wrap my mind around writing a program in assembly and juggle the audio and video work simultaneously in a sane manner.
    – Wyatt Ward
    Commented Oct 16, 2019 at 18:34
  • A lot of the time sound was handled in the vertical blank interrupt, especially music. On most machines playing a sound involved writing to a handful of registers.
    – PaulHK
    Commented Feb 10, 2020 at 5:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .