Re: [OpenOCD-devel] Stange behaviour with STM32F7 and freshly built OpenOCD

[<bo...@el...>]

Rocco Marco Guglielmi writes:
> I thought I was clear. Let me point out some statements
> 
>   • The code is loaded in 0x0800 0000 (LMA) and executed at 0x0020 0000 (VMA)
>     in line with Freddie suggestion
>   • The flash procedure works as expected (even after error, on target reset
>     the code is executed properly)
>   • On a previous version of openocd (Open On-Chip Debugger
>     0.10.0+dev-00226-g1c2e3d41d) we noticed no problem with the same identical
>     code
>   • The issue seems related to the inability of OpenOCD to place a breakpoint
>     in the VMA.
> 
> To me, it sounds like a regression but I cannot be sure.
> Ciao,
Sorry for adding confusion!

What does "info mem" in gdb tell. Is the 0x00200000 region marked as
memory or flash? Probably this reasoning applies:
If the 0x00200000 region is not marked as flash, gdb assumes it to be
RAM. So gdb thinks it can use a normal RAM breakpoint by writing BRK
to that address. This obvious does not work with flash.

I have to look at the blackmagic code too.

Bye
-- 
Uwe Bonnes                bo...@el...

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------