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 -BLAB
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
Hi Karl,
its really difficult to communicate with you. I sent a lot of
emails recently, no-one seem to reach you...
> I can make the .asm files available if anyone is interested...
I am.
And if you could please re-send your user guide to me again,
I've got only old versions from 2007 (at leas
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
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
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
