Re: [Amforth-devel] amforth application development cycle

[pito <pi...@vo...>]

Hi Christian, I am using XP:
1. my editor is PN (programmers notepad)
2. terminal is Mosaic Terminal (tuned for forth, drag and drop
capab., promt history)
3. editing in PN and draging files directly into MT, always "marker
-BLABLA" at the beginning of any forth code I do
4. when not happy do -BLABLA and you delete all the stuff you did
recently
5. When happy with my words I upload all final words I may need (my
"system setup", basically I have everything interesting from amforth
repository there as I have 128KB flash) and then I DOWNLOAD (via
avrdude) the whole image from atmega into a file called my.hex and
my.eep (currently ~20k, it takes ~30sek)
6. when a crash occures I burn back my.hex and my.eep only, it takes
40sec and I am fully back with everything I need.
7. So an incremental approach with periodic downloads of the atmega
flash and eeprom (!)images into a backup file. The way of flashing
the forth core and then upload of all the forth libs and then all my
own words via terminal is simply too langweilig for me. Pito