7cad9ffe40
There wasn't much of a reason to leave a loop early on 0x0d or null. The idea was that once you have a CR or null, the rest is garbage and you shouldn't see it. However, it brought a problem: In VE, you couldn't insert characters past that limit. It would be written, but never displayed. So let's get rid of this logic and simply always display a 64x16 grid. |
||
|---|---|---|
| .. | ||
| hw | ||
| libz80@8a1f935daa | ||
| .gitignore | ||
| avra.sh | ||
| emul.c | ||
| emul.h | ||
| forth.bin | ||
| forth.c | ||
| Makefile | ||
| README.md | ||
| stage.c | ||
| xcomp.fs | ||
| zasm.sh | ||
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.
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.
Usage
Run ./forth to get the Collapse OS prompt. Type 0 LIST for help.
The program is a curses interface with a limited, fixed size so that it can provide a AT-XY interface (which is yet to implement).
Problems?
If the forth 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.
A modified blkfs can also break things (although even with a completely broken
blkfs, you should still get to prompt), you might want to run make pack to
ensure that the blkfs file is in sync with the contents of the blk/ folder.
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.