Skip to main content
DSimp.1
DSimp.1
Associate III
February 22, 2022
Solved

STM32CubeIde cant find .ioc file

  • February 22, 2022
  • 1 reply
  • 7553 views

Hello,

I changed cubeIDE project structure, put files to folders to make it look cleaner, then changed project location. I managed to fix all linker errors etc. code builds and flashes, but the problem I encounter is that when I try to open cubeMx file I get error.

Is there a way to make .ioc file active project file? It is the same file just in other location, which was linked in paths.

0693W00000Ka22LQAR.png

This topic has been closed for replies.
Best answer by mattias norlander

Hi,

If you use the "STM32Cube" project type inside CubeIDE, then CubeMX will require that the project name is not changed, and that the project structure is not modified in any significant way.

Yes, you can add new folders. But you cannot re-arrange any folders/files which are managed by CubeMX.

Moving or renaming the ioc-file is not allowed, this will break the project.

I think you have two options:

  1. Use STM32Cube projects and respect the contraints about folder/file organisation and naming.
  2. Rely on CDT project instead. CubeMX is not at all used. --> No files are generated into this project at all. But, you have full control of this project yourself.

I tend to use the STM32Cube project as a playground to test various peripheral configurations and generate the code.

Then I copy files and peripheral initialization code from the STM32Cube project into a CDT project. I consider the CDT project to be my real development/production project.

1 reply

mattias norlander
mattias norlanderBest answer
ST Employee
February 25, 2022

Hi,

If you use the "STM32Cube" project type inside CubeIDE, then CubeMX will require that the project name is not changed, and that the project structure is not modified in any significant way.

Yes, you can add new folders. But you cannot re-arrange any folders/files which are managed by CubeMX.

Moving or renaming the ioc-file is not allowed, this will break the project.

I think you have two options:

  1. Use STM32Cube projects and respect the contraints about folder/file organisation and naming.
  2. Rely on CDT project instead. CubeMX is not at all used. --> No files are generated into this project at all. But, you have full control of this project yourself.

I tend to use the STM32Cube project as a playground to test various peripheral configurations and generate the code.

Then I copy files and peripheral initialization code from the STM32Cube project into a CDT project. I consider the CDT project to be my real development/production project.

Terms & ConditionsAccessibility statement