Re: [Amforth-devel] amforth application development cycle

2010-10-25 Thread Christian Kellermann
Hi pito et al., thanks for all your suggestions. After a weekend with amforth this turns out to be a minor issue that now comes naturally. The marker hint proved valuable as well as the upload script. I had to modify it to use the python serial lib to make it work on OpenBSD though. Thanks for a

Re: [Amforth-devel] amforth application development cycle

2010-10-21 Thread Erich Waelde
Hi Christian, On 10/21/2010 04:54 PM, Christian Kellermann wrote: > Dear amforth'ers, > > During my playtime with amforth I always wonder how to develop > longer dictionaries with the device. > > What I am doing now is: > > - try out wording at the amforth prompt. > - transfer changes to a diction

Re: [Amforth-devel] amforth application development cycle

2010-10-21 Thread Matthias Trute
Hi, First: I do development on my desk, not in the forest or beneth the roof. Whenever I'm satisfied with a new version, I copy the flash/eeprom content from the working controller to hex files (avrdude can do reads as well as writes) and transfer those files to the final target systems (one by

Re: [Amforth-devel] amforth application development cycle

2010-10-21 Thread Karl Lunt
I can't speak for all of the amforth'ers, but I can tell you what I do. I have a set of words (in assembler) that support the Microchip 25LC512 serial EEPROM. These words allow me to save and restore a full system image on my ATmega328P. By "full system image" I mean flash from 0 to dp and

[Amforth-devel] amforth application development cycle

2010-10-21 Thread Christian Kellermann
Dear amforth'ers, During my playtime with amforth I always wonder how to develop longer dictionaries with the device. What I am doing now is: - try out wording at the amforth prompt. - transfer changes to a dictionary file. - flash the device with the standard image. - use a little program to in