68k-MBC: a 3 ICs 68008 homebrew computer

An easy to build homebrew SBC with a 68008 CPU. Two HW options: Lite and Full. Lite allows to build a 3 ICs 68008 system running CP/M-68K.

Similar projects worth following
The 68k-MBC is an easy to build 68008 CPU SBC (Single Board Computer), using only easy to find TH parts.

It follows the same "concept" of the previous Z80-MBC2 ( and V20-MBC ( boards, using a PIC18F47Q10 MCU as EEPROM and "universal" I/O emulator (so a "legacy" EPROM programmer is not needed).

You can choose between two main HW configuration options: Lite or Full. Lite HW configuration option allows to build a 3 ICs 68008 system running CP/M-68K.

It has an optional on board 16x GPIO expander, and uses common cheap add-on modules for the SD (HD emulation) and the RTC options.

Having two onboard RS232 serial ports, it allows to connect RS232 terminals like uTerm-S (

It is compatible with the uTerm ( and uCom ( add-on boards.

* NOTE TO THE READER *: Due to a text size limitation of the Hackaday. io site a few chapters have been moved to "Log files". In this case you have just to click on the link of the chapter's name to open a new tab and read it.

* * PROJECT STATUS (10/10/2021) * *


  • Released all the HW related files (see the FILES section);
  • Added the USING A SMALL THERMAL PRINTER chapter;
  • Added the USING A uTERM2-S RS232 TERMINAL chapter;


  • Released all the SW related files (see the FILES section);
  • Updated IOS S310121-R130421 and (see the FILES section);;
  • Added the complete collection of the 4 Manuals of CP/M-68K (see the FILES section);
  • Updated IOS S310121-R150421 and (see the FILES section);
  • Added the SW/FW for the Arduino Uno PIC programmer, including the "ICSP Shield" board (see the paragraph: FLASHING THE FIRMWARE WITH AN ARDUINO UNO AS PROGRAMMER);
  • Updated (see the FILES section);
  • Released a working experimental doker image for a gcc cross-compiler toolchain (See the paragraph: SLOAD: HOW SETUP A "DOCKERIZED" GCC + NEWLIB CROSS-COMPILING AUTOMATED TOOLCHAIN (LINUX));
  • Updated IOS S310121-R250521 and (see the FILES section);
  • Added the 68000 IDE installation files and the custom cstart.asm file for the 68k-MBC (128/512/1024KB versions. See the FILES section);
  • Updated (see the FILES section);
  • Updated IOS S310121-R010721 and (see the FILES section);
  • Updated IOS S310121-R220721 and (see the FILES section).


  • Task in progress...


In the first phase of the design I've used a prototype on a breadboard to check the basic "concepts".

I've used as "companion" MCU a PIC18F47Q10 on a custom board (PicOne) I previously made and that it is directly pluggable on breadboards, and with onboard microSD card and USB-serial adapter.:

To make the firmware for the PIC18F47Q10 I've used MPLAB X IDE with the MCC plugin.

Here a short video with an automated assembler toolchain using Easy68K as assembler and sLoad, a custom SW utility to load from the serial port and execute a Motorola S-record formatted executable:

To allow a real automated toolchain an auto-reset circuit on the breadboard takes the DTR signal from the serial-USB adapter and uses it to reset the MCU (like in the Arduino Uno board), so it is possible reset the breadboard from a batch file running in the PC using a macro of Tera Term.

* * WHY A PIC? * *

Those have followed the previous Z80-MBC2 and V20-MBC boards will note that I haven’t used here an Atmega MCU. Using an Atmega MCU allows to use the friendly Arduino IDE and many ways to flash the MCU, so this is an enabling factor.

Unfortunately Atmega MCU GPIO ports are not TTL compatible, and this limitation was solved in the previous boards using a CMOS CPU that under given conditions can accomplish the digital levels of the Atmega MCU.

But here the 68008 CPU isn’t available in CMOS technology at all, so an Atmega MCU cannot be used.

So I’ve done some searches to find an alternative MCU having three main constraints: must have TTL compatible GPIOs (I mean strictly "guaranteed" TTL compatible), must be a TH part and cheap too.

The only part I’ve found was a PIC18F47Q10 MCU, and I must say that it accomplish the previous constrains very well. More, it is a modern MCU with lot of interesting features and more flash and RAM memory than the previous Atmega32 MCU.

Of course nothing comes free, and the choice of a PIC18F47Q10 brings some complexities. The first is the need for an appropriate HW programmer to perform the flashing (however I've found a way to use a common Arduino Uno board as PIC programmer. See the paragraph "FLASHING THE FIRMWARE WITH AN ARDUINO UNO AS PROGRAMMER" below). The second is the constraint to use...

Read more »


The IOS in executable format (.HEX). This executable file is intended for the use with MPLAB IPE (or any other equivalent SW) to program the PIC MCU directly.

x-hex - 86.59 kB - 07/23/2021 at 17:34


The sources for the IOS (with the needed libraries). Unzip into a folder and open with MPLAB X IDE (I've used version v5.45). IOS must be uploaded into the PIC18F47Q10 flash. See the CHANGELOG section on main.c source for more info on changes.

Zip Archive - 2.02 MB - 07/23/2021 at 17:33


The content of the microSD for IOS S310121-R220721. See the CHANGELOG.TXT file inside the SD root for more info on changes.

Zip Archive - 2.33 MB - 07/23/2021 at 17:32


EF06120-A2-user manual.pdf

QR203 printer commands (it is referred to another model but the commands seem to be the same of this one).

Adobe Portable Document Format - 424.74 kB - 07/23/2021 at 17:57


68000 IDE installation files. Unzip into a folder and run SETUP.EXE to install the 68000 IDE on your Windows system.

x-zip-compressed - 2.63 MB - 06/15/2021 at 16:37


View all 12 files


    Just4Fun10/10/2021 at 09:03 2 comments


    I'm currently making a Standard Parallel Port (SPP) adapter for the 68k-MBC GPIO port.

    In this way you can use a legacy parallel (Centronics) printer.

    The cable to use is the common parallel printer cable, with a DB-25 connector at one side and a Centronics connector at the other:

    * * WORK IN PROGRESS! * *


    Just4Fun09/10/2021 at 15:30 0 comments

    * * USING A uTERM2-S TERMINAL *  *

    I've just relesed the uTerm2-S, a new multi-emulation color RS232 terminal for the 68k-MBC (but not only...). It is based on a ESP32 cheap module and is designed to use the FabGL library.

    More info on the uTerm2-S can be found here.

    The following image shows the uTerm2-S (previous PCB revision) connected to a 68k-MBC using the custom RS232 cable (A020221) previously described:

    Here I've set the screen of the uTerm2-S to 132 columns x 75 rows to have a large display area:

    In the following images a 68k-MBC powered with a uCom add-on board and connected to a uTerm2-S terminal (here the terminal was set to 128 columns x 40 rows):


    Just4Fun07/20/2021 at 17:25 0 comments


    It is possible to find "around" cheap little thermal printers like those used to make receipts. The model name of the one I've used here should be QR203.

    These printers typically have an RS232 serial interface, so you can connect it to the 68k-MBC  thru the second RS232 port and use it as a little system printer (i.e. activating the "hard copy" with the CP/M command Ctrl-P):

    These printers are normally sold with two cables, one for the power and one for the data (RS232 or TTL). I suggest to cut both cables in the middle so you'll get two pieces (with one side already connectorized on the printer side) for each type.

    To connect the printer to the RS232 port 2 (J4/AUX) of the 68k-MBC you have to make a custom cable using an half data cable connected to a 3 pin Dupont connector as in the following photo (I've just soldered three wires with one side already connectorized with a Dupont terminal, then isolated with a heat-shrink tube):

    Here the table with the connections between the RS232 connector on the PCB printer side (5 pin) and the Dupont 3 pin connector (for J4/AUX):

    Only GND and RX are really needed, anyway I've connected also TX.

    The pin 1 of the Dupont connector (RX) is the one marked with a white dot on the photo.

    The pin 1 of the 5 pin RS232 connector on the printer PCB side is the one on the left (black wire) on the previous photo.

    This way it is ready to be connected to the RSR232 port 2 pins of J4/AUX as the RS232 custom cable (A020221):

    To power the printer I suggest to use a 9V 3A power supply adding a silicon diode (at least 3A rated) in series to protect against polarity inversions and to lower a little the voltage (9V is the maximum voltage for this printer).

    Remember to set the speed of the serial port 2 at 9600 bps, as this one is the standard operating speed for this model.

    I've done a little utility (SETPRINT.68K) to set the printer to 42 columns using a smaller font and to set bold characters for a better readability (it is in the drive B: together with the source SETPRINT.BAS for the CB68 Basic compiler):

    In the Files section I've uploaded a manual with all the commands for this printer (it is referred to another model, but the commands seem to be the same of this one).

View all 3 project logs

Enjoy this project?



allen wrote 09/07/2021 at 02:26 point

How about a version that would run OS9-68K?

  Are you sure? yes | no

Just4Fun wrote 09/08/2021 at 07:50 point

Hmmm... I never used it. Have you any link?

  Are you sure? yes | no

wawa.voun wrote 08/08/2021 at 17:42 point


Just build successfully the full version. You do a great job !

I have try to use the serial port 2 on J4 (pin 14, 16 and 18) to connect to a vt100 terminal.
Should I get the console directly on this port ? It seems no...

If I use ctrl-p on the normal console (J2) then I see something outgoing on port 2 (pin 14 of J4).

I understand I should probably use "stat" to do that but I am careful not to 'loose' the standard console and then lost control of the board if I do something wrong...

Basically the most easy for me is to have both port (J2 and J4 14-16-18) acting as a console. Of course using only one at a time...

Thanks for the advice.
Regards. Philippe

  Are you sure? yes | no

Just4Fun wrote 08/08/2021 at 18:12 point

Hi, not clear which configuration are you setting...

If you want use the "PC console" (serial 1) on J2 (with the serial-USB adapter) and a legacy RS232 VT100 terminal acting as console too at same time, you could simply connect it (the VT100) on J4 as port 1 too (pin 13, 15 and 17). Of course they will have the same speed and you should use a keyboard a time...

BTW: if you "loose" the console due to a wrong STAT, you can just press the reset button...

  Are you sure? yes | no

wawa.voun wrote 08/08/2021 at 18:35 point

Just give a try. Works well ! I have made the test on the wrong port.

Thanks. Philippe

  Are you sure? yes | no

Sarala Saraswati wrote 07/21/2021 at 08:59 point

I would love to see a pure 16-bit z8002/z8004 version of the mbc2 platform. These are such great projects. Also wish they sold with a nice case! 

  Are you sure? yes | no

Nick Brok wrote 07/08/2021 at 08:51 point

Hi just4fun.
Is it possible to "relocate" the f83.68k bin? I did not find the sourcecode from it, unfortunataly.

  Are you sure? yes | no

Just4Fun wrote 07/19/2021 at 13:48 point

Being a non-relocatable binary I have to say no.

  Are you sure? yes | no

Nick Brok wrote 06/22/2021 at 14:18 point

I tried this one, but the binary doesn't work.

  Are you sure? yes | no

Just4Fun wrote 07/03/2021 at 09:04 point

Hi, I've analyzed the binary of F83.68K and it is a not-relocatable binary that wants start at absolute address 0x00500. But this address is inside the RAM area where CP/M-68K lives, so out from the TPA. The only way is to try to "re-generate" a new F83.68K that starts from an absolute address inside the TPA (TPA starts at 0x07A00 for the 68k-MBC).

  Are you sure? yes | no

Nick Brok wrote 06/22/2021 at 11:25 point

Hi I succesfully build the full version 68ksbc. There was a little issue with the CPU, but Giovanni has sent me an other CPU that works great now. I've found a forth83, but this will not run under CP/M.  I found this in the m68k CP/M archive.

  Are you sure? yes | no

Just4Fun wrote 06/22/2021 at 11:53 point

Hi, you probably are referring to the kits sold by Giovanni...

About Forth 83 try this one that should run under CP/M-68K (not tested by me):

Here a book about Forth 83 by Dr. C. H. Ting:

  Are you sure? yes | no

esiako wrote 06/21/2021 at 09:40 point can run on this device?

  Are you sure? yes | no

Just4Fun wrote 06/21/2021 at 17:17 point

Theoretically I think yes.

  Are you sure? yes | no

esiako wrote 06/24/2021 at 09:04 point

We waiting for mobile version with fuzix ;)

  Are you sure? yes | no

sergei kovalenko wrote 06/19/2021 at 05:22 point

Hello! I have a problem. The loading stoped at:

68k-MBC - A091020-R140221

IOS - I/O Subsystem - S310121-R150421

IOS: Full HW configuration detected
IOS: Found RTC DS3231 Module (15/04/21 15:56:53)
IOS: RTC DS3231 temperature sensor: 21C
IOS: Found GPE Option
IOS: CP/M Autoexec is OFF
IOS: Loading boot program... done
IOS: 68008 CPU is running from now

sLoad - S-record Loader - S180221
1024KB - Full HW configuration
Waiting input stream...

Please help.

  Are you sure? yes | no

Just4Fun wrote 06/19/2021 at 11:41 point

To run CP/M-68K you have to select it from the boot system menu (press RST + USER key, then release RST holding down USER until the menu appears).

  Are you sure? yes | no

sergei kovalenko wrote 06/19/2021 at 13:55 point

Thank you very much! It works now ;) 

I love the board! :) 

  Are you sure? yes | no

gkaufman wrote 05/29/2021 at 20:28 point

I'm trying to get a handle on why the P8's don't seem to work here - and seem to work for others.

I've now built up 3 "Full" and 1 "Lite" boards with the UTerm adapters.

I have PIC's with date codes 21070RU and 19309HU

I have 5 MC68008P8's and 3 MC68008P10's with various date codes.

The 3 MC68008P10's work fine in all boards, the 5 MC68008P8's fail in all boards.

I've also tried 74HCTxx and 74ACTxx TTL

I've tried 512K and 1mb in the "Full" boards.

I've tried several different SD cards.

I've tried with and without the RTC board

I've tried with and without the MCP23017 I/O

Any other ideas to try??

  Are you sure? yes | no

Just4Fun wrote 07/03/2021 at 09:06 point

Last IOS revision fixed your issue.

  Are you sure? yes | no

marazm wrote 05/21/2021 at 13:18 point

I possible run OS 7 on this device? Many people woul be rewrite ROM if get working prototype

or meybe PalmOS?

  Are you sure? yes | no

Just4Fun wrote 05/21/2021 at 14:50 point

Hi, I don't know the HW requirements for the above OSes, but it should be possible to run any OS that uses 68000 machine code @ 8MHz and can be fitted in 1024KB of RAM (Os + user space, no MMU) and uses  block devices for disks and serial ports and terminals for I/O. There is no ROM/EPROM as the boot program is loaded from SD by the 68008 "driven" by the PIC MCU, then a reset is made to let the CPU run normally.

  Are you sure? yes | no

marazm wrote 05/29/2021 at 18:03 point

can You add rom and trying run macintosh classic SE mac os 7.* ?

  Are you sure? yes | no

villaromba wrote 05/19/2021 at 17:56 point

I completed my build today but have the same problem as a few others  (Facebook) I I keep re-booting I can occasionally get the complete menu but only option 6: works. All  other attempts give

IOS: Current Disk Set 0 (CP/M-68K v1.3)
IOS: Loading boot program (CPM68.BIN)...
IOS: CPU bus fatal error code: 2 – Aborted

68k-MBC - A091020-R140221
IOS - I/O Subsystem - S310121-R150421
IOS: Full HW configuration detected
IOS: CP/M Autoexec is OFF

 IOS: Select boot mode or system parameters:

 0: No change (2)
 1: sLoad
 2: Enhanced 68K Basic
 3: Autoboot
 4: Load OS from Disk Set 0 (CP/M-68K v1.3)
 5: Change Disk Set 0 (CP/M-68K v1.3)
 6: Change serial ports speed
 7: Change CP/M Autoexec (->ON)

Enter your choice >4  Ok
IOS: Current Disk Set 0 (CP/M-68K v1.3)
IOS: Loading boot program (CPM68.BIN)...
IOS: CPU bus fatal error code: 2 – Aborted

All 3 ICs from Mouser  with batch code 19309HU
It seems as though there are a few anomalies somewhere !!!

@Fabio I'm happy to send you one of the ICs if it helps identify this problem

  Are you sure? yes | no

Just4Fun wrote 05/20/2021 at 07:34 point

Hi, it seems that there are a few (at least up to now) cases like yours. I haven't had this issue up to now, and the same for the person who sells the kit (and there are others who have successfully assembled the board and also using the same 19309HU batch as this one: ), so this might be a good idea as I can't try "to understand" something that I can't "see". I sent you a message.

  Are you sure? yes | no

Just4Fun wrote 05/20/2021 at 10:13 point

Hi, some days ago I received another batch of PIC and forgot about it...

I've checked just now and they appears to be the same batch of yours (19309HU).

So I've tried one in a 68k-MBC board with a MC68008P8 ad it works perfectly... (see photo here:

  Are you sure? yes | no

villaromba wrote 05/20/2021 at 13:59 point

Thank you for trying. I AM NOW FULLY WORKING!!!  After trying power from usb, a powered usb, a Rapsberry pi PSU (5v 2.5A) and finally a Raspberry pi PSU 5.2v 2.5A  all is good. Sorry for all the fuss but it seems  that the right and adequate power supply is the solution ...... for me any way !!!

  Are you sure? yes | no

gkaufman wrote 05/20/2021 at 16:57 point

I don't think it's the PIC - I have two boards built up from the same Mouser order of parts.  Both work fine with a MC68008P10 and have the same CPU bus fatal error code: 2 error with a MC68008P8.  Both are USA sourced used CPU's.

The system will often boot up once when the MC68008P8 is cold, but then fails repeatedly until the CPU cools off.  I'm suspicious that the timing is marginal for the P8's.  I have two more MC68008P10's on order - but as they are from China the real speed ratings are unknown.

I use the uTerm board for power and i/o, with a reasonable quality 9VDC supply feeding the uTerm. 

I haven't tried lowering the clock rate, as I'm waiting for the additional MC68008P10's to arrive first.

The running system is VERY nice!!

Addendum -= after seeing the note above I tried the MC68008P8 system off of a HP/Agilent power supply  - no difference with a high quality supply or varying the voltage from 4.8 --> 5.5vdc

The same board is rock solid with the MC68008P10.

  Are you sure? yes | no

Just4Fun wrote 05/20/2021 at 14:06 point

Great!!! The MC68008 is not a CMOS CPU like the previous one, so it is more picky about the power (and also it drains more...)

So only the last one PSU worked?

  Are you sure? yes | no

villaromba wrote 05/20/2021 at 14:25 point

Yes, the others 'worked' but gave the error message as above., so couldn't do anything. The final one 100%. ........... (sigh of relief !!!)

  Are you sure? yes | no

Russell Leu wrote 06/19/2021 at 04:38 point

I was able to get mine running today, and it's also a 19309HU PIC18 - I flashed it while connected to a powered USB hub.  The 68000 is a power hungry chip and was quite warm after a few hours.  Trying to run it on an unpowered hub was impossible.  

  Are you sure? yes | no

gkaufman wrote 05/10/2021 at 14:31 point

PicKit3 "clone" worked easily to program the PIC18F47Q10, so another inexpensive option.

Boards went together nicely, thanks for another fun project!

I had 2 cpu's here - a MC68008P10 worked perfectly, but a MC68008P8 hangs detecting the BUS.  Do you think it might be speed related?  I built up 2 boards and it occurs with both (and the MC68008P10 runs fine in both).

  Are you sure? yes | no

villaromba wrote 05/10/2021 at 15:17 point

That's good news! I have a PicKit3 which I'll try and remember how to use again. I have all parts now for my board except the PCB which should arrive from China anytime now. 

  Are you sure? yes | no

Just4Fun wrote 05/11/2021 at 08:14 point

Hi, strange... I'm using a MC68008P8 on one of the three assembled boards without any problem. I've used another MC68008P8 also on the first prototype on breadboard (running @ 8MHz). The person who is making the kits and the assembled version is currently using the MC68008P8 without problems too (he is using the Pickit3 too...).

  Are you sure? yes | no

gkaufman wrote 05/11/2021 at 14:28 point

Perhaps I have a defective MC68008P8.  Is the circuit dependent on the xtal frequency or could I try a slower one?

  Are you sure? yes | no

Just4Fun wrote 05/12/2021 at 12:01 point

The serial ports and some parts of the code are time dependent, and were tuned for a CPU clock @ 8MHZ and a MCU clock 64/4MHz. So I'm not sure if the whole thing can work using i.e a 8MHz (instead of 16MHz) quartz.

You can just try it with the MC68008P10 at first (remember that the default serial speed will be 57600 bps) and check if it works. If it works then you can try to use the MC68008P8.

  Are you sure? yes | no

Just4Fun wrote 05/20/2021 at 10:41 point

I've just ordered another MC68008P8 to try it  (instead of a MC68008P10)...

  Are you sure? yes | no

brane331133 wrote 04/13/2021 at 18:40 point

So, going off 68K already ?

Shame. 68SEC000+ that PIC could make great two-chip QL...

  Are you sure? yes | no

proto raven wrote 04/13/2021 at 11:17 point

Is there a native C compiler for this setup like there is for the z80-MBC2?

  Are you sure? yes | no

Just4Fun wrote 04/13/2021 at 13:21 point

Yes, there is the DRI C compiler that was released with the CP/M-68K distribution disks. I've added also the DRI CBASIC compiler. I've found also another C compiler, but not tested yet. Also FORTH83 is available around.

  Are you sure? yes | no

brane331133 wrote 04/12/2021 at 21:24 point

It's not true that you can't have 68008 in CMOS flavor.

You can have 68EC000 (5V)  or 68SEC000 ( 3.3V). Both have internal de/multiplexer that can be activated by strapping one pin to GND (IIRC) after which a chip behaves like 68008.

It also seems that you could have done good part of video circuitry and more with PIC.

Perhaps keyboard scanning etc. AND SRAM emulation.

PIC32MK1024GPE100 is $6-ish apicece and could do most of that, icluding DMA transferes to internal and external memory, COM ports, OTG USB, RTC etcetc.

  Are you sure? yes | no

Just4Fun wrote 04/13/2021 at 08:53 point

Hi, thanks for the info!

I've used here the most simple and cheap parts available, so only DIP TH parts (as for the others XXX-MBC boards).

I've in my "to do" list (might be the next thing...) another board "to make experiments" with a 68SEC000 CPU, a STM32 MCU and a Cyclone IV FPGA. Of course will be a more complex board (likely 4-layer PCB and all SMD) to build.

  Are you sure? yes | no

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates