When we want to debug only the M7 core, we use the following line and connect from VsCode:
/c/ST/STM32CubeIDE_1.14.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.win32_2.2.200.202505060755/tools/bin/ST-LINK_gdbserver.exe -cp '/c/ST/STM32CubeIDE_1.14.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.2.200.202503041107/tools/bin/' -d -e -v -m 0 -g
But the problem is that always the whole processor is reset because of the following as described in
https://www.st.com/resource/en/user_manual/um2576-stm32cubeide-stlink-gdb-server-stmicroelectronics.pdf
-g, --attach
Attaches to the running target.
Attach is aimed to be used to connect to a running program in the device without doing a reset or
downloading a new program.
[STM32_Programmer_CLI is always started with “mode=UR reset=hwRst” so that a device reset is
done when loading a new program independent of this option. This guarantees that the flashing of the
device is made correctly.]
In our configuration the M7 is off after power on (BCM7 unchecked).
And the M4 is our main processor which starts the M7 afterwards.
When we then want to debug the M7, the whole hardware is reset and the debugger can't connect to the M7 anymore and crashes.
Is there a way to change to reset software or reset core?
