The zip file is in this gallery.
Nokia colour LCD displays in forth. My displays have epson controllers. These displays usually have green connectors. If you have a philips controller my code definitely will not work. Philips based display usually have brown connectors.
I doubt anyone will do a h256 build but if you do add the line "0 CONSTANT INITPER" to the GENERIC.DEF file.
There are also variations between batches of epson based displays. Some support 8 bit mode (mine don't) some have a two bytes per pixel mode (mine don't). In particular single pixel writes (as used by the line drawing code) may not work properly on some displays.
After that the backlight will blink as the board waits for a serial connection.
You can connect in two ways.
The simplest way to use EMFORTH is using a serial terminal such as hyperterminal. EMFORTH will send alternating plain text and emserver protocol packets to the serial line. Just hitting a terminal key will put forth into terminal mode.
The access the PC disk files you must use emserver but terminal mode is useful for simple programs and testing.
You can't rebuild forth in this mode but you can drag and drop source into hyper terminal or dump a text file.
There is no handshaking or buffering so to compile using a terminal you must insert a time delay between lines.
Terminal settings are 115Kbaud 8 data 1 stop no parity or handshake.
Emserver mode.If emforth can successfully ping the serial server it will enter emserver client mode. The server is a very old program and is fairly crude. It needs rewriting but this isn't going to happen any time soon.
The port to sharpdevelop has been shelved because if appears mono-develop is being ported to windows and this should provide a multi-platform IDE at last.
The server is a console (dos) program which requires real serial ports (not USB adapters).
The reason to use the server is to be able to compile files from disk with nested include files.
If everything is set up properly rebuilding forth becomes trivial but process can easily be broken as well.
The working directory for emserver has to point to the source directory (called system in this case). I do this by making a emserver shortcut and editing the properties.
The root source file for doing a rebuild is called arm.fth. At the top of the file you have to set the PCB type and whether you want nokia support. Just look at the file and you should be able to figure it out.
If you boot one of the builds I supplied you can do a rebuild by simply typing "SOURCE ARM.FTH" (without the quotes).
It should build, relocate and build the extras automatically.
A few hints are also printed.
The new build runs in ram. You can copy it to FLASH so it runs next time the board is booted but even then the forth will be copied to ram and run in ram.
You can create a version which executes mostly in FLASH by compiling the file "toflash.fth" ie "SOURCE TOFLASH.FTH".
You will again need to use MIRROR1 to commit this to flash. The kernel was already moved to the second 64K block of flash but MIRROR1 copies stuff which has to be setup at the bottom of memory.
For older displays try setting it to 1F ie type "HEX 1F LCDV1 !"
Test it by typing SPLASH - if it looks ok you can copy the ram image back to flash by typing MIRROR1.