Senior

Solved

Importing STM32CubeMX project into STM32CubeIDE - Missing Build Options

Forum|Forum|1 month ago
April 29, 2026
5 replies
466 views

Hi,

I created a project in STM32CubeMX 6.17.0 targeting the NUCLEO-G491RE and successfully generated the code. I then imported the project into STM32CubeIDE 2.1.1 and as far as I can tell it looks ok. The only apparent issue was that when I clicked on the .ioc file I thought that the STM32CubeMX project was supposed to open inside STM32CubeIDE but instead I get an error saying:

Screenshot 2026-04-29 at 15.01.07.png

So that's one issue. But when I come to build the project in STM32CubeIDE there is no Build All (CMD+B) option available, or indeed any other build options available.

This is the folder structure:

Screenshot 2026-04-29 at 15.07.37.png

What is missing from this workflow to create a project that can be built in STM32CubeIDE please?

Kind regards,

Al

Best answer by unsigned_char_array

You selected EWARM as an IDE in STM32CubeMX, not STM32CubeIDE.

I always generate under root.
This is the difference in project structure:

Not under root:

project.ioc
.mxproject
Core/
Drivers/
STM32CubeIDE/
 .project
 .cproject
 .settings
 STM32*_FLASH.ld

under root:

project.ioc
.mxproject
Core/
Drivers/
.project
.cproject
.settings
STM32*_FLASH.ld

If you generate not under root you need to open the STM32CubeIDE folder in STM32CubeIDE, not the root folder.

Additionally I recommend this setting:

This is easier with version control. Only peripherals that are changed will have changed files.

@alw wrote:
what is the recommended workflow for making changes in STM32CubeMX and then updating STM32CubeIDE please (without overwriting existing user code in main.c)?

By writing all user code in the appropriate user code sections. Sometimes this can be tricky. I can help you with that. All the user code we write is never overwritten. Our policy is that regenerating in STM32CubeMX doesn't lead to changes.

Ghofrane GSOURI

Technical Moderator

Hello @alw

Actually STM32CubeMX is no longer integrated inside STM32CubeIDE. Instead, the two tools are interoperable.

For more details , please check the following LINKs:

STM32CubeIDE 2.0.0 workflow tutorial - STMicroelectronics Community

STM32CubeIDE 2.0 release - early heads-up! - STMicroelectronics Community

The missing Build All option usually means CubeIDE does not recognize what you imported as a valid STM32CubeIDE managed C/C++ project .The fix is to reopen the .ioc in STM32CubeMX, set Project Manager > Toolchain/IDE = STM32CubeIDE, regenerate the code, make sure the project root contains .project and .cproject files, then import it into CubeIDE using File > Import > General > Existing Projects into Workspace

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

A

alwAuthor

Senior

Hi @Ghofrane GSOURI

I'm aware that they are two separate applications now, but read that clicking the .ioc in STM32CubeIDE would open the graphical view of the device pinout in STM32CubeMX to allow changes to the .ioc file. It would seem that this isn't the case.

If I've already imported a project from STM32CubeMX into STM32CubeIDE, what is the recommended workflow if I want to make changes to the .ioc file please? Is there any documentation that provides an explanation of the migration of this workflow from STM32CubeIDE 1.x please?

Kind regards,

Al

Ghofrane GSOURI

Technical Moderator

Hello @alw

Try to open the .ioc using STM32CUbeMX following those steps:

- Launch STM32CubeMX 6.17.0

- Go to File > Load Project
- Browse to the project folder
- Select the required .ioc file
- Click Open

If the project opens correctly there, you can make your hardware/configuration changes in CubeMX, then regenerate the code with Toolchain / IDE = STM32CubeIDE

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

A

alwAuthor

Senior

Thanks @Ghofrane GSOURI

I now have the project toolchain specified as STM32CubeIDE, and the folder structure looks like this when imported into STM32CubeIDE:

Screenshot 2026-04-29 at 15.54.33.png

I still don't have the ability to build the project, what is missing from the workflow please?

Kind regards,

Al

Ghofrane GSOURI

Technical Moderator

Hello @alw

Could you please provide your IOC ?

I am waiting for your feedback .

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

A

alwAuthor

Senior

Hi @Ghofrane GSOURI

Please see attached, all I'm doing at this stage is setting up SAI1 for I2S receive and transmit.

Kind regards,

Al

240628_WISA_DELAY.ioc

Ghofrane GSOURI

Technical Moderator

Hello @alw

A good next step would be to copy the .ioc file into a clean new folder, open it with STM32CubeMX 6.17.0 (as described in my second comment) generate the code again with STM32CubeIDE selected as the project toolchain, and then try building that fresh project.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

A

alwAuthor

Senior

Hi @Ghofrane GSOURI

I had it build successfully one time when I followed your instructions, but then tried it again in a newly created project folder and I still had the same problem with no build options available. I'll investigate more and will post what I find.

Should the 'Generate Under Root' option be ticked next to the Toolchain/IDE selection in STM32CubeMX please?

Kind regards,

Al

U

unsigned_char_arrayAnswer

Lead III

You selected EWARM as an IDE in STM32CubeMX, not STM32CubeIDE.

I always generate under root.
This is the difference in project structure:

Not under root:

project.ioc
.mxproject
Core/
Drivers/
STM32CubeIDE/
 .project
 .cproject
 .settings
 STM32*_FLASH.ld

under root:

project.ioc
.mxproject
Core/
Drivers/
.project
.cproject
.settings
STM32*_FLASH.ld

If you generate not under root you need to open the STM32CubeIDE folder in STM32CubeIDE, not the root folder.

Additionally I recommend this setting:

This is easier with version control. Only peripherals that are changed will have changed files.

@alw wrote:
what is the recommended workflow for making changes in STM32CubeMX and then updating STM32CubeIDE please (without overwriting existing user code in main.c)?

By writing all user code in the appropriate user code sections. Sometimes this can be tricky. I can help you with that. All the user code we write is never overwritten. Our policy is that regenerating in STM32CubeMX doesn't lead to changes.

"Kudo posts if you have the same problem and kudo replies if the solution works.Click ""Accept as Solution"" if a reply solved your problem. If no solution was posted please answer with your own."

A

alwAuthor

Senior

Hi @unsigned_char_array

Thanks very much, I've got all the above working now.

Kind regards,

Al

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded