Hello, I'm using openOCD 0.11.0 RC1 on a raspberry pi 3. Further I'm using an Atmel (Microchip) SAMD20G17 on my own developed testboard. The security bit will be set from the controller source code.
On the web page " <http://openocd.org/doc/html/Flash-Commands.html> http://openocd.org/doc/html/Flash-Commands.html"; (chapter "at91samd set-security") I have found this: . Warning: at this time, openocd will not be able to communicate with a secured chip and it is therefore not possible to chip-erase it without using another tool. In the new version 0.11.0 RC1 I have seen some changes in the file "src\flash\nor\at91samd.c". So my hope was that the chip erase issue was maybe fixed. But it doesn't. My request is to understand the technical reason why it is not possible to execute a chip erase on a secured chip. The controller datasheet describes how a chip can be erased. Even if the security bit is set. For this reason, I am interested in why it is not possible for openOCD. Can someone help me to understand that problem? That would be very nice. Best regards, Marcel
_______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
