cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeIDE 2.0 detached STM32CubeMX problem

JensH
Associate III

Hello,

I tested the new STM32CubeIDE 2.0 today and was initially confused that CubeMX opened when I double-clicked on the *.ioc file. However, this is listed as a new feature in the release notes.


Unfortunately, this feature completely destroys my projects.
When the code is generated, these settings in the CubeIDE project change:
- Targeted Language changes from C++ to C
- Linked folders are deleted
- Configurations: DEBUG, SYSTEM added
- Linker file settings from own configurations deleted

Did I make a mistake in the settings? Why is the project changed so much?

Best regards,
Jens

19 REPLIES 19

Hello @JensH ,

 

The issue is confirmed: Restoring previously the deleted DEBUG/RELEASE configurations on STM32CubeIDE 2.0

and reported to the dedicated to the Dedicated Team.

Your contribution and interaction are greatly appreciated.

 

Best Regards.

Mahmoud

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.

Theodore-henry6
Associate II

Hello Jens,

This isn’t a mistake on your side. In STM32CubeIDE 2.0, opening the *.ioc file automatically with CubeMX can overwrite project settings—switching C++ to C, deleting linked folders, adding new configurations, and removing custom linker files.

For now, the safest approach is either to avoid regenerating code from the .ioc file or use the standalone CubeMX. Many users have reported the same issue, so it seems to be a change in 2.0 rather than a misconfiguration.

Mahmoud Ben Romdhane
ST Employee

Hello @JensH @Theodore-henry6 @jd5 @MGogr.1 

 

The issue is confirmed: [Linked Folders are deleted] and reported to the dedicated to the Dedicated Team.

I will let you know when the issue is fixed.

 

Thanks.

Mahmoud

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.

JensH
Associate III

Hallo @Mahmoud Ben Romdhane ,

so am I right that everything I reported is confirmed and reported?

  1. Targeted language changes from C++ to C
  2. Linker file settings from own configurations deleted (because of switching from C++ to C)
  3. Configurations: DEBUG, SYSTEM added
  4. Variable linked folders are deleted

Best regards,

Jens

Can you make it like the previous version where we dont have to open.ioc file in MX Cube.

That will be really helpful.

another STM MCU FU!  This is not a fix. Don't they test even the basic functions before releasing updated FGS!

Teun888
Associate

There should really be an update in every type of documentation for this. I was just following the tutorial and the video from 5 years ago showed features I couldn't find. Including this rabbit hole I dove in to when I couldn't create a project with the graphical user interface in the IDE. Only to read the release notes for 2.0 afterward. Very frustrating!

While I agree it's bad that the documentation is out-of-date - especially with such a significant change - I don't think you can really complain about a 5 year old video not reflecting the latest version!

That's even older than v1.07.0 !

See this post for an up-to-date 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.

And I will totally agree with that. But then why do they have links to 5 year old videos in their documentation?
I'm not sure how I got to the video this afternoon but I think it was through the videos for tutorials directly in CubeIDE.


@Teun888 wrote:

why do they have links to 5 year old videos in their documentation?


That's a good question!

It should, at least, be clearly flagged that it relates to a (very) old version ...

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.