Sorry for the resend, but I accidentally titled the last post incorrectly as stm32f103 instead of stm32f105 as the message details.
On Tue, May 10, 2011 at 3:38 PM, Rob Emanuele <r...@crystalfontz.com> wrote: > Greetings, > > I'm using a J-Link with openocd. It provides nice rtck support and is > great for debugging on some of the higher speed arm9 chips. > > I've use the Olimex ARM-USB-OCD in the past to program and debug > STM32F105 chips. When I try to use the J-Link to program the STM32 I > will always get an error: > >> flash write_image erase unlock standard/standard.elf > auto erase enabled > auto unlock enabled > device id = 0x10016418 > flash size = 256kbytes > Padding image section 0 with 0 bytes > flash memory not erased before writing > flash writing failed with error code: 0xfffffc7a > error writing to flash at address 0x08000000 at offset 0x00000000 (-902) > > If I perform a "stm32x mass_erase 0" first it programs just fine. > What about the J-Link code could be failing to erase the sectors first > that is done correctly with the Olimex? > > For programming the STM32F105 my config looks like this: > source [find interface/jlink.cfg] > set WORKAREASIZE 0x5000 > source [find target/stm32.cfg] > > Can someone tell me why I need the WORKAREASIZE too? > > Thanks, > > Rob > -- > Robert Emanuele > Crystalfontz America, Inc. > www.crystalfontz.com > r...@crystalfontz.com > +1 509 892 1200 > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
