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

You are viewing a reply to Linux and External Tools  

Linux and External Tools


I recommend you to install the external tools (OpenOCD in particular) because this version was modified to support the latest ST boards which might not be supported yet by the last OpenOCD release.

If you don’t install them, you can modify the compiler path in the project settings and the OpenOCD path in the debug configuration. It should work as well.

If you install the external tools, they are installed in the Eclipse plugin directory (ECLIPSE_DIR/plugins/fr.ac6.mcu.externaltools.openocd.linux64.xxxxxxx) and no system environement variable is used nor modified to launch these tools so it should not disturb your system, and no conficts with the IDE.


To whom it may concern,

as OpenOCD in SW4STM32 contains changes to OpenOCD from OpenOCD.org, the sources should be somehow accessible. Best would be that AC6 cares for getting the patches into opneocd, but I understand that gerrit and openocd’s patch review policy is quite a big obstacle. I would also care, as time allows, but that requires access to the source or even better to your repository. So, where are the sources or where is your openocd repository?



Hi Kevin,

As Indicated on page About System Workbench for STM32 the source code for the version of OpenOCD we ship with System Workbench for STM32 has to be a patched version, as the standard version do not support all recent STM32 chips; this source code can be accessed by cloning our source base from the GIT server listed on this page.

ST people push their changes to the official development base but, as you know, getting them through takes some time so, as we want to provide support for th enew chips as soon as they are available, we need to integrate these patches ourselves and provide a custom OpenOCD version.

Bernard (Ac6)

Hi Bernard,

I am not Kevin, but Uwe (Bonnes).

I am in the process of separating and releasing the patches to OpenOCD/Gerrit. Please review!