New / our own FPGA core for MiSTer

MERIDIAN 816The home computer that never was.

Somewhere between the C64 and the Amiga: a brand-new computer with a 65C816 processor, custom chips for graphics, sprites, sound, copper and blitter, Microsoft BASIC and 16 MB of memory. Not an emulator but real logic inside the MiSTer's FPGA – designed, built and signed off on real hardware. Since 4 October 2026 the core is out – free of charge and open source. Since 8 October it is finished: MERIDIAN 1.0, with a look of its own and built-in tools for sprites, maps and sounds. Since then the graphical desktop HORIZONT and the first game have followed, both ready to download.

Runs on real hardwareMERIDIAN 1.0Free core on GitHub
MERIDIAN 816 power-on screen: **** MERIDIAN 816 ****, colour bars with 16 colours, 65C816 / 8 MHz / 16 MB RAM / OS 1.0, 47102 BYTES FREE, MERIDIAN 816 BASIC V1.1, COPYRIGHT 1978 MICROSOFT, READY.
MERIDIAN 816
Power-on screen on the MiSTer, grabbed through the capture card
65C816 · 8 MHz◆16 MB◆256 of 4096 colours◆32 sprites◆4 synth + 8 samples◆Copper◆Blitter◆Microsoft BASIC

The video / 7 October 2026

The MERIDIAN on video.

LOAD "FIRST816"

Introduction / chips & first applications

New

The home computer that never was – in seven minutes

How the idea came about, what PINSEL, KOBOLD, LOTSE, KRAN and ORGEL can do – and the first applications: TAKTSTOCK, a tracker in the style of ProTracker with its own column for the light show, and FABULA with the adventure WILLKOMMEN ZURÜCK. At the end the demo FIRST816 runs: music and light show from a single file, played by the ORGEL. The video is in German with German subtitles.

Watch the video on YouTube ↗

The idea / a thought experiment

Between two worlds.

SYS 816

The C64 arrived in 1982, the Amiga in 1985. In between lies a gap that was never filled: a home computer that still feels like a C64 – switch on, READY., start typing – but can already do what made the Amiga famous. That is the machine we are building.

The name says it all: a meridian is the line between two halves. It is built as a core for MiSTer, an open FPGA platform on which classic computers are not emulated but recreated as circuits. Except that the MERIDIAN has no original to recreate – every chip is designed from scratch.

The idea and the sign-off on real hardware come from Marcel; design, code and testing from Claude, an AI by Anthropic. Every stage is documented in the build log – with all the decisions, detours and bugs.

Key figures compared
C64MERIDIAN 816Amiga 500
CPU6510, 1 MHz65C816, 8 MHz68000, 7 MHz
Memory64 KB16 MB: 256 KB chip RAM + 15.7 MB extra memory512 KB
Colours16 fixed256 of 409632 of 4096
GraphicsText, 2 bitmap modes2 layers: text 40/80, tiles with scrolling, bitmap with 16 or 256 coloursBitplanes
Sprites832 × 16×16 (or 32×32), 16 colours, no per-line limit8
SpecialRaster IRQCopper, blitter, raster IRQCopper, blitter
SoundSID, 3 voices4 synth voices + 8 sample channels, echo, stereoPaula, 4 sample channels
BASICMicrosoft V2Microsoft 1.1 + commands for graphics, sound, drives and networkAmigaBASIC
Storage170 KB floppy, cartridgefloppy and hard disk images (FAT16), cartridges up to 4 MB880 KB floppy
Network–TCP and HTTP(S) from BASIC–

The chips / German names, custom logic

One CPU and ten chips.

$C000–$CBFF

Just like Commodore back in the day, the MERIDIAN only buys in its CPU – a proven, free 65C816 core. Everything around it is home-made, and every chip has a German name that tells you what it does.

P65C816

Processor

8 MHz · 16-bit registers · 16 MB

