Re: [Openocd-development] STM32: "flash write_image" has an alignment issue and flash protect/erase is broken

[Øyvind H. <oyv...@zy...>]

On Thu, Nov 19, 2009 at 11:46 PM, Johnny Halfmoon
<jha...@mi...> wrote:
> Hiya,
>
> I've found a few issues in OpenOCD and thought that I'd share before hacking a solution together. The following revision is used:
>
> commit 8f446fcf676e9cd13cf53d9946f0cae5d29a10ec
> Date:   Thu Nov 19 13:23:49 2009 -0800
>
> When doing "flash write_image erase unlock image.bin 0x8000000 bin" on an STM32, the following error is generated:
>
> auto erase enabled
> auto unlock enabled
> Info : device id = 0x20036410
> Info : flash size = 128kbytes
> Warn : Error: start and end sectors must be on a 4 sector boundary
> Error: failed setting protection for areas 0 to 21 (-901)
>
> So it seems we need write_image to be a bit smarter and do some boundary
> aligning before doing the unprotect / erase.

Could you include a debug_level 3 trace?

The conclusion seems a bit premature based on the limited information
above.


-- 
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer