This article welcomes anyone that wants to help with translations or contributions.
Sega (and their TV ads) want you to know: It’s impossible to bring descent games without faster graphics and richer sounds.
Their new system includes lots of already familiar components ready to be programmed. This means that, in theory, developers would only need to learn about Sega’s new GPU… right?
This console has two general purpose processors.
Firstly, we’ve got a Motorola 68000 running at ~7.6MHz, a popular processor already present in many computers at that time, such as the Amiga, the (original) Macintosh, the Atari ST… Curiously enough, each one of them succeeded its ‘6502 predecessor’ and while the Master System (Mega Drive’s precursor) doesn’t use a 6502 CPU, the NES did (and in some way, Sega’s goal was to win Nintendo consumers over). All in all, you can see a bit of correlation between the evolution of computers and game console technology.
Back on topic, the 68k has the role of ‘main’ CPU and it will be used for game logic, handling I/O and graphics calculations. It has the following capabilities:
(If you wonder the reason behind using 24-bit addresses with a CPU that can handle 32-bit addresses, I doubt that in the 80s many were asking to manage 4 GB of RAM and adding unused lines is costly in terms of performance and money).
Secondly, there’s another CPU fitted in this console, a Zilog Z80 running at ~3.5 MHz. This is the same processor found on the Master System and it’s mainly used for sound control. It features:
Both CPUs run in parallel.
The main CPU contains 64 KB of dedicated RAM to store general-purpose data and the Z80 contains 8 KB of RAM for sound-related operations.
Sega chose two independent processors that have no awareness of each other, so how can games manage both at the same time? Well, the main program is executed in the 68000, and this CPU can subsequently write on Z80’s RAM. So, it’s possible for the 68000 to send a program to the Z80’s RAM and make the Z80 load it (by sending a reset signal to that CPU). Once the Z80 is under control, it can be used to manage the sound sub-system and move memory around using the previously described method, all of this while the 68000 is running other operations.
Because one CPU will have to step in the other’s CPU bus and both can’t use it at the same time, there’s an extra component called Bus arbiter that must be activated to stall either processor, so memory can be written without hazards.
It’s important to point out that this design can underperform if not managed properly, so games will have to take special care of the bus arbiter and watch for not stalling either CPU for longer than needed.
Graphics data is processed by the 68000 and rendered on a proprietary chip called Video Display Processor (or ‘VDP’ for short) which then sends the resulting frame for display.
The VDP runs at ~13 MHz and supports multiple resolution modes depending on the region: Up to 320x224 pixels in NTSC and up to 320x240 pixels in PAL.
This chip has two modes of operations:
What about Mode 0 to III? Well, these belong to the even older SG-1000 and the Mega Drive doesn’t support them.
The graphics content is distributed across 3 regions of memory:
The following section explains how the VDP draws each frame, for demonstration purposes Sonic The Hedgehog is used as example. I recommend checking out the functioning of its predecessor since there will be a lot revisited in here.
Just like Nintendo’s PPU, The VDP is a tile-based engine and as such it uses tiles (basic 8x8 bitmaps) to compose graphic planes. Each tile is coded in a simple 4-byte array where each 4-bit entry corresponds to a pixel and its value corresponds to a colour entry.
Game cartridges contain tiles in their ROM but they have to be copied to VRAM so the VDP can read them. Traditionally, this was only possible during specific time frames and handled by the CPU, fortunately this console added special circuitry to offload this task to the VDP (we’ll get into details later on).
Tiles are be used to build a total of 4 planes which, merged together, form the frame seen on the screen. Planes' tiles will overlap with each other, so the VDP will decide which tile is going to be visible based on the type of plane and the tile’s priority value.
The Background plane, also known as Plane B is a scrollable tilemap containing static tiles.
This plane can have six different dimensions: 256x256, 256x512, 256x1024, 512x256, 512x512, 1024x256. The choice can be based on the type of scrolling that will be required.
Each tile can be flipped horizontally and/or vertically and have a priority set.
On the showed example you’ll notice that the selected area for display is not a square… It doesn’t have to! The VDP allows to set up horizontal scrolling values for the whole frame, each individual scan-line or for every eight pixels. This means that developers can shape the selected area like a rhomboid and alter its angles while the player moves in order to achieve a Parallax effect. Tricks like this one don’t result in a distorted plane, the VDP fetches each (selected) horizontal line and builds a squared frame from it.
The Foreground plane, also known as Plane A, has the same properties as the Background Plane except this plane has a higher priority, so tiles rendered here will inherently be on top of the Background Plane.
Additionally, this plane allows to divide itself to form a new sub-plane: The Window Plane. The only difference is that the latter doesn’t scroll.
Compared to previous consoles, the combination of different priorities and the Window plane allows to achieve a more convincing illusion of depth.
In this plane, tiles are treated as sprites, they are positioned in a 512x512 px map and only a part of it (VDP’s output resolution) is selected for display. This is convenient for hiding unwanted sprites or preparing others that will be shown in the future. The VDP also provides an old collision detection function.
Sprites are formed by combining up to 4x4 tiles (32x32 map) and selecting up to 16 colours (including transparent), if a bigger sprite is needed then multiple sprites can be combined into one.
There can only be a maximum of 20 sprites per scan-line and 80 per screen (overflowing this will corrupt the whole layer).
The region in VRAM where Sprites are defined is called Sprite Attribute Table and each entry contains the tile index, layer coordinates (x and y), Link value (manages which sprites are drawn first), priority (the sprite with highest priority is the one to be displayed during overlaps), colour palette index and vertical and horizontal flip.
While the frame is being drawn, the system will sequentially call different interrupt routines depending where the CRT’s beam is pointing to. As you probably seen before in previous consoles, this allows the CPU to work on the next frame (or alter the current one).
Conventionally, there are two types of interrupts called: H-Blank (every horizontal line) and V-Blank (every frame).
H-Blank is called numerous times but is limited to executing short routines, only CRAM and VSRAM are accessible, so games can only update their colour palettes or vertically scroll their planes.
V-Blank allows for longer routines with the drawback of being called only 50-60 times per second, it’s also able to access all memory locations.
So far we’ve discussed what the CPU can do to update frames, but what about the VDP? This chip actually features Direct Memory Access (‘DMA’ for short) that allows to move memory around at a faster rate without the intervention of the CPU.
The DMA can be activated during H-Blank, V-Blank or active state (outside any interrupt), each one will have a different bandwidth. Additionally, during any DMA transfer the CPU will be blocked, this means the timing is critical to achieve performance.
If used correctly, you’ll gain high resolution graphics, fluid parallax scrolling and high frame-rates. Moreover, your game may also be featured on TV ads with lots of Blast Processing! signs all over it.
This console has the same video out port of the Master System.
The Mega Drive has 2 sound chips with very different capabilities:
An FM synthesiser that runs at the 68000 speed and supports six FM channels, one can be used to play PCM samples (8-bit resolution and 32 KHz sampling rate).
Frequency modulation or ‘FM’ synthesis is one of many professional techniques used for synthesising sound, it significantly rose in popularity during the 80s and made way to completely new sounds (many of which you can found listening to the tunes from that era).
In a strict nutshell, the FM algorithm takes a single waveform (carrier) and alters its frequency using another waveform (modulator), the result is a new waveform with a different frequency (and sound). The carrier-modulator combination is called operator, multiple operators can be chained together to form the final waveform, different combinations achieve different results. This chip allows 4 operators per channel.
Compared to traditional PSG synthesisers, this was a drastic improvement: You were no longer stuck with pre-defined waveforms.
A PSG chip that can produce three pulse waves and one noise.
This is actually the original Master System’s sound chip and it’s embedded in the VDP, it runs at the speed of the Z80.
Notice the ‘Pulse 3’ channel remains unused, this is indeed reserved to play the effects during gameplay.
Both chips can output sound at the same time, the audio mixer will then receive both signals and merge them before sending it through the audio output.
The Z80 is the only CPU capable of sending commands to those two chips, which is a relief for the 68000 since the latter is already fed up with other tasks.
However, let’s not forget that the Z80 is an independent processor by itself, so it needs its own program (stored in the 8 KB of RAM available) which will enable it to interpret the music data received from the 68000 and effectively manipulate the two sound chips accordingly. This program is called sequencer or driver.
Now, some games may decide to exploit the PCM channel, and for that they also need to plan a way to continuously sequence and stream their music using the rest of RAM available. The main constraint is that in order to fill that memory, the main bus has to be blocked first (so no commands or samples can be sent to the audio chips during that timeframe). If this issue wasn’t tackled properly, different sound anomalies could appear (muting, frozen notes, low sample rates, etc).
I’ve decided to dedicated a section for those who successfully manage to overcome the aforementioned constraint. Instead of just sticking with ordinary drum kits, some games found incredible ways to stream richer samples to that single PCM channel, check out these examples:
I know, they are nowhere near CD quality, but bear in mind those sounds were once deemed impossible to reproduce in this console and I’m not even emphasising how much progress this represents compared to the previous generation, so they certainly deserve some merit at least!
If programming an FM synthesiser was already considered complicated using the controls of an electronic keyboard (the Yamaha DX7 is a good example of this), imagine how much it was using only pure assembly…
Luckily, Sega ended up producing a piece of software for PC called GEMS to facilitate the composition (and debugging) of music. It was a very complete tool, among lot of things it included lots of patches (already configured operators to choose from), which would also explain why some games have very similar sounds.
The audio subsystem enabled games to create more channels than allowed and assign each one a priority value, then when the console would play the music, it dynamically dispatched the music channels to the available slots based on priorities. Additionally, channels with a high priority but without music could be automatically skipped.
Channels also contained some logic by implementing conditionals inside their data, this allows music to ‘evolve’ depending of how the player moves in the game.
Here’s an interesting fact: The Mega CD add-on provided 2 extra channels for CD Audio (among other things). One of its most famous games, Sonic CD, had very impressive music quality but like all games it had to loop, the problem was that looping music on a 1x CD reader had noticeable gaps, so the game included loop fillers that were executed from another PCM chip while the CD header was returning to the start.
These fillers are only found on early betas of the game and they didn’t make it for the release, the remake finally included them. This is one of the levels of the game:
Have you noticed the gap on the Mega CD’s version?
They are mainly written in 68000 assembly while the sound driver is in Z80 assembly. Both reside in the cartridge ROM and can size up to 4 MB without the need of a mapper.
In terms of expandability, this design wasn’t as modular as the NES or the SNES. Hence, some add-ons like the 32x had to bypass the VDP (hence the need for the ‘Connector Cable’).
Only one custom chip was produced for cartridges, the Sega Virtua Processor, among other things it helped to produce polygons, although only one game included it as it resulted very expensive to produce.
To block imported games, Sega changed the shape of the cartridge slot between regions (it kept the same pinouts, though). Games could also block their execution by checking the value of the ‘Version Register’ which outputs the region value. An easy way to bypass this was to either buy one of those shady cartridge converters or do some soldering to bridge some pins on the motherboard that alters the Version Register.
When it comes to Anti-Piracy measures, the easiest check was on the SRAM size: Bootleg cartridges had more space than needed to fit any game, so games checked for the expected size on the startup. Programmers could also implement extra checksum checks at random points of the game in case hackers were to remove the SRAM checks. The only way to defeat this was to actually find the checks and remove them one by one… Although finding them was the trickiest part!
This article is part of the Architecture of Consoles series. If you found it interesting please consider donating, your contribution will be used to get more tools and resources that will help to improve the quality of current articles and upcoming ones.
A list of desirable tools and latest acquisitions for this article are tracked in here:
## Interesting hardware to get (ordered by priority) - A PAL/NTSC/JAP Megadrive (£30) - Controller (£5) - USB MegaDrive DevKit (~£50 in materials)
Alternatively, you can help out by suggesting changes and/or adding translations.
Always nice to keep a record of changes.
## 2020-10-25 - Added more content focusing on the 68k-z80 communication ## 2020-09-07 - Expanded CPU section - Corrected main RAM values ## 2020-01-18 - Expanded Audio section and included more audible content ## 2019-09-17 - Added a quick introduction ## 2019-05-23 - Improved definition of FM (such a difficult topic) ## 2019-05-18 - Ready for publication