The CPU of the Super Nintendo and the Apple IIGS: 16-bit registers, 24-bit addresses, and it runs 6502 code too. That makes the MERIDIAN a 16-bit computer with an 8-bit data bus that turns into a 6502 on request – which is how BASIC runs. The core comes from the MiSTer community – along the way we found and fixed two translation bugs in it.

PINSEL

Graphics · “paintbrush”

$C000 · 2 layers · 256 of 4096

Two layers on top of each other, each showing text with 40 or 80 columns, tiles with pixel-smooth scrolling, or a 320 × 240 bitmap in 16 or 256 colours. Colour 0 on the front layer is transparent: text over pictures, parallax from two tile layers. Because PINSEL has its own memory port, the CPU never waits for the graphics. Since MERIDIAN 1.0 it has a look of its own: the MERIDIAN-256 palette in 30 colour families, shine for gradients without steps, glow for light halos around marked colours and ink for outlines and shadows around sprites.

KOBOLD

Sprites · “goblin”

$C300 · 32 sprites · no line limit

32 sprites of 16 × 16 pixels or double size, each with 16 colours from its own palette bank, mirrorable, in front of or behind the front layer, with collision detection. All 32 may share the same line – the C64 managed eight. That is down to a dedicated pattern memory that delivers a whole sprite line in a single clock.

ORGEL

Sound · “organ”

$C500 · 4 synth + 8 samples · echo · stereo

The SID soul: four synth voices with triangle, sawtooth, pulse and noise, ring modulation, sync, envelopes using the SID's own timing tables and a resonant filter – the registers are even in SID order. The Paula soul: eight 8-bit sample channels with loops, played straight from expansion RAM, up to 16 MB per sample – Paula never reached the Amiga's fast RAM. Each channel has a bit crusher, a distortion, an optional route through the filter and a send to an echo that rings for up to a second in SDRAM. Since stage 18 the filter output can be distorted and sent into the echo too – so the synth voices get delay and bite as well. Every voice has its own volume and its own place in the stereo field.

LOTSE

Copper · “pilot”

$C700 · 6 instructions · pixel-exact

A harbour pilot comes aboard and says exactly when to do what. LOTSE reads a command list, waits for a position of the electron beam and then sets registers: colours, layers, scrolling, sprites, even sound. That gives you gradients, split screens and waving logos without the CPU lifting a finger.

KRAN

Blitter · “crane”

$C600 · fills 17.6 MB/s · copies 8 MB/s

KRAN copies and fills rectangles in memory, optionally with transparency for game characters. It works through whole job lists while the CPU does something else, and it reaches the extra memory too – the Amiga's blitter never got anywhere near its Fast RAM.

PFORTE

Input/output · “gate”

$C100 · keyboard · mouse · 2 joysticks · clock

A keyboard buffer for 16 events with German layout (PC or Mac), two joysticks with up to six buttons, the MiSTer's mouse, two timers ticking in microseconds and a calendar clock that takes the date and time from the MiSTer at power-on. Reading has no side effects on purpose: the 65816 performs some “dummy” reads, and keys would otherwise get lost.

BOTE

Program loader · “messenger”

$C200 · menu or network · remote start

BOTE loads programs from the MiSTer menu – or straight from the development machine over the network: it writes into a mailbox in the MiSTer's memory, BOTE copies the program in via DMA and starts it. From the command on the Mac to the running program takes just under a second.

ZUSATZ

Extra memory · “add-on”

Banks $04–$FE · 15.7 MB SDRAM

ZUSATZ drives the MiSTer's SDRAM module at 48 MHz and maps 15.7 MB into the address space. Writing costs no time, reading one wait cycle. The biggest puzzle on the way: on MiSTer modules, the byte masks run over address lines.

TRUHE

Drives · the chest

$C900 · 2 images + 1 folder · FAT16

TRUHE (“chest”) reads and writes floppy and hard disk images on the MiSTer's SD card, up to 15 blocks at a time. The DOS in ROM speaks FAT16, so the same images open on a PC or Mac. Plus cartridges of up to 4 MB that start at power-on and keep a save file, a bit like the EasyFlash on the C64. Drive 3 is a folder on the SD card: copy files in from your computer and DIR shows them right away – no image, no re-inserting.

