Development Workflow

This is my current development workflow that I use for general z80 development and developing any related whizz80 system software.

My development environment is setup on 2 seperate devices which are in 2 seperate locations. A Mac which is in my office, and a Raspberry Pi (running Raspbian) at my electronics workstation. I syncronize the sources between the 2 using a self-hosted git repository (as well as to github.com when i reach a milestone).

There are 5 major steps in my workflow. Each step is requies the previous step to be completed.

graph LR vim{1. Text
Editor} --> ASM[whizz80.z80] ASM --> zasm zasm{2. z80
Assembler} --> HEX[whizz80.hex] zasm --> LIST[whizz80.lst] HEX --> z80sim{3. z80
Simulator} HEX --> eeprom{4. Upload to EEPROM}

1. Text Editor

You need a way to write your z80 code with a text editor, any editor will do. Because I am developing on 2 different devices I need something simple and lightweight. I am currently using vim which is working well for me. I find it also helps if your chosen editor can also do syntax highlighting. All my z80 assembly code is saved as .z80 files.

2. z80 Assembler

Once you have your .z80 file you need to assemble them using an assembler. I am currently using zasm on the Mac.

zasm whizz80.z80 --opcodes --labels whizz80.hex (creates a whizz80.hex and whizz80.lst file)

I’ll probably end up putting all this into a nice Makefile to make my life a bit easier.

3. z80 Simulator

I am currently using the z80 simulator from the z80pack suite. I am only using the z80sim component. Why am I not using the z80asm assembler from the z80pack suite? It doesn’t appear to support assembler macros, and it is a rather simple assembler, with a small number of features. There was a limited amount of documentation to get me started with it. The z80pack simulator is nice as you can set software breakpoints and manipulate the z80 memory, registers and flags as you step through your code. It also has a nice text input and text output interface (using a virtual port 1) for debugging input/output devices.

z80sim -m FF (this runs the simulator and sets all memory to values to FF)

Once the simulator has started then you just r whizz80.hex and start simulating.

I did come across another z80 simulator which looked really nice and with a tty terminal front end to display all the z80 registers, memory, etc, however I couldn’t get it to compile on my mac (suspect its a 64-bit thing), and I didn’t really want to run a separate virtual linux machine just to run a simulator. Shame really - it looks pretty.

4. Upload to EEPROM

Once I am happy with my hex output file, I need to do some real testing on some real hardware. I have a TL866+ programmer that I can just upload the hex files into my EEPROM. Because I’m running on a mac I use the minipro which you have to download and compile yourself.