Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
STLinkGDB does not work with STM32F722
#1
Dear EmBitz,

The STLinkGDB does not work with STM32F722, while it works Ok with STM32F746.
The message:

Remote debugging using localhost:4242
0x010000000x01000000 in ?? ()
Connected
Loading section .isr_vector, size 0x1e0 lma 0x8000000
Note: automatically using hardware breakpoints for read-only addresses.
Error: Warning:Cannot insert hardware breakpoint 1:Remote communication error.  Target disconnected.: No error..

In previous similar case you asked for the device name and ID.
Here are the data:

Device STM32F72x/F73x
Device ID 0x452
Revision ID Rev A

I have an urgent project, which I do not want to switch to other toolchain.
Please, can you help me before the next release?

Thank you very much,

EmBitz member

vdaniel
Reply
#2
You could try what I wrote at 
https://www.embitz.org/forum/thread-773-...ml#pid5219
I don't know if it helps, but you could try.
The release information of this new gdb says : Added STM32F72xx73xx support
Reply
#3
(14-05-2018, 10:56 AM)FrankW Wrote: You could try what I wrote at 
https://www.embitz.org/forum/thread-773-...ml#pid5219
I don't know if it helps, but you could try.
The release information of this new gdb says :    Added STM32F72xx73xx support

Hi FrankW,

I tried. It writes a lot of messages, see attachment, but still does not work.

vdaniel


Attached Files Thumbnail(s)
   
Reply
#4
Well - to me it looks as if it is flashing 2048 bit page after 2048 bit page.
And after "found 8 HW breakpoint registers" - is that it ? Nothing more ?

As I said. I don't know if it works for you.
I had problems with my STM32F746G. the debugger could not connect to the USB port. With this version it is working.
In the relase message I found "Added STM32F72xx73xx support" - so I thought it might work for you as well.

I have to admit - I should switch off all this unnecessary debugging log messages.
I guess that makes is slower and is irritating.
Reply
#5
Hi FrankW,

Maybe you can find a time and compile again, switching off "all this unnecessary debugging log messages".
Then I will try again.

Great thanks,
vdaniel
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)