DRAHT

Network · the wire

Bank $FD · 64 KB in DDR3 · TCP and HTTP

DRAHT (“wire”) is a window into the memory that the MiSTer's FPGA and Linux share. On the Linux side a small network service waits: it opens connections, takes calls, fetches web pages and programs and creates new disks. From BASIC, NET "GET wttr.in/Berlin" is all it takes – one request takes 1.2 ms.

Circuit board / how it all connects

The virtual mainboard.

REV 1.0

The MERIDIAN has no physical board – everything lives as circuitry inside the MiSTer's FPGA. Drawn out, it would look like this:

The virtual mainboard of the MERIDIAN 816The P65C816 CPU sits on the system bus together with the kernel ROM, the ROM in bank $FF (BASIC, DOS, monitor, SONG, workshop) and the registers of every chip: PFORTE, BOTE, LOTSE, ORGEL, KRAN, PINSEL with KOBOLD, TRUHE and DRAHT. The CPU reaches chip RAM through the memory arbiter (port A); LOTSE, ORGEL and KRAN get the free cycles there via DMA. PINSEL reads chip RAM through its own port B. ZUSATZ connects the CPU, KRAN and ORGEL (samples and echo) to 128 MB of SDRAM. TRUHE reads and writes disk images on the SD card, DRAHT talks to the network service under Linux through a window in the DDR3 memory. At the bottom, the MiSTer framework supplies keyboard, joysticks and programs and outputs picture and sound.MERIDIAN 816 · MAINBOARD · REV 1.0 · 2026RETRO-MODERNSYSTEM BUSPORT ADMAPORT BDMA (9a)DMA (15)keys, joysticksprogramssound (stereo)disk imagesnetwork servicevideoCLOCK24 MHz system12 MHz pixels48 MHz SDRAMPLLKERN ROM12 KB · $00:D000ROM BANK $FFBASIC, DOS, TOOLSP65C816CPU · 8 MHz16-bit registers24-bit addresses, 16 MBas in the SNES and Apple IIGSARBITERmemory accessCPU first, never stalledfree cycles for DMALOTSE › ORGEL › KRANCHIP RAM256 KB inside the FPGAbanks $00–$03two portsPort A: CPU · Port B: videoPFORTEinput/outputmouse, clock, timers$C100BOTEprogram loadermenu + network$C200LOTSEcopperrides with the beam$C700ORGELsound4 synth + 8 sample$C500KRANblittercopy, fill$C600PINSELgraphics2 layers$C000KOBOLD32 spritesown 16 KB$C300TRUHEdrivesimages + folder$C900DRAHTnetwork64 KB in DDR3BANK $FDZUSATZSDRAM controller, 48 MHzSDRAM 128 MB15.7 MB addressableMiSTer FRAMEWORKDE10-Nano with ARM Linux: USB · menu and SD card · network service in DDR3 · HDMI/VGA · sound

The CPU is never stalled.

A CPU bus cycle takes three system clocks. The CPU only needs the RAM in one of them – the second for reading, the third for writing. The memory arbiter hands the remaining clocks to LOTSE, ORGEL and KRAN, in that order.

Graphics with a door of their own.

PINSEL reads chip RAM through a second port. While one line appears on screen, it is already painting the next into a line buffer. On the C64 the CPU had to wait whenever the graphics needed the bus (“badlines”) – here, never.

24 MHz heartbeat.

From a 24 MHz system clock the CPU gets every third tick (8 MHz) and the graphics chip every second (12 MHz pixels, 640 × 240 visible, 60 or 50 Hz). Why not 48 MHz? The longest path through the CPU logic takes about 26 ns – at 48 MHz there would only be 20.8.

BASIC / Microsoft's original from 1978

Switch on. READY. Start coding.

47102 BYTES FREE

