2025-03-19 3:01 AM
Hello everyone,
I am currently working on an STM32H745ZI-Q dual-core project and want to generate the code using CubeMX, compile and flash it with PlatformIO, and use CLion as my development environment.
My primary goal is to understand the best approach for setting up a dual-core project with these tools, particularly how boot configuration, toolchain selection, and PlatformIO integration should be handled. Below are my key questions and observations.
I want to use CubeMX for code generation and then compile, flash, and debug using PlatformIO within CLion.
CubeMX requires selecting a Toolchain/IDE when generating code.
Currently, CubeMX has the "Dual Core Boot Mode" field greyed out, and it is set to "Both CPUs booting at once". While this setup is fine for me, I want to understand whether it is possible to boot CM7 first and start CM4 later.
Since I use PlatformIO, I need to ensure both cores are flashed and debugged correctly.
I have structured my platformio.ini as follows, separating the M7 and M4 environments:
When generating the project with CubeMX, I noticed that some expected startup files are missing, including:
However, I do see a file in the Common folder named:
system_stm32h7xx_dualcore_boot_cm4_cm7.c
Is this file meant to replace the missing startup files?
I appreciate any insights from those who have set up, compiled, flashed, and debugged an STM32H745 dual-core project using CubeMX and PlatformIO in CLion.
Thanks in advance!
Leon
2025-03-19 3:07 AM - edited 2025-03-19 3:08 AM
Hello @eon and welcome to the community,
For Platformio environement, better to ask them on their community on this link.
On this community, we can help on ST dev environment: STM32CubeMx/STM32CubeIDE/STM32CubeProgrammer etc ..