1a6a549857
Working on programming AVR chips exposes a glaring omission in my first design of the SPI Relay: not allowing multiple devices make this task hard. I constantly have to unplug my SD card before, plug the AVR chip holder, then play a bit, then unplug the AVR holder, then replug the SD card... My prototype for a SPI relay design is built, but I haven't tested it yet. I need to adapt the code first, which is what I do here. When the prototype is tested, I'll update the SDC recipe with a new schema. |
||
|---|---|---|
| .. | ||
| hw | ||
| libz80@8a1f935daa | ||
| .gitignore | ||
| Makefile | ||
| README.md | ||
| emul.c | ||
| emul.h | ||
| forth.c | ||
| xcomp.fs | ||
README.md
emul
This folder contains a couple of tools running under the libz80 emulator.
Requirements
You need ncurses to build the forth executable. In debian-based distros,
it's libncurses5-dev.
Build
First, make sure that the libz80 git submodule is checked out. If not, run
git submodule init && git submodule update.
After that, you can run make and it builds the forth interpreter.
Usage
The ./forth executable here works like the one in /cvm, except that it runs
under an emulated z80 machine instead of running natively. Refer to
/cvm/README.md for details.
Not real hardware
./forth doesn't try to emulate real hardware
because the goal here is to facilitate "high level" development.
These apps run on imaginary hardware and use many cheats to simplify I/Os.
For real hardware emulation (which helps developing drivers), see the hw
folder.