The MERIDIAN starts the way a home computer should: in BASIC. Not a clone, but Microsoft BASIC M6502 1.1 built from the original source code, which Microsoft released under the MIT licence in 2025 – the same family tree as the BASIC in the PET, the Apple II and the C64.

The catch: the source is written for MACRO-10, the assembler of a PDP-10 mainframe. That assembler no longer exists. So we wrote a translator that turns Microsoft's code into modern assembler syntax – octal numbers and period macros included. Everything else is still Microsoft's code. The ROM even keeps the hidden greeting “WRITTEN BY WEILAND & GATES”.

BASIC runs in the 65816's 6502 mode – at 8 MHz instead of 1 MHz. And it has more room than on the C64: 47,102 bytes for programs (C64: 38,911), because program and variables live in a memory bank of their own.

The same BASIC code on both machines
C64MERIDIAN
FOR I=1 TO 1000:NEXT1.03 s0.12–0.13 s
300 × SIN(I)8.9 s1.02 s

PROGRAM // REGENBOGEN (RAINBOW) // 11 LINES

10 rem *** regenbogen - meridian 816 basic ***
20 cls:graphic 1
30 for x=0 to 319 step 2
40 line 160,239,x,0,16+x*.75
50 sound 1,200+x*2,1:pause 1
60 next:sound 1,0
70 for a=0 to 6.29 step .01
80 plot 160+120*sin(a*3),110+90*cos(a*2),1
90 next
100 sound 1,523,1:sound 2,659,1:sound 3,784,1
110 pause 90:silence
REGENBOGEN 160 lines across the colour wheel, a tone for each, then a Lissajous figure and a C major chord. Picture from the simulation, sound from the hardware.
The new words in MERIDIAN BASIC
GRAPHIC 1 · PLOT · LINEa 320 × 240 bitmap with 256 colours in front of the text, points and lines – lines are drawn by the kernel in fast 16-bit code
PALETTE · GRADIENTremix colours, colour gradients per line via the copper
SPRITE · PATTERN · STAMP · BLITsprites, images and the blitter straight from BASIC, even from extra memory
SOUND · SAMPLE · PLAYtones, samples on eight channels (also straight from expansion RAM) and background music: PLAY "T150 O5 L8 CEGEC<G>CE !"
SONG · SONG()songs from the TAKTSTOCK tracker in the background – with SONG(0) a game follows the music
SHINE · GLOW · INKthe PINSEL look: gradients without steps, glowing colours, outlines and shadows around sprites
MAP · TILE · SFX · LOOKthe data from the workshop: show and scroll maps, set and read cells, play sounds, take over palette and character set
MOUSE() · JOY() · KEY() · HIT() · CLOCK()mouse, joysticks, keys held down, sprite hits, date and time
DIR · LOAD "name" · SAVE "name"programs and data on disk images or, with DRIVE 3, in a folder on the SD card, plus BLOAD, BSAVE, SCRATCH, HEADER
NET · NET$()online: fetch web pages, open connections, load programs, create disks
ELSE · WHILE · REPEAT · RENUMBERwhat the 1978 BASIC was missing: IF … ELSE, two loops and renumbering with every jump updated
PEEK · POKE · WAITwith 24-bit addresses: POKE 65536*4,123 writes to extra memory
MONITORenter the machine-code monitor with its assembler, return with X

At first the MERIDIAN spoke German: FARBE, KLANG, LADE. Since stage 10 the keywords are English, and saved programs keep working – the tokens stayed the same. One hurdle came even earlier: the sound command was meant to be TON (German for “tone”), but Microsoft's BASIC would have read FOR I=1 TON as TO N.

Every word with its value ranges and a short example tested on the MiSTer: the command reference BASIC.md ↗.

Build log / 3 to 8 October 2026

Eighteen stages to a home computer – and four steps to 1.0.

LOG

