Updating to STM32CubeIDE 2.1.1 - How to create IOC file?

alw · ‎2026-03-17

Hi,

Having just updated to STM32CubeIDE 2.1.1, I've created an STM32CubeIDE Empty Project (the only apparent relevant option) targeting the STM32F072 Discovery Kit as I want to experiment with the touch sensing capabilities, however when the project is created I don't see an IOC file.

Has the workflow reverted to using STM32CubeMX to create the IOC file etc. please?

Kind regards,

Al

Gyessine · ‎2026-03-17

Hello @alw

from the STM32CubIDE V2.0.0, the STM32CubeMX plug-in has been removed. So, the .ioc file is opened out of the STM32CubeIDE on the standalone version of the STM32CubeMX.

see STM32CubeIDE 2.0.0 released.
BR
Gyessine

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

alw · ‎2026-03-17

So apparently functionality removed form STM32CubeIDE which seems like a backwards step...

Gyessine · ‎2026-03-17

Hello @alw

from the STM32CubIDE V2.0.0, the STM32CubeMX plug-in has been removed. So, the .ioc file is opened out of the STM32CubeIDE on the standalone version of the STM32CubeMX.

see STM32CubeIDE 2.0.0 released.
BR
Gyessine

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 · ‎2026-03-17

@alw wrote:
So apparently functionality removed form STM32CubeIDE which seems like a backwards step...

It was also announced ahead of the v2.0.0 release: STM32CubeIDE 2.0 release - early heads-up!

See Version 2.0.0 - why remove MX ? for discussion and more on the rationale.

Note also: Introducing STM32CubeMX2, a new flavour of STM32CubeMX tool - having both integrated is probably impractical, so having both separate makes more sense ...

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.

Pavel A. · ‎2026-03-18

This is more adequately described as "The Cheese has moved!".

Andrew Neil · ‎2026-03-19

Ha ha! Brilliant - I'm stealing that!

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.

BWH · ‎2026-05-14

... it is not the solution how to create the *.ioc-File also for version 2.x but only the explanation why it is not there anymore! :(

Andrew Neil · ‎2026-05-14

If you read the linked article, it explains that CubeMX is used to create the .ioc file, and the OP already hinted at that.

See also: STM32CubeIDE 2.0.0 New workflow tutorial.

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.

BWH · ‎2026-05-15

...maybe the link is interesting for people who use CubeMX, I don't.

The original reason why I searched for the *.ioc-file was a hint somewhere in the internet that in order to create a terminal window for debug reasons you can write something into the *.ioc-file.

But I found another solution: I installed plugins for the topic terminal and then could create one at "window/show view/others->terminal. After configuring for my FTDI-USB modul (Baud rate etc) it worked fine.

But thanks for your comment!

Andrew Neil · ‎2026-05-15

Well, if you want an .ioc file, then you do have to use CubeMX* - the .ioc file is the CubeMX file.

* Whether standalone or, before v2.0.0, integrated into the IDE.

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.