Re: [Amforth] Development request

[Matthias T. <mt...@we...>]

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 Michael (long ago) and some details still
need to be worked on. But that I will leave as an exercise
to the reader..

> 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 command.
> 
> At boot time all dynamic data is first initialized from write protected
> flash.
> It is then up to the application to do whatever further initialization
> that is needed. That also includes setting up the application dependent
> IRQ vectors in ram. 

>From checking your code, I can imagine a few things that would break
FF as well. ;)

Matthias