collapseos/emul
Virgil Dupras cbf5baf3b6 Pack core words a bit
This leaves space for xcomp-core which is growing.
2020-05-12 21:27:06 -04:00
..
hw ti84: we have a prompt 2020-05-09 14:28:55 -04:00
libz80@8a1f935daa Move "emul" folder to root 2019-12-31 13:34:24 -05:00
.gitignore Keep stage1 bootstrap bin instead of stage 0 2020-04-29 19:38:43 -04:00
emul.c Add emul_memdump() and stop automatically on ROM write 2020-04-09 08:26:41 -04:00
emul.h Add emul_memdump() and stop automatically on ROM write 2020-04-09 08:26:41 -04:00
forth.bin xcomp: add XCOMPILE and X[COMPILE] 2020-05-12 21:08:18 -04:00
forth.c Keep stage1 bootstrap bin instead of stage 0 2020-04-29 19:38:43 -04:00
Makefile Keep stage1 bootstrap bin instead of stage 0 2020-04-29 19:38:43 -04:00
README.md Update READMEs 2020-05-03 12:51:21 -04:00
stage1.fs Add word NL 2020-05-04 08:10:18 -04:00
stage.c Keep stage1 bootstrap bin instead of stage 0 2020-04-29 19:38:43 -04:00
xcomp.fs Pack core words a bit 2020-05-12 21:27:06 -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.