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 a CubeMX project with Debug and Release Targets

Hi,
I have successfully used CubeMX for initialisation of a custom STM32F411 based development board which was then imported into a System Workbench project which I was able to build and debug successfully using an ST-LINK V2 debug probe.

However, if I create a new C project in System Workbench I get the options to create both a Debug and Release configuration. In addition I have options to include the Cube HAL source code into the project etc.

When I imported the CubeMX project into System Workbench I could not find a way setup both Debug and Release configurations.

Is there some procedure which will allow me to import/create a System Workbench project that uses the initialsation code generated by CubeMX and also provide me with a Debug and Release configuration? I also need to be able to use CubeMX to update the initialisation code arbitrarily?

What is the recommended optimisation level for the CubeMX generated code?

Regards
FarmerJo

Hi FarmerJo,
Once you imported a CubeMX generated project into SW4STM32, you may want to create / manage the (build) configurations using :
- Right-click on your project >> Properties >> C/C++ Build >> Manage Configurations button (on the top right side of the window);

This IOC file (CubeMX extension) can be reopened and updated in CubeMX.
Warning, the user code must be located in between the beacons/tags :

/* USER CODE BEGIN # */
/* USER CODE END # */

... else it will be lost.

I would recommend -Og optimization at the beginning.
Then, when the application is functional, you may switch to :
-Os to reduce the generated code size (but with lower performances);
-O3 to get high performance application (but with a bigger ode size);

Hi Vetch,
Thats just what I ws looking for, many thanks.
Regards
FarmerJo