Building the software

Getting started with the software for your new board is as simple as grabbing the source code from GitHub and compiling it for the board.

You'll need a m68k toolchain for this part - if you don't have one, you can easily install ours using Homebrew*.

We use git for version control and it's the easiest way to get the code and stay up to date, but you can also grab a zip-file if you prefer. No matter how you get the files the rest of the process is the same, so this document applies to both methods.


Step one - Get The Code

Before we can build the software, you'll need to get a copy of it onto your local machine. You can either use git, or download a zip file.

Using git

This is our preferred option, and it'll make it easy to stay up to date when we add new stuff. If you've never heard of git, check out this page for the lowdown.

If you're on macOS® or Linux, the chances are git is already installed. While we don't support Windows® directly, there is a version of Git for your platform, but you'll need to download it separately. We strongly recommend using a sane OS (e.g. Linux) in a virtual machine if you're on Windows - otherwise we're going to assume you already have advanced knowledge, as you'll already have built a custom cross-compiler for that platform. 

To clone the project, navigate to a suitable directory where you want to, and run:

git clone

This will probably take a few seconds, and will copy the very latest version of everything to your local computer. You'll get the code for everything from the sample programs to the code that runs the glue logic on the board, plus a ton of documentation other stuff. Once git has done its thing you'll find everything below your current directory, in a directory called rosco_m68k.

If you're interested in hardware hacking, you might also want to grab some additional design files, which we keep in a separate repository:

git clone

But these are totally optional - the main repository contains the main design files for the board alongside all the software.

Download a zip

If you don't want to use git, that's cool too - you can download the latest release as a zip file from the following links:


If you want to explore the project a bit before you download it, head on over to and have a look around - as well as the code, you'll find our issue tracker, documentation, and a bunch of other stuff. If you're interested in feeding back issues or contributing code, now would be a great time to sign up for a free GitHub account if you don't already have one!


Step two - Build!

Now you have the code locally you're ready to make sure you can build stuff. If you installed our toolchain, this part should be a breeze. 

Firstly, you'll need to build some library code that the other programs share. Execute the following:

cd rosco_m68k/code/software/libs
make install

This won't install anything globally on your machine, instead it will just build the libraries and put them in a standard place within the project where the other code can find them.

Now we're ready to build a program. Run the following commands:

cd ../adventure

Assuming everything's installed correctly, this should take a second or two, and will create a file called adventure.bin - this is a port of Jeff Tranter's Adventure to the rosco_m68k, and it's all ready for you to upload to your board and try out!

If you see any errors when building either the libraries or the example program, it's likely your m68k toolchain isn't complete. We highly recommend installing our toolchain from Homebrew, but if you've gone with the option of building it yourself then you'll have to do some debugging. If you're stuck you can always reach out on discord and we'll do what we can to help!

All you need to do now is make sure your rosco_m68k is connected to your computer and up and running, then use minicom (or your terminal of choice) to send the adventure.bin file to the board using the Kermit protocol. Once the board receives the binary it will automatically start running it, and you'll be playing a fresh new game of Adventure!


Next steps

Now that you've tested out the toolchain and know you can successfully build software for your rosco_m68k, it's time to have a look around at the rest of the examples, and maybe even start doing some coding yourself. 

The best and most up-to-date documentation can always be found in the project itself. You can either open up the files locally, or they're always available (with formatting) on GitHub. A good place to start is - you'll see a list of directories and files, and the for that directory if you scroll down a bit.

Whenever you navigate to a new directory that has a, you'll see the documentation right there!

Building the firmware & GAL code

If you opted to not receive pre-programmed ROMs or PLDs when you ordered your rosco_m68k, you'll be wanting to build the firmware and the GAL code.

You'll find what you need in the following locations:

  • rosco_m68k/code/firmware/rosco_m68k_v1
  • rosco_m68k/code/pld

You'll find fairly extensive documentation for the firmware here:

For the glue logic, we've included the compiled JEDEC files in Git. If you want to modify the code, you'll need to grab a copy of GALasm from here - it isn't included in the standard toolchain, but is easy to build with your platform compiler.

Once you've built them, there are scripts in each directory that will use minipro (included in the standard toolchain) to burn these to the appropriate chips. This will work fine if your EEPROM burner is supported by minipro - if not, you'll need to use the appropriate software that came with your burner.

As always, if you get stuck, give us a shout on discord and we'll help where we can.