cancel
Showing results for 
Search instead for 
Did you mean: 

CubeIDE 18.1 does not create CubeMX project - no .ioc file

Hi,
I encountered the following problem on two different computers with different versions of STM32CubeIDE. I select File->New->STM32 Project, then i select MCU or Board and click to Finish. Then pops up window called "STM32 Project" to fill up project name. Usualy there is "next" button to select another features, like which CubeFW version to use etc. But now, the "next" button is greyed out. Probably due field called "Target Project type" with greyed out option "STM32 Cube". When i hit "finish" button, IDE creates empty project without ioc file - in other words it does not open CubeMX to configure project.

I am not aware of interfering with the IDE in any way (plus I observed it on two independent PCs). I am including screenshots.

Thanks,
Michal

Version of CubeMXVersion of CubeMXCubeFW is actualCubeFW is actualEmpty projectEmpty projectmissing option to use Cubemissing option to use Cube



1 ACCEPTED SOLUTION

Accepted Solutions
Souhaib MAZHOUD
ST Employee

Hello @Michal Dudka 

Please use the latest version of CubeIDE 1.19.0, the same issue is discussed here.

 

BR,

Souhaib

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.

View solution in original post

7 REPLIES 7
Souhaib MAZHOUD
ST Employee

Hello @Michal Dudka 

Please use the latest version of CubeIDE 1.19.0, the same issue is discussed here.

 

BR,

Souhaib

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.

Andrew Neil
Super User

Can confirm this with v1.18.1 on Win11-Pro.

Nucleo-F030 as target.

Maybe the key is that 'STM32Cube' is disabled in 'Target Project Type' - so it can only create an 'Empty' project?

AndrewNeil_0-1752567642040.png

 

Same issue here - confirmed by many:

https://community.st.com/t5/stm32cubeide-mcus/stm32-targeted-project-type-is-empty-and-its-not-generating-ioc/m-p/819652

Looks like it's a bug v1.18.1 - solution is to use v1.19.0 instead.

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Sorry, sir, but this is not a solution. There are situation in which people want to maintain a stable ide version with the libraries from that version and so on, and updating to a new version can be not acceptable. Is there a way to enable the generation of ioc file on older releases? Btw, the 1.19 linux installer ( at least the debian one ) fails to write the appropriate rules files, so on a clean system the user need to manually copy the rules on rules.d .
Are there plans to release a more usable version that doesn't  break the old installations?

Screenshot from 2025-07-15 15-49-07.png

read the linked threads - there are workarounds listed there.

See also: 

https://community.st.com/t5/stm32cubeide-mcus/ioc-file-not-generating/m-p/822500/highlight/true#M37461

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Thx for your reply.

Btw all the solutions proposed end with "you should update your STM32CubeIDE to the latest version 1.19.0", and is the base of my question as I need to maintain the old 1.16 and 1.18 because our fw was developed on those and was sent to our customers.
Removing the . files on my platform has no effects at all, and changing the work area too has no effects.
So, seems to me a solution is not yet available, am I correct?

Regards

Filippo

 

The problem is with creating new projects - so if you're just maintaining old ones, it shouldn't matter?

 

But it does seem that something has recently broken...

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Thx for your reply.

I understand, seems not a real issue, but the point is we have to maintain currently 3 different versions, 2 for the running systems on 16 and 18, and the 1 for new ioc generation. I'm thinking to usb drivers, external tools like fatfs and lwip and so on. Additionally an ioc generated on 19 is not immediately compatible with 16 and 18.
It's really annoying thou.
The big surprise was that it broke silently, without any intervention, no update or something like that, and on 3 different pcs with only the 16 installed, and unused from months.
This make me think there are hidden updates, and what happened yesterday could happen tomorrow again and are hours of work.

Anyway thank you for your help.

Filippo