This page is still being prepared. In the future you'll find here tutorials on etherforth and GA144 chip programming. For the time being, there is a simple application example.

LED demo application

This application needs an LED connected with its cathode to pin 500.17 of the target chip, and its anode to +3.3 V power supply. It is recommended to place a 470 Ω resistor in series as well.

First, we create a new working disk in DISK 000 as a copy of template DISK 001. This is done by executing following commands:

1 disk
0 disk

We send each line to interpreter with Enter key. Notice that it is not possible to execute more than one command at a time.

Now, we open block 20 in the editor with 20 edit, and enter the following code.

led demo
ether 4 load
500 led 22 code

Leave the editor, and save the current block with keep. Then enter the following into block 22.

500 led
on 00 20000 !b ;
off 02 0 !b ;
init io b! . . on ;
4 u 0 l 0 path send

Again, leave the editor, and save the current block with keep. The application is now ready to be launched with 20 load. If you made no typo when entering the code, the LED should immediately turn on.

In general, when there is any error in the source code (both in load and code blocks), the last command (such as 20 load) remains in the command line, and system does not respond to any key. In this case you have to reset the whole system.

That explains why it is a good idea to keep the current project on DISK 0, as this disk loads into SRAM after reset. Moreover, it is advisable to save (either one block with keep or whole disk with save, which takes more time) as often as possible. System hang up due to source code errors is not the only time when you'll need to reset it. For instance, a line overflow in editor is enough to crash the system. There are other caveats I'll describe in more detail in User's manual.