Mikael Nordman <mikael.nord...@pp1.inet.fi> 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 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. > > MARKER is also supported. it restores flash, eeprom and ram allocation > pointers. > > > BR Mikael > > http://flashforth.sourceforge.net
Thanks, I thought that your work was just Microchip centric. Generally speaking, I prefer OSS development efforts to be merge-ing rather than fork-ing :-) Before selecting "Amforth" I tested the "avrforth" project which I found quite dormant. Project development activity is one of the deciding factors and Amforth, thanks to Matthias relentless work, gets very high marks. Sincerely, Enoch. > > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_feb ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
