SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

   With System Workbench for Linux, Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world.
And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4.
You can get more information from the ac6-tools website and download two short videos (registration required) highlighting:

System Workbench for STM32

Flashing without connecting NRST


why is it necessary to connect the NRST of my MCU to the ST-Link? I have no problem connecting to the target with the ST-Link utility but I do have problem flashing/debugging when I use SW4STM32. Well, problems is an understatement: it’s impossible.

My target is the infamous STM32 Blue Pill (STM32F103C8T6). The reset pin is exposed, but on the 4-pin SWD connector (has gnd, swio, swclk, and 3.3V).

The ST-Link utility is clearly able to reset/half the target via some SWD commands, it seems. I believe openocd supports that as well. See http://openocd.org/doc/html/Reset-Configuration.htmlQuestion

Has somebody got a clue whether it’s working? If so, where would I add the openocd options to switch from hardware reset (via NRST) to emulation reset (via SWD commands)?

In debugger configuration, Debugger tab, Configuration Script, Mode Setup, Reset mode combo box, select “Software system reset”
That works like a charm. That setting is somewhat hidden though.