Skip to content

Support for e4thcom and STM8S001J3, faster NVM compilation

Compare
Choose a tag to compare
@TG9541 TG9541 released this 16 Sep 18:04
· 672 commits to master since this release

BINARY REMOVED DUE TO ISSUE #69

Please use the latest release instead!

e4thcom Support

e4thcom is a nifty terminal for embedded Forth systems that supports #include and basic dependency management with #require. The author contributed support for STM8EF that works with 2-wire (half-duplex), and 3-wire (full-duplex) serial interfaces. Thanks a lot!

FILE ... HAND is now disabled by default because the method used in e4thcom works better (e.g. a decent error indication with the BEL character, and indication of compile mode with OK like in noForth).

STM8S001J3M3 Support

STM8EF now supports the latest member of the STM8S low-density family: the STM8S001J3M3 in a hobby-friendly SO8N package.

STM8S001J3M3

The default configuration uses the STM8S UART1 in half-duplex mode (see issue #57 ) for the console. Connecting a PC-UART works as described in 2-wire communication​. Depending on your UART you may need a 10k pull-up resistor. Note that the risk that PD1/SWIM gets blocked is significantly reduced by using pin8 for the console. Alternating usage of pin8 for reading an analog sensor, or console communication, might work, too.

The default configuration uses the STM8S UART1 in half-duplex mode (see issue #57 ) for the console. Connecting a PC-UART works as explained in 2-wire communication. Depending on your UART you may need a 10k pull-up resistor. Note that there is very little risk that PD1/SWIM lock gets locked on your device when pin8 is used for the console. Alternative use of the pin for reading an analog sensor might work.

Faster Compilation in NVM Mode

Let's just say it's faster now (much faster, indeed), and let's forget that it should have been like that from the start ;-)

Forget Release v2.2.14

The binary release was OK, but due to a merge hick-up the source code in master was rubbish. Thanks to @timsoer for reporting issue #59 !