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

New install on Win7 is broken

Installed install_sw4stm32_win_64bits-latest on Win7 machine, using default locations/options. I then created a test ‘C’ project using default options. The Console view appears to show the build running successfully, but the Problems view shows two errors:
Program “arm-none-eabi-g++” not found in PATH
Program “arm-none-eabi-gcc” not found in PATH
If I then open the file “src/system_stm32f4xx.c” the Problems list grows with dozens of errors such as:
Symbol ‘uint32_t’ could not be resolved
Type ‘FLASH_ACR_DCEN’ could not be resolved

This is a default installation that is installed as the developers intended and it is fundamentally broken right out of the box. Is it to much to expect the tool to actually work?



>Hi Alex,
These are known bugs we are working on; currently the workarounds are quite simple:

  1. For the “arm-none-eabi-g++” not found errors, these only appear while creating the project; if you just delete them from the Problems view.
  2. For the “could not be resolved” errors, this is due to the indexing not done correctly (often due to th eprevious error); you just have to right click on the project, then Index >> Rebuild and it should be OK then.

Hope this works for you,

Thank-you. I have now resolved the errors.

I was expecting that any know problems would be noted in release notes attached to the install package. When I install a new toolchain, I use “create and build default project” as a test that the toolchain is installed and working correctly. With no notes to the contrary, I was expecting the tool could do this cleanly without manual intervention from the user.