From the first READY. to disks, networking and a monitor with an assembler took two days. Every stage ran in simulation first, then on the MiSTer, signed off through the capture card. For testing, Claude even types on it: via a virtual USB keyboard that a small script creates on the MiSTer. Then four steps led to MERIDIAN 1.0: music from the tracker, a look of its own, the workshop and the polish.

  1. 01

    3 October

    “READY.” – CPU, RAM, ROM, text mode

    The free 65C816 core, 128 KB of RAM, a custom character set with umlauts and a kernel ROM in assembler. The first start in simulation worked straight away – only the cursor would not blink.

    What went wrong

    After the WAI instruction the CPU fell asleep forever. The culprit was a translation bug in the Verilog core: IRQ_N = '0' had become IRQ_N == 1. And the clock was first meant to be 48 MHz – but the CPU logic needs about 26 ns, while 48 MHz only allows 20.8. Hence 24 MHz.

  2. 02

    3 October

    Keyboard, screen editor, monitor

    German layout for PC and Mac keyboards, a screen editor like the C64's, a machine-code monitor with built-in help and a fixed jump table for your own programs.

    What went wrong

    The cursor interrupt used the same scratch variables as the editor – a bug that would only have struck now and then. Spotted while reading the code, before it ever happened. And the simulation's first test keyboard typed Y and Z in US layout: the ROM was right, the simulation was not.

  3. 03

    3 October

    Loading programs, timers, raster line

    BOTE loads programs from the menu or over the network and starts them via NMI. The first program: RASTERBALKEN, with a stopwatch counting in decimal mode.

    What went wrong

    On the second send, the restart never came. An NMI got lost if it arrived just before the end of an instruction – the second translation bug in the CPU core. The simulation gained a “send twice” test; since the fix, “FERNSTART” appears twice on screen.

  4. 04

    3 October

    Graphics: two layers, tiles, 256 colours

    Text, scrolling tiles and bitmaps on two layers. Plus a synthwave picture and a parallax landscape – all generated by script, no borrowed images.

    What went wrong

    Quartus had built the chip RAM twice, because of a detail in how reads behave during writes. Described properly, it fits straight into the FPGA's memory blocks – and 128 KB became 256 KB.

  5. 05

    3 October

    Sprites: KOBOLD

    32 sprites without a line limit thanks to a dedicated pattern memory – and a little game with a UFO, balls and collisions.

    What went wrong

    At first every sprite dragged vertical stripes behind it: a 2-bit line tag matched again every four lines. The fix is a register with one bit per pixel that is cleared in a single clock at the start of each line.

  6. 06

    3 October

    Sound: ORGEL

    A SID soul and a Paula soul in one chip. A small tracker in Python pre-computes the music; the MERIDIAN plays it back with 30 lines of assembler. Hardware and simulation sound the same – measured, not guessed.

    What went wrong

    On the hardware, one note sounded a good one per cent sharp. The clock? A five-minute cross-check: 8 ppm deviation, spot on. The recording was to blame – it dropped whole blocks. Lesson learned: distrust the measuring chain before the chip.

  7. 07

    3 October

    Copper and blitter: LOTSE and KRAN

    Plus a memory arbiter that hands out the free cycles. The demo BALLETT manages 248 balls in 11.2 ms per frame – at 60 frames per second.

    What went wrong

    Marcel couldn't hear the kick drum. Rightly so: 96 % of its energy was below 100 Hz, where small speakers reproduce nothing. The cure: a new kick, a little saturation and a bass that briefly ducks out of the way on every hit.

  8. 08

    3 and 4 October

    16 MB of memory and BASIC

    ZUSATZ brings in the SDRAM, Microsoft BASIC 1.1 gets its own commands. In the end the MERIDIAN reports 47,102 bytes free – more than the C64.

    What went wrong

    In the first memory test, every byte written landed in both halves of a 16-bit word: 99.6 % errors. The MiSTer's SDRAM modules carry the byte masks on address lines A11 and A12. After that: 16 MB without a single error.

  9. 09

    4 October

    Extra memory for everyone – and BASIC learns the chips

    The blitter and the program loader now reach the 15.7 MB of SDRAM too, and BASIC drives every chip: copying blocks, stamping images, sprites, samples and colour gradients. 19 lines fetch picture and sound from the big memory, paint a copper sky and make a sprite bounce.

    What went wrong

    One BASIC command ran as another: each loads its number into a register and then jumps on – but for number 0 the load sets the zero flag, the jump didn't happen and the code fell into the next command. A classic 6502 bug.

  10. 10

    4 October

    Disks and cartridges

    The MERIDIAN no longer forgets: floppies and hard disks live as FAT16 images on the SD card, BASIC saves and loads by name, and the Mac reads the same files. Cartridges of up to 4 MB start at power-on. Afterwards the whole computer switched to English – commands, messages and menu.

    What went wrong

    Saving 64 KB took 9.5 seconds: the MiSTer writes every block to the SD card straight away. Now the DOS gathers up to 15 blocks into one request – 2.2 seconds.

  11. 11

    4 October

    BASIC for games, mouse and music

    Mouse, joysticks, keys and sprite hits can be read, the clock delivers date and time, and PLAY plays music in the background. The game STARFALL needs 60 lines for all that.

    What went wrong

    PLAY played every note at the same pitch. The code in ROM read its note table from the wrong memory bank – the 65816 fetches tables wherever its data bank register points. Since then that code only reads with full 24-bit addresses.

  12. 12

    4 October

    Networking, the modern way

    No emulated modem: the MERIDIAN opens connections, takes calls, fetches web pages and programs and creates its own disks. The work is done by a small service on the MiSTer's Linux side, which the computer talks to through a shared piece of memory. The demo: a chat where, if you like, an AI answers as the sysop of a BBS.

    What went wrong

    The network service killed itself on restart: the start script looked for old copies by name – and found its own session, whose command line contained that name. Now the service remembers its process number.

  13. 13

    4 October

    Tools for programmers: ELSE, WHILE and a SMON

    BASIC learns ELSE, WHILE, REPEAT and RENUMBER without costing a single byte of program memory. The monitor becomes a SMON for the 65C816: assembler, disassembler, registers, hunt, compare – and a single step made possible by a small assist in our own hardware. In the evening the core was published on GitHub.

    What went wrong

    The self-test translated all 256 instructions there and back and found 25 errors – at different places every time. With interrupts disabled: none. The music routine, which runs every frame, used the same memory as the monitor. After the move: 0 errors, on the hardware too.

  14. 14

    5 October

    A folder as a drive

    Getting a file from a computer onto the MERIDIAN used to mean: mount the image, copy, put it back on the SD card, re-insert it in the menu. Now a folder on the SD card is drive 3. The network service on the MiSTer's Linux side answers the DOS, and to every program the folder looks like a disk. Long file names show up as 8.3 aliases.

    What went wrong

    The free bytes of an SD card don't fit into the eight digits of DIR – it said “4967295”. The service now reports at most 99,999,999.

  15. 15

    5 October

    Samples from expansion RAM

    ORGEL now fetches samples straight from SDRAM, and a sample may be 16 MB long. It gets priority over the CPU and the blitter there – a late byte is an audible click – and keeps a whole word per channel. A new register balances samples against the synth voices: a sawtooth holds its peak, a drum hit only for a moment.

    What went wrong

    The first measurement on the hardware said 480 Hz instead of 440. Only the measurement was wrong: counting zero crossings tripped over the mirror frequencies of the 8 kHz playback rate. The spectrum showed exactly 440.0 Hz.

  16. 16

    5 October

    Echo, crusher, distortion

    A shout sounded “far too clean” – the rave shouts of 1992 came off vinyl, through filters, with echo, roughed up. Now every sample channel has a crusher that drops low bits and holds values, a soft-clipping distortion and a route through the synth voices' filter. On top comes an echo of up to a second that lives in SDRAM. Measured: repeats exactly every 0.30 s, each half as loud as the one before.

    What went wrong

    Until then the SDRAM could only write bytes; the echo needs whole words. The “whole word” flag has to stay at the SDRAM until the next request – if it is busy refreshing, it takes the request later. On the first try the flag was gone after one clock.

  17. 17

    5 October

    Eight sample channels

    For music with eight channels – old tracker modules, for instance – four sample channels were not enough. The new ones sit in a second register page with the same offsets, so older programs notice nothing. The channels fetch their bytes in turn, so the last ones don't always have to wait. On the hardware all eight play at once, within 1.2 dB of each other. The FPGA gave up its last multipliers for it.

    What went wrong

    Nothing big this time: the simulation ran through on the first try. A music program used to borrow another track's channel for samples on its synth tracks; now every track has its own.

  18. 18

    6 October

    Echo and distortion behind the filter

    An acid line from a SID voice was supposed to crunch – with delay, roughed up. It couldn't: only the sample channels had echo and distortion. Now both sit behind the filter as well, right where a 303 has its effects pedal. Everything that runs through the filter can be soft-clipped and sent into the echo – two new registers. Measured on the acid line: 7 to 12 dB more between 4 and 12 kHz, and the repeats ring on after the last note.

    What went wrong

    With the new core, the test program reported “drive not ready”. Neither the core nor the network service was to blame: the program keeps its drive setting in chip RAM, and reloading the core had reset it to drive 1 – where no disk was inserted.

  19. 19

    8 October · MERIDIAN 1.0

    Music from the tracker: SONG

    The TAKTSTOCK tracker writes songs with eight tracks, effects, envelopes and a synth panel. Now BASIC plays them itself: SONG "NEBEL" loads the song and plays it in the background while the program keeps running. SONG(0) and SONG(1) tell where the music is – a game can follow it. The player comes from the tracker and sits in a ROM of its own.

    What went wrong

    The volume column and the envelopes sounded wrong: the player read the file in a different layout than the tracker. Now it plays the file in place. And the computer's start-up chime cut off the first notes of a song.

  20. 20

    8 October · MERIDIAN 1.0

    A look of its own

    A new computer needs a face of its own, or its pictures look like VGA or SNES. PINSEL got four parts: the MERIDIAN-256 palette with 30 colour families (dark shades turned towards blue violet, light ones towards yellow, the way pixel artists shade), shine for gradients without steps, glow for light halos and ink for outlines and shadows. The picture ABEND paints a lake in the evening with it, in BASIC. Everything is off after start-up – whatever ran before looks exactly the same.

    What went wrong

    Gradients going down flickered in stripes: the clamp took the sign for a carry. And the halo on glowing areas washed them out – glowing pixels now keep their colour.

  21. 21

    8 October · MERIDIAN 1.0

    The workshop

    Six tools in ROM, one key away with F1 to F6: paint sprites and tiles, build maps, sounds like on the Pico-8, a look and a character set of your own. One file keeps program and data together, old files load as before. BASIC got MAP, TILE, SFX and LOOK. Claude recorded and measured the sound of the sounds – a painted sequence falls exactly with the painted notes.

    What went wrong

    An empty map is made of tile 0. Anyone who painted it filled the whole map – so tile 0 stays empty, like sprite 0 on the Pico-8. And the assembler does not tell upper from lower case: an address called KA_LOTSE and a routine ka_lotse were the same to it.

  22. 22

    8 October · MERIDIAN 1.0

    Polish – and fixed for good

    Nothing new, everything sturdier: the MERIDIAN now also runs without an SDRAM module (with 256 KB), loading from the MiSTer menu is twice as fast, and a test bench checks every chip in two seconds. Memory map, registers, entry points and BASIC tokens are fixed since 1.0: later versions only add.

    What went wrong

    Without an SDRAM module the start-up screen still said 16 MB – the open data bus held the last value written, and the memory check read it back. And a program arriving over the network interrupted the DOS in the middle of deleting a file: 130 KB on the disk belonged to no file any more. A remote start now waits until the DOS has finished.

