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


You are viewing a reply to Starting with SW4STM32  

Starting with SW4STM32

Hi

The point is that CubeMX generated code generally do not fit the the “firmware” examples in STM32Cube_FW_F0_V1.5.0, STM32Cube_FW_F1_V1.4.0, STM32Cube_FW_F3_V1.6.0, STM32Cube_FW_F4_V1.11.0, STM32Cube_FW_L0_V1.5.0, STM32Cube_FW_L1_V1.4.0, ... One can not import an example project into AC6 and then modify it by CubeMX thereafter.

See also the discussion https://community.st.com/thread/34173-usb-cdc-example-cubeQuestion

My approach is to generate the initial code by CubeMX and then using the examples and the HAL documentation to write my own code. This way I can recreate the project any time by CubeMX changing the usage of the peripherie.

What makes things even worse is the fact, that updates of CubeMX can break existing code. Last example is user_diskio.c. It was all user code before CubeMX 4.16. Now CubeMX insists here of function names beginning with user_

Please find examples of my solutions here https://github.com/nichtgedacht/mini-sys/Question

Dieter