On 22 December 2014 at 06:58, Jens Bauer <jens-li...@gpio.dk> wrote: > Hi Paul. > > The reason I made a mdw 0, is that I understood that 0x08000000 is mapped to > 0x00000000 by default. > Anyway, before I unlocked the board, All I got from OpenOCD was... > > in procedure 'mdw' > > ...for both 'mdw 0' and 'mdw 0x08000000' (I know by now that "in procedure > 'mdw'" means 'read error' or 'access error'. > Now both shows data as 0xffffffff, which is (what I) expected. > > Before going into details on the steps I used to try mass-erasing, I'd like > to ask if this is what it's expected to be: >> flash banks > #0 : stm32f4x.flash (stm32f2x) at 0x08000000, size 0x00100000, buswidth 0, > chipwidth 0 > > -I'm asking, because I'm used to working with the LPC43xx, where I defined > the banks like this: > target/lpc43xx-backup/lpc4337.cfg:flash bank flash_a lpc2000 0x1A000000 > 0x80000 0 0 $CHIPNAME.m4 lpc4300 96000 calc_checksum > target/lpc43xx-backup/lpc4337.cfg:flash bank flash_b lpc2000 0x1B000000 > 0x80000 0 0 $CHIPNAME.m4 lpc4300 96000 calc_checksum > > ... The STM32F4 is slightly different: > target/stm32f4x.cfg:flash bank $_FLASHNAME stm32f2x 0 0 0 0 $_TARGETNAME > >
Looking at the log you attached the cmds all look ok to me. May be the watchdog that is causing problems - see http://openocd.zylin.com/988 Cheers Spen ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