Data sheet / for the curious

The numbers.

M D000
Memory map as the CPU sees it
$00:0000zero page and stack
$00:0400screen memory – a nod to the C64
$00:1800character set
$00:2000free for programs
$00:C000the chips: PINSEL, PFORTE, BOTE, KOBOLD, ORGEL, KRAN, LOTSE, SYSTEM, TRUHE
$00:D000kernel ROM with editor, monitor and jump table
$01–$03more chip RAM: BASIC programs, graphics, samples
$04–$FEextra memory, 250 banks of 64 KB – including the workshop data
$40–$7Fcartridge, up to 4 MB
$FDDRAHT: window to the network service
$FF:0000ROM: BASIC, DOS, music, network, monitor, SONG and the workshop
FPGA logic
19,808 of 41,910 ALMs (47 %)
Block RAM
3.5 Mbit (61 %)
Multipliers (DSP)
112 of 112 – all of them, mostly for ORGEL
Timing slack at 24 MHz
10.5 ns
Picture
640 × 240 visible, 15.71 kHz, 59.95 Hz (NTSC) or 50.3 Hz (PAL)
KRAN
fills 17.6 MB/s, copies 8 MB/s
Pitch on the hardware
488.277 Hz against an expected 488.281 Hz
One Quartus build
just over 9 minutes
Saving to disk
64 KB in 2.2 s
Loading from the MiSTer menu
576 KB in 0.3 s
One network request
1.2 ms round trip
Samples
8 channels, up to 16 MB per sample from SDRAM
Echo
up to 1 s, 16 bit, in SDRAM
The MERIDIAN's own character set: upper and lower case, digits, punctuation, umlauts, lines and block graphics
CHARACTER SET designed in-house: ascenders and descenders, Ä Ö Ü ä ö ü ß, lines and blocks

