Loading...
 

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


Importing Demonstration Project - 2 Modes - Only One Works - UBUNTU

Hello Pascale,

The instructions in the “Documentation” => “System Workbench for STM32” => “Importing a Cube MX project” are for importing Cube MX projects, not Demonstration Projects. Although I did an import of a Cube MX project successfully it is not a Demonstration project.

It is indeed so when importing a project while NOT copying it in the Workspace from the Demonstrations folder in the STMCube Repository everything is fine. Obviously this cannot be the intention if we want to change the coding since it affect the original repository.

However when copying the project into the Workspace SW4STM32 instanly points out the linker problem in the Problem tab. And there one can see that SW4STM32 utilises absolute referencing to the linker sources. So how does SW4STM32 know to include my home folder name in this absolute file addressing? How did it get there when the repository is after all from ST who is unaware of my home folder name?

Thx for explaining.

Greets,
Ben