cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeIDE only generates Dual-Core structure

Discount_50
Associate II

Hello,

I am working with the STM32WL55CC (48-pin package). When I imported the official STM32CubeWL example projects from ST, I noticed that they provide both SINGLE CORE and DUAL CORE versions. But the board that these examples are listed under STM32WL55JCIX, which itself is a DUAL CORE device.

However, when I create a new project in STM32CubeIDE for the same device (STM32WL55JCIX), CubeIDE always generates a Dual-Core project structure (with CM4 and CM0+ folders). There is no option to generate a Single-Core project, even though the example projects clearly include one.

Also, the file structure of the official examples is very different from the structure generated by CubeIDE. Following the tutorials, example projects contain folders like Application/, Utilities/, and files like se-identity.h, But I am not able to find "se-identity.h"

Since I am developing for the STM32WL55CC (48-pin) variant, I am having trouble understanding how to properly port the example code (which is for WL55JC) to the WL55CC 48-pin device.

2 REPLIES 2
Issamos
Lead II

Hello @Discount_50 

For the first question, i remember that you can select the number of cores that you will use for your project on the same tab of the project name if you are using the CubeMX plugin of the CubeIDE. And if you are using the CubeMX in standalone version, you can select the number of cores once you select your MCU and click on the create project button using a pop-up that will appear to ask you if you want a single or a dual core project. 
For your second question, I do agree with you that the structure is different between examples and generated code. But all files you are looking for should be there. If you want a quick way to find them, you may use the search feature of the CubeIDE to search for the name of the file and you will find it or find where it is included so you can open it.

Best Regards

II

Discount_50
Associate II

Thank You, I am going to do so.