Re: [OpenOCD-user] Flashing STM32 failed to read/write memory

[Eyal N. <ey...@ch...>]

Yes, changing to 0x08000000 fixed it.
Thanks!

On Sat, May 4, 2019, 09:43 André van Schoubroeck <an...@bl...>
wrote:

> On 03-05-2019 17:45, Eyal Niv wrote:
> > Hello,
> > I'm trying to use openOCD over FT2232 (emulating SWD) to flash\debug
> > an STM32F302 from SW4STM32 (OpenSTM system workbench).
> >
> > I ran into failures reading\writing memory when gdb is called from
> > SW4STM32 (see attachment for the relevant debug dump section).
> >
> > Side notes:
> >
> >   * I can run gdb and flash/debug from J-TRACE over SWD just fine
> >   * The same openOCD script over FT2232 (exactly the same setup) works
> >     fine with an STM32F303 (also from SW4STM32).
> >
> > Support will be highly appreciated.
> > Thanks,
> > -Eyal
> >
> >
> >
> >
> >
> > _______________________________________________
> > OpenOCD-user mailing list
> > Ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/openocd-user
>
> When I look at your output, I notice
>
>     Debug: 1939 19560 target.c:2030 target_write_buffer(): writing
> buffer of 1156 byte at 0x00000000
> and
>     Error: 1957 19654 arm_adi_v5.c:378 mem_ap_write(): Failed to write
> memory at 0x00000004
>
> This suggests you're linking your code at 0x00000000 in stead of
> 0x08000000, the address, where the flash exists.
> Even through the 0x00000000 is aliased to 0x08000000, you might try
> linking your code at 0x08000000 in stead of 0x00000000
>
> André
>
> --
> ------------------------------------------------------------
> an...@bl...               http://www.blaatschaap.be
> ------------------------------------------------------------
>
>
> _______________________________________________
> OpenOCD-user mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openocd-user
>