unable to debug stm32f4 target

[rvl13]

I have recently installed following toolchain on my machine and I am unable to debug STM32F4 discovery, attached are the logs and screenshot of the debugger.

• OS/Hardware : Windows 10 on Intel i5-6200U
• Toolchain : GNAT FSF 12.2.0 for arm-eabi, GPRBUILD 22.0.0, gnatstudio 23.0w
• Dev board : STM32F4 discovery

GDB_log.txt

As per the screenshot, :

• the load command fails because it seems like gdb is unable to parse path with backslashes. hence I issue load command again with forward slashes instead. and it loads the executable.
• After that, issuing the "monitor reset halt" has no effect, it surely resets the target, but does not halt it.
• And hence because of it, none of the step/continue commands work.
• Note that I have enabled the debugging information flag (-g) in project properties.

Additionally, I also have community 2019 arm toolchain installed and debugging just works fine using the same, hence I do not think this is an issue with the st-link gdb-server installation.

Please let me know if more information is required.

Thanks,
rvl13

[Fabien-Chouteau]

Hello @rvl13 , unfortunately I don't understand why the monitor reset halt command would work with one version of GDB and not the other.

There is a GDB command to enable some debug info: set debug remote 1. You can try to use it and compare the results using both versions.