stlink: STM32H750: GDB breakpoints do not halt execution

I made serious effort to avoid creating duplicate or nearly similar issue
Programmer/board type: Stlink/v2-clone
Operating system and version: st-util: Armbian Linux, a Debian 10 derivative. gdb: macOS 10.15.6
Stlink tools version and/or git commit hash: 1e20921
Stlink command line tool name: st-util
Target chip: STM32H750VBT6

Command line output:

$ /Applications/ARM/bin/arm-none-eabi-gdb fmplayground-h7.elf
(gdb) tar ext 172.16.3.114:4242
(gdb) b FmPlaygroundMain.c:46
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: <redacted>/fmplayground-h7.elf

Expected/description: The execution should stop at the specified breakpoint location, which is inside main(). I also tried various other locations, but it never stops. The same setup works with various other STM32 devices and other st-link versions.

This is a followup to #1011 .

Thanks for your effort!

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 26 (11 by maintainers)

Most upvoted comments

Hey, I found something interesting: If I start the program through the debugger, then hit the reset button on the dev board, from then on it stops at every breakpoint I throw at it! However, when I want to continue execution, it stops at the same breakpoint again without actually executing anything.

Maybe this is important: In my projects I exclusively use the 4-pin SWD connection (SWDIO, SWCLK, 3.3V and GND) and don’t connect the reset pin.

@Ant-ON I’m going to test your branch now.

cmdrf on Oct 29, 2020