Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
blog:retro_z80_mark4 [2019/11/21 15:00] – john | blog:retro_z80_mark4 [2019/11/21 21:42] (current) – [Upgrades - Accelerated Graphics] john | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Z180 Mark IV Single Board Computer ====== | ====== Z180 Mark IV Single Board Computer ====== | ||
+ | |||
+ | There is a thriving community of enthusiasts who design and build their own computers from scratch, not just buying ready-built parts, but laying out pcb's, writing the firmware etc. | ||
+ | |||
+ | Check out: https:// | ||
+ | |||
+ | A few years back I thought I'd have a go at assembling my own system from some of the designs on that site. I chose the [[https:// | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | |||
+ | ==== Initial Mark IV Build, Backplane and IO ==== | ||
8 slot ECB backplane board | 8 slot ECB backplane board | ||
- | {{: | + | {{: |
+ | |||
+ | ... see if you can spot the < | ||
Building and programming the PropIO peripheral controller | Building and programming the PropIO peripheral controller | ||
- | {{: | + | |
+ | {{: | ||
Testing VGA and keyboard functionality of the peripheral controller | Testing VGA and keyboard functionality of the peripheral controller | ||
- | {{: | + | |
+ | {{: | ||
Running the Z180 Mark IV test rom | Running the Z180 Mark IV test rom | ||
- | {{: | + | |
+ | {{: | ||
Output from UNA BIOS on the Mark IV, using a traditional serial terminal | Output from UNA BIOS on the Mark IV, using a traditional serial terminal | ||
- | {{: | + | |
+ | {{: | ||
Output from UNA BIOS on the Mark IV, using the peripheral controller board | Output from UNA BIOS on the Mark IV, using the peripheral controller board | ||
- | {{: | + | |
+ | {{: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Z180 Mark IV Software ==== | ||
+ | |||
+ | In addition to a specific firmware which needs to be programmed into the peripheral controller, to make the Mark IV board work, you need at least some level of firmware/ | ||
+ | |||
+ | * ROM: [[https:// | ||
+ | * ROM: [[https:// | ||
+ | |||
+ | Then once you have a rom for the board(s), you need an operating system, unless you're going to write applications direct for the hardware: | ||
+ | |||
+ | * OS: [[https:// | ||
+ | * OS: [[https:// | ||
+ | * OS: [[http:// | ||
+ | |||
+ | There are others, but //UNACPM// and //ROMWBW// are the main ones and are [[https:// | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Upgrades - USB Interface ==== | ||
+ | |||
+ | TBD | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Upgrades - Accelerated Graphics ==== | ||
+ | |||
+ | How do you display graphics on a text-mode Z80 based system? Well you don't, without some serious ingenuity or workarounds! | ||
+ | |||
+ | My idea is to interface to a Raspberry Pi (Zero) and essentially use it as a command-driven GPU accelerator; | ||
+ | |||
+ | On the Mark IV side we'll need some translation layer that turns (for example) SDL_CreateSurface() or SDL_BlitSurface() calls into simple ASCII strings that can be sent over an interface we can talk to the Pi on (serial? i2c? spi?), then remap them to native Linux SDL functions once they' | ||
+ | |||
+ | Work in progress is here: https:// | ||
+ | |||
+ | Main article page yet to be created... |