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 upgrade we must provide the client with a > serial port based method of new firmware install (compiling/uploading > new Forth) without the client having to open the box. In which way would MARKER prohibit this scenario? A well designed application with in-field replaceable application code (the amforth core cannot be changed with WIPE btw) can place a strategic marker label that does all you want to do. One may want to re-check if the information, MARKER restores is sufficient, but that would be a bug in MARKER. > 4e4th is targetting educational applications. There too there's a need > for rapid "factory reset" between one student application to the next > one. An "unbreakable" amforth is possible as well. I came across this years ago but never really implemented it. It requires an atmega with an NRWW section big enough to hold the whole amforth core system. Since the NRWW section cannot be destroyd by amforth itself, there is only a copy of the EEPROM needed and a trigger that reprograms the EEPROM at boot time. Should be easy to implement. Finally: I do understand WIPE and the goals that one may want to achieve with it (IMHO its an alias for MARKER). But why on earth should this (rather complex) tool be implemented in assembly language? Matthias ------------------------------------------------------------------------------ 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