Get involved / programs and games wanted

A computer needs software.

A home computer lives on what people write for it. That is exactly what we hope for the MERIDIAN: games, demos, music, tools – or BASIC listings to type in, just like the magazines of old.

The first applications already exist.

The desktop HORIZONT with the file manager ATLAS and the tracker TAKTSTOCK is out, now at version 2.6, along with the games from TIEFGANG to PERLENRIFF. FABULA runs on the MERIDIAN: SENDESCHLUSS was already built with it, and the workshop itself comes together with the Amiga version in one package, planned for late 2026. WrestleVerse is still in the works.

You can send in your own programs via the KATALOG. Everyone can find them there, and on the MERIDIAN the KATALOG app loads them straight onto drive 3.

Free, in the spirit of MiSTer.

The core is out: free of charge and open source under the GPL-3, like almost everything in the MiSTer project. GitHub ↗ has the source, the register reference and the example programs; the release holds the ready-made .rbf file and a demo disk.

If you like, you can chip in.

MERIDIAN stays free – the core and HORIZONT. Hosting, the domain, tools and AI assistance still cost money. If you want to help carry the project, you can do so voluntarily via PayPal: no subscription, nothing in return, no donation receipt. Buying FABULA helps just as much.

Support via PayPal ↗

What you need

A MiSTer.

A DE10-Nano with an SDRAM module, as most MiSTer owners already have. The module provides the extra memory. Since 1.0 the MERIDIAN also runs without one – with 256 KB and without the workshop.

How to program it

BASIC or assembler.

BASIC right on the machine, with commands for graphics and sound and with the workshop for sprites, maps and sounds. Or 65C816 assembler on a PC or Mac, for example with 64tass, loading the result as a MER file from the MiSTer menu. Or right on the machine in the monitor with its built-in assembler. A fixed jump table in the kernel helps you get started, and an interrupt hook at $0300 tips its hat to the C64's $0314.

What comes with it

Source code, the MiSTer way.

The complete source of the core on GitHub ↗, including a description of the chip registers. Plus the demo programs as source code – GRAFIK, KOBOLDE, ORGEL, BALLETT, STARFALL, CHAT and the rest – to learn from, tinker with and build on.

Thanks & sources

MERIDIAN 816 is an independent project and is not affiliated with the MiSTer project, Microsoft, Commodore or Amiga. All trademarks belong to their respective owners.