collapseos/emul
Virgil Dupras 177e70580f sms/kbd: begin rewriting ps2ctl to Forth
So far, the resulting binary matches.
2020-05-17 14:24:27 -04:00
..
hw sms: WIP ! 2020-05-14 22:15:31 -04:00
libz80@8a1f935daa Move "emul" folder to root 2019-12-31 13:34:24 -05:00
.gitignore emul: rename stage2 to stage 2020-05-14 10:55:39 -04:00
avra.sh sms/kbd: begin rewriting ps2ctl to Forth 2020-05-17 14:24:27 -04:00
emul.c By default, allocate about 0x100 bytes for PSP+RSP 2020-05-14 18:41:09 -04:00
emul.h By default, allocate about 0x100 bytes for PSP+RSP 2020-05-14 18:41:09 -04:00
forth.bin core: define H@ a bit sooner 2020-05-15 22:59:38 -04:00
forth.c Make INTERPRET break on ASCII EOT 2020-05-13 21:44:46 -04:00
Makefile emul: rename stage2 to stage 2020-05-14 10:55:39 -04:00
README.md Update READMEs 2020-05-03 12:51:21 -04:00
stage.c By default, allocate about 0x100 bytes for PSP+RSP 2020-05-14 18:41:09 -04:00
xcomp.fs Move Cross-compiled core from B390 to B350 2020-05-15 22:44:49 -04:00
zasm.sh avra: first steps 2020-05-16 09:51:02 -04:00

emul

This folder contains a couple of tools running under the libz80 emulator.

Not real hardware

In the few emulated apps described below, we don'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.

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.

Run ./forth to get the COllapse OS prompt. Type 0 LIST for help.

Problems?

If the libz80-wrapped zasm executable works badly (hangs, spew garbage, etc.), it's probably because you've broken your bootstrap binaries. They're easy to mistakenly break. To verify if you've done that, look at your git status. If forth.bin is modified, try resetting it and then run make clean all. Things should go better afterwards.

If that doesn't work, there's also the nuclear option of git reset --hard and git clean -fxd.

If that still doesn't work, it might be because the current commit you're on is broken, but that is rather rare: the repo on Github is plugged on Travis and it checks that everything is smooth.