Hi Matthias,

This message is of considerable interest to me as I am a long time devotee
of the MSP430 and CamelForth. I have an even longer relationship with Forth
and have followed Amforth with a mostly academic interest until recently
when, here at work, we have started using AVR micro's. Unfortunately, the
ATtiny parts we are using don't have enough memory for Amforth, but I am
becoming much more familiar with all things AVR. Mike Kohn's first version
of naken_asm was for the MSP430 and I was pleased to find on a recent visit
to his site that he now also supports AVR parts. This cross-pollination
should benefit both communities: MSP430/CamelForth and AVR/Amforth. By the
way, I hope you don't mind that I've taken the liberty of copying Brad on
this message.

Around the same time I re-found an old TI Stellaris
> Lauchpad that I got a year or two ago from my
> friends at the German Forth society and spent a few
> hours with 4€4th and camelforth for the msp430.
>

A minor correction: TI did sell a Stellaris Launchpad that used an
ARM-based micro, but I believe that you're referring to the MSP430
Launchpad here.

-John



On Wed, Nov 12, 2014 at 3:16 PM, Matthias Trute <mtr...@web.de> wrote:

> Hi,
>
> It's time to disclose the secret around the license change.
>
> A few months ago I started playing with the naken_asm by
> Mike Kohn to get rid of the Atmel assembler. The first
> changes were easy, some things were difficult to achieve
> but one show stopper finally kncked me out: The naken_asm
> cannot generate a hex file for initialized EEPROM content.
>
> Around the same time I re-found an old TI Stellaris
> Lauchpad that I got a year or two ago from my
> friends at the German Forth society and spent a few
> hours with 4€4th and camelforth for the msp430. It was not
> that difficult to get them working, the differences to amforth
> are small but annoying (for me at least). The source code was a
> real surprise: almost like amforth. The same implementation
> strategy (indirect threaded) and even the pre-assembled
> forth code for many words is *really* close.
>
> So I started to closely examine the camelforth sources
> (Brad ported them to naken_asm earlier this year) to follow
> the amforth style (that is: many small source files with XT_*
> labels). A month ago or so I found a solution to have the
> same source code for both assemblers: the naken_asm for the
> MSP430 part and the Atmel assembler for the AVR8's.
>
> Since Brad's code is GPLv3 I had to change the amforth license
> to that level too to be compliant, not that I really liked
> or enjoyed it, but law is law and beer is beer.
>
> Finally: rev 1702 is a huge patch. It compiles and generates
> working images (for me at least). People who come from
> camelforth get a new command prompt. Exceptions and double
> cell number output (no input yet) are working too. Recognizers
> are almost done (need a way to put the recognizer stack
> into the INFO flash).
>
> Amforth users may find a long list of missing features, I'll
> work on it to make it shorter. Maybe, sometimes both controllers
> will have an identical feature set. Maybe this is impossible.
> Future will tell. For now the new code is highly experimental
> and not suitable for serious work, regressions are likly ;)
>
> Matthias
>
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Amforth-devel mailing list for http://amforth.sf.net/
Amforth-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amforth-devel

Reply via email to