larsbrinkhoff / xforth Goto Github PK

• 8051
  • C8051F330: Silicon Labs ToolStick
• AVR
  • ATtiny85: Adafruit Trinket
  • ATtiny13A: Cheepit Sparrow
  • ATmega328P: on breadboard
• Cortex-M
  • STM32L011K4T6 Cortex-M0+: STM Nucleo-32
• MSP430
  • TI Launchpad
    • MSP430F2012IN
    • MSP430G2452IN23
    • MSP430G2553IN20
• PIC
  • PIC16F1619: Microchip Curiosity DM164137
• STM8
  • STM8S103F3P6 : noname breakout board

Add library for using an UART on targets that have it.

I'm trying to build a Docker image that contains the dependencies in test/deps.sh. However, I fail to understand the environment dependencies:

root@4481fedadce4:/xForth.git/trunk# sh -e test/deps.sh
+ install_lbforth
+ test -f /root/bin/forth
+ cd lbForth
test/deps.sh: 5: cd: can't cd to lbForth

I guess that this has is related with a Travis-CI environment dependency ($HOME). Help in understanding the assumptions and dependencies of test/deps.sh would be appreciated!

Optional library for interrupt handling.

It would be very useful for applications to have the MS word available.

Perhaps there should be a bsp directory with files for board support packages.

Add a new chapter to document the assemblers.

Add library for accessing timers.

Optional library for digital I/O.

Unclear what kind of abstraction might work across many targets.

The Z80 still enjoys some popularity.

Contemporary parts include Z8, eZ8, eZ80, Z810, Rabbit.

Add features to write the image into a connected target.

Two varietes spring to mind:

• Bare metal. Program though JTAG/UART/what have you.
• Live Forth. Send commands to a target-resident Forth.

I like minicomputers.

• PDP-8
• PDP-11 (lbForth already works in Unix V7)
• Nova
• TI-990

8-bit devices:

• 6502
• 68HC05/08/RS08
• 8051
• AVR
• H8/300L
• PIC (just midrange for now)
• ST6
• STM8

16-bit devices:

• MSP430
• PIC24 (dsPIC)
• MAXQ20
• R8C
• RL78
• H8/300H
• 68HC11/12
• 68HC16
• C166/C167/ST10/XE2000

32-bit devices:

• Cortex-M, in particular M0
• Xtensa (ESP8266)
• RISC-V
• PIC32 (MIPS)
• ARC
• ColdFire
• MicroBlaze

Add support for DOES>.

This isn't really an issue, but it's convenient to make notes here.

• 6502
  • naken (beta)
• 68HC08 / RS08?
  • fortyn by @kulp
• 68HC11
  • binutils/gdb
• 8051
  • emu8051
  • ucsim
• AVR
  • simulavr
  • naken
  • ucsim
• ColdFire
  • qemu
  • coldfire
• H8/300
  • binutils/gdb
• MSP430
  • naken
• Nova
  • simh
• PDP-8
  • simh
• PDP-10
  • simh
• PDP-11
  • simh
• PIC
  • gpsim
• RL78
  • binutils/gdb
• RX
  • binutils/gdb
  • softgun
• STM8
  • ucsim
• V850
  • binutils/gdb
• Xtensa
  • qemu
• Z80
  • ucsim

USB stack. Phew!

Add words for multitasking. TASK, PAUSE, etc. User variables?

Add optional library with an interpreter. Just interpretation, no compilation mode.

Depends on UART (#52), or other character I/O.

https://github.com/mschuldt/rtx2000_simulator

PIC-like devices from Padauk: http://www.padauk.com.tw/

There is a software emulator for the PDK14 here: https://github.com/free-pdk/fppa-pdk-tools

Where applicable, make negate fall through into 1+.

: negate   invert [  \ Fall through, no ;
: 1+   1 + ;

Add DEFER, IS, ACTION-OF, DEFER@, and DEFER!.

A deferred word should probably compile to a single jump instruction.

IS should work at both compile time and run time.

A perennial favourite.

If this becomes a thing, here is some information. Including a blink test program:
http://www.fischl.de/thomas/elektronik/r8c/

This might come in handy:
https://github.com/msalau/rl78flash

The test should be improved.

• Cover all run-time words
• Check more than one invocation
• Ensure stack depth isn't off after execution of each word

Rumor has it these are still in use.

This doesn't work:

1 constant foo
foo allot

Add library for traditional blocks. Maybe adjust block size as required by flash sectors.