On Wed, Oct 21, 2009 at 2:22 PM, Luca Ottaviano <[email protected]> wrote: > Øyvind Harboe ha scritto: >> >>> Unlocking flash is good. >> >> Thanks. I'll hold out a bit longer for any objections. > > I've been thinking about it in the past few days and I concluded that if the > protection is there, ignoring it would destroy its purpose, which is protect > from accidentally erasures.
There is a huge difference between stopping the JTAG debugger from modifying flash and the application running on the target device in standalone mode from modifying the flash. > Can't you just encode un-protect knowledge into the cpu specific config > file, in a function called unprotect() which can be called on request? Unprotect is available via an option to write_image or via the flash protect command, so it's done rather explicitly. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
