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 original > Amforth state, both Flash& EEPROM content, means that on-site code > replacement can be done without a JTAG, etc. > > Comments?
"the original state" is what? So WIPE needs to store a copy of the first N eeprom Bytes elsewhere (done at assembly time) and then replace eeprom, user area and thus the stack pointers as well? > Stacks unchanged strikes me as odd. > > Thank you, Enoch. > > P/S Marker is not good enough: It does not restore the EEPROM. It > removes itself after application. Well marker does not remove itself. The defined word does. </nitpick> So, do I see this right? WIPE restores a known state. This state needs to be calculated at assembly time. It includes the initial state of eeprom, wordlist and other pointers, user area, disabling tasks ... where do you stop? Does wipe call COLD as well? Do you need to clear any interrupts, too? Does it restore the default interrupt handlers? No, I did not look at the code of WIPE. Well, I'm using marker a lot. And I don't see, how wipe would get me any further. The only time I need to reflash is when I screwed up something in the dictionary before the first marker or som flash based data structures. Cheers, Erich ------------------------------------------------------------------------------ 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
