Hi Jens :) On Sat, Sep 24, 2016 at 05:46:36PM +0200, Jens Bauer wrote: > I'll try making sure I execute "stm32f1x mass_erase 0" and report back. :) > [perhaps I should bring some boards with me to the harbour as well.]
Debug: 510 6279 stm32f1x.c:179 stm32x_wait_status_busy(): status: 0x10 Error: 511 6279 stm32f1x.c:190 stm32x_wait_status_busy(): stm32x device protected So just as I suspected, it's protected. mass_erase should help with that. Or probably "stm32f1x unlock 0". -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
