Re: [Amforth] Development request

2013-02-27 Thread Mikael Nordman
On Wed, 2013-02-27 at 22:01 +0100, Matthias Trute wrote: > Mikael, > > >> >From checking your code, I can imagine a few things that would break > >> FF as well. ;) > > I am interested to know what that could be. > > In flashforth.asm I found the following lines > > rcall DOLIT >

Re: [Amforth] Development request

2013-02-27 Thread Matthias Trute
Mikael, >> >From checking your code, I can imagine a few things that would break >> FF as well. ;) > I am interested to know what that could be. In flashforth.asm I found the following lines rcall DOLIT .dw dp_start rcall FETCH rcall TRUE_ call

Re: [Amforth] Development request

2013-02-27 Thread Mikael Nordman
On Wed, 2013-02-27 at 19:59 +0100, Matthias Trute wrote: > You drive me crazy ;) Well it was not my intention :-; > >From checking your code, I can imagine a few things that would break > FF as well. ;) I am interested to know what that could be. I guess it can break but remarkably seldom. Everyt

Re: [Amforth] Development request

2013-02-27 Thread Matthias Trute
You drive me crazy ;) > For your information, FlashForth has these robustness mechanisms built > in. One may find the new recipe "Unbreakable" worth studying. http://amforth.sourceforge.net/TG/recipes/Unbreakable.html Some information may be new, some are rather hidden. Some ideas are from Mich

Re: [Amforth] Development request

2013-02-26 Thread Enoch
Mikael Nordman writes: > Hi Enoch, > For your information, FlashForth has these robustness mechanisms built > in. > > The aim has been to make it so robust that a reflash should never be > needed. > > The Kernel is write protected, the memory allocation pointers in eeprom > are initialized from w

Re: [Amforth] Development request

2013-02-26 Thread Mikael Nordman
Hi Enoch, For your information, FlashForth has these robustness mechanisms built in. The aim has been to make it so robust that a reflash should never be needed. The Kernel is write protected, the memory allocation pointers in eeprom are initialized from write protected flash with the EMPTY comma

Re: [Amforth] Development request

2013-02-20 Thread Matthias Trute
Hi, > MARKER is great for development, and I use it as well, but it is not > good enough in production situation: > > Let's say we are consultants and ship an Amforth based "blackbox" to a > client whose firmware we loaded before shipping via JTAG. When this > firmware needs a bug fix or an upgr

Re: [Amforth] Development request

2013-02-20 Thread Michael Kalus
Hi. Am 20.02.2013 um 10:16 schrieb Enoch: >> So, do I see this right? >> WIPE restores a known state. This state needs to be calculated at >> assembly time. Yes. >> It includes the initial state of eeprom, wordlist and >> other pointers, user area, disabling tasks ... where do you stop? >> Do

Re: [Amforth] Development request

2013-02-20 Thread Michael Kalus
Hi Enoch. Am 20.02.2013 um 04:35 schrieb Enoch: .. > Honored to meet you, the "4e4th" guy :-) To tell the truth, most of 4e4th is Camelforth, so Brad deserves the honor. Dirk Brühl is the guy with most of the ideas that brought it onto MSP430 LaunchPad. And Ulrich Hoffmann contributed as wel

Re: [Amforth] Development request

2013-02-20 Thread Enoch
Erich Waelde writes: > Hi Enoch, > > On 02/19/2013 10:36 PM, Enoch wrote: >> G'day to you to you all, >> >> I found something that seems to me useful on http://www.4e4th.eu/ >> >> WIPE ( -- ) Back to original status. Stacks unchanged. uarea back to >> original. >> >> Having an asm based word

Re: [Amforth] Development request

2013-02-20 Thread Erich Waelde
Hi Enoch, On 02/19/2013 10:36 PM, Enoch wrote: > G'day to you to you all, > > I found something that seems to me useful on http://www.4e4th.eu/ > > WIPE ( -- ) Back to original status. Stacks unchanged. uarea back to > original. > > Having an asm based word which restores the system into its o

Re: [Amforth] Development request

2013-02-19 Thread Enoch
"Michael Kalus" writes: > Hi. > >> Comments? > > > :-) > > > > Michael > Honored to meet you, the "4e4th" guy :-) To become current with Forth I review code by other OSS Forth projects. Another that deserves attention, IMHO, is the Open Firmware . In a

Re: [Amforth] Development request

2013-02-19 Thread Michael Kalus
Hi. > Comments? :-) Michael Am 19.02.2013 um 22:36 schrieb Enoch: > G'day to you to you all, > > I found something that seems to me useful on http://www.4e4th.eu/ > > WIPE ( -- ) Back to original status. Stacks unchanged. uarea back to > original. > > Having an asm based word which res

[Amforth] Development request

2013-02-19 Thread Enoch
G'day to you to you all, I found something that seems to me useful on http://www.4e4th.eu/ WIPE ( -- ) Back to original status. Stacks unchanged. uarea back to original. Having an asm based word which restores the system into its original Amforth state, both Flash & EEPROM content, means that o