6502/of816
1
0
Fork 0
mirror of https://github.com/mgcaret/of816.git synced 2025-03-06 13:30:23 +00:00
Code Issues Projects Releases Wiki Activity

Neon816: README update

Browse Source
This commit is contained in:
mgcaret 2019-12-14 15:14:02 -08:00
parent 343dd83cdd
commit 2c886a982e
1 changed files with 63 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

75
platforms/Neon816/README.md
View File

@ -1,21 +1,36 @@
# Neon816
This is a port to Lenore Byron's [Neon816](https://hackaday.io/project/164325-neon816) system. The Neon816 Developer Edition ships with a small 16-bit Forth.
This is a port to Lenore Byron's [Neon816](https://hackaday.io/project/164325-neon816) system. The Neon816 Developer
Edition ships with a small 16-bit Forth.
OF816 for the Neon816 is configured to run as an alternative firmware out of bank $20. With a little ajustment, it could be configured to run out of bank $21 (but starting it is an excercise for the reader).
OF816 for the Neon816 is configured to run as an alternative firmware out of bank $20. With a little ajustment, it
could be configured to run out of bank $21 (but starting it is an excercise for the reader).
It configures the MMU and serial port like NeonFORTH does. The direct page, stack, and return stack occupy the first $400 bytes of RAM.
It configures the MMU and serial port like NeonFORTH does. The direct page, stack, and return stack occupy the first
$400 bytes of RAM.
To build OF816 for the Neon816, change to the platform directory and run
``build.sh``. It will output a 64K binary named ``of816-neon.bin`` that can be flashed into the Neon's firmware. See below for installation instructions.
``build.sh``. It will output a 64K binary named ``of816-neon.bin`` that can be flashed into the Neon's firmware.
See below for installation instructions.
## Port Features
Hopefully this section will be filled up with stuff that works like Lenore's
Forth. See the [Neon816 Manual](https://cdn.hackaday.io/files/1643257030480800/sysmanual.pdf). But right now, it's just a bare port with no system-specific extensions.
Hardware access words with the same semantics as NeonFORTH are found in the NEON816 dictionary.
## Installation
The hardware access dictionary is currently not complete but has the words for accessing the PS/2 ports, I2C2,
and VDC.
Execute ``also neon816`` to gain access to the words.
See the [Neon816 Manual](https://cdn.hackaday.io/files/1643257030480800/sysmanual.pdf) for descriptions of the
specific words.
## Installation / Removal
The instructions assume you are running Linux. The Neon firmware loader is supported under Linux only.
### Installing OF816
**THIS WILL OVERWRITE THE NEON'S ORIGINAL FIRMWARE!**
@ -23,11 +38,15 @@ Forth. See the [Neon816 Manual](https://cdn.hackaday.io/files/1643257030480800/
**READ _ALL_ OF THE FOLLOWING BEFORE PROCEEDING AND DO NOT PROCEED IF ANY OF THIS MAKES YOU UNCOMFORTABLE!**
After building the firmware image, the image must be converted to Intel Hex format. I like the bin2hex tool found [here](https://grumpf.hope-2000.org) (page is in German). Build the ``bin2hex`` binary and execute: ``bin2hex of816-neon.bin > of816-neon.hex``
After building the firmware image, the image must be converted to Intel Hex format. I like the bin2hex tool originally
found [here](https://grumpf.hope-2000.org) (page is in German), also in my [Github repo](https://github.com/mgcaret/bin2hex).
Build the ``bin2hex`` binary and execute: ``bin2hex of816-neon.bin > of816-neon.hex``
Once you have the .hex file, you will need to use the [Neon firmware loader](https://hackaday.io/project/164325-neon816) to install the image. This requires an FTDI cable connected to the 3.3V UART header on the Neon816 system board.
Once you have the .hex file, you will need to use the [Neon firmware loader](https://hackaday.io/project/164325-neon816)
to install the image. This requires an FTDI cable connected to the 3.3V UART header on the Neon816 system board.
To back up the original firmware, you will need to add an additional command routine to neonprog.cpp (add it after the write command):
To back up the original firmware, you will need to add an additional command routine to neonprog.cpp (add it after the
write command):
```
else if(!strcmp(cmd,"dumprom")) {
@ -59,8 +78,40 @@ build neonprog then start it with ``neonprog /dev/ttyUSBx`` (replace device with
From within neonprog, execute ``dumprom backup.bin`` to save an image of both ROM banks to ``backup.bin``.
Once the backup has finished (it will take a while), you can proceed to the installation of OF816 with ``flash of816-neon.hex``. This will also take a while. When it is done, reset your Neon and OF816 should start.
Once the backup has finished (it will take a while), you can proceed to the installation of OF816 with
``flash of816-neon.hex``. This will also take a while. When it is done, reset your Neon and OF816 should start.
## Restoring the Original NeonFORTH Firmware
Since the Neon (at the time of this writing) only ships with the first bank of flash occupied, first, split your backup with ``split -b 65536 backup.bin``. This will output two files, ``xaa`` and ``xab`` that are bank $20 and bank $21, respectively. Then run ``bin2hex xaa > neonforth.hex``. You can then flash this with neonprog using ``flash neonforth.hex``. Once it's done, reset your Neon and you should see the original firmware running.
Since the Neon (at the time of this writing) only ships with the first bank of flash occupied, first, split your backup
with ``split -b 65536 backup.bin``. This will output two files, ``xaa`` and ``xab`` that are bank $20 and bank $21,
respectively. Then run ``bin2hex xaa > neonforth.hex``. You can then flash this with neonprog using
``flash neonforth.hex``. Once it's done, reset your Neon and you should see the original firmware running.
## A Comparison of OF816 and NeonFORTH
NeonFORTH, which comes with the Neon816, is a compact 16-bit Forth specifically designed for the system by its creator.
OF816 is a portable 32-bit Forth that is designed to run on many 65816 systems. As a result of its 32-bit cells, it has
a flat view of the 65816 address space. A negative consequence is that it is slower and uses more memory than a system
like NeonFORTH.
A general comparison:
| OF816 | NeonFORTH |
|------------------------------------------|----------------------------------------------|
| 32-bit cells | 16-bit cells |
| First-class access to '816 address space | Special words to access memory beyond bank 0 |
| Slower | Faster |
| More RAM/ROM use | Less RAM/ROM use |
| ANSI standard Forth | Not ANSI standard |
| FCode support | No FCode support |
| Larger dictionary | Smaller dictionary |
Additionally, as NeonFORTH is maintained by the creator of the Neon816, it is going to have features specific to the
Neon816 sooner than OF816 will have them.
Overall, NeonFORTH is small, and well suited to basic experiments with the Neon816's hardware. OF816 is more powerful
in the large built-in dictionary, and in the way it handles numbers, address space, exceptions, and stack over/
underflow. However, this makes it slower and use more memory.