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 (registration required) various documents highlighting:

System Workbench for STM32

Error in final launch sequence

Please can you assist me. I am using a custom STM32F103C8T board but am getting the following error:

Error in final launch sequence
Failed to execute MI command:
-target-select remote localhost:3333

I am searched through all the suggested fixes but have found none that works.

My .cfg file is as follows:

source find interface/stlink-v2.cfg

transport select “hla_swd”
source find target/stm32f1x_stlink.cfg
reset_config none

The strange bit is that if I try to use the NUCLEO-F401RE everything works fine and as expected.

I also only receive this error when debugging. Programming the device works well.

It seems there is an issue on SW4STM32 latest version (1.14.0) for “use local script” cfg file.
If the board cfg is in project workspace, it won’t be executed. That is the case for custom board created during a new project.
The workaround is either to copy the cfg elsewhere and to reselect it by browse button or to use the “manual spec” mode for the cfg.

If using the “manual spec” mode and for the boards that don’t have reset line connected from STlink, you can add
-c “reset_config none” in openocd options in debug config launch (debugger tab).


If I had only found this 4 hours ago biggrin

My problem came after upgrading to the current version. Flashing code would work just fine but debugging would fail.

My project lives outside the Eclipse workspace.

After a bit of experimenting, I think that using a local board file works fine as long as the project is inside the eclipse workspace.

It looks like you can have the board config file anywhere except in a project that is not in the workspace.

A strange bug. And incredibly frustrating. Someone owes me three hours sleep.

I may create a workspace folder that just has local board config files and only ever reference those.

BTW, if you use the “manual spec”, Eclipse just creates a hidden cgf file in the project folder. But that one works just fine!

Thank you Laurent for making this clear.

Hi Laurent

You are amazing! Thank you for this. I have struggled for days with this. Really appreciate your help!