Skip to main content
MFred.2
MFred.2
Associate III
May 16, 2022
Question

In CubeIde: IOC file behavior after code generation !

  • May 16, 2022
  • 6 replies
  • 4967 views

With STM32CubeIde 1.9.0, open and change some settings in the IOC file, save your changes, and then click yes when a popup asks you to generate the code. At the end of the code generation, the IOC file is marked again as an unsaved file!

This topic has been closed for replies.

6 replies

MM..1
MM..1
Chief III
May 16, 2022

And what ?

Andrew Neil
Andrew Neil
Super User
May 16, 2022

@MM..1​ : I think the question is: "Why does the IOC file get marked as 'unsaved' ("dirty") when it hasn't been edited?"

@MFred.2​ : so has the IOC file actually changed?

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.
MM..1
MM..1
Chief III
May 16, 2022

I mean after generating is ioc marked / edited with generation info and result , but yes ...

Pavel A.
Pavel A.
Super User
May 16, 2022

> "Why does the IOC file get marked as 'unsaved' ("dirty") when it hasn't been edited?"

Changes in the view state are also saved in the .ioc file (zoom level, rotation of the chip view).

These changes do not affect code generation, can be discarded.

Andrew Neil
Andrew Neil
Super User
May 17, 2022

So not thought-through for revision control, then?

:persevering_face:

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.
Pavel A.
Super User
May 17, 2022

Looks so. There were many complaints that .ioc files are not friendly to revision control. No sign of progress.

MFred.2
MFred.2Author
Associate III
May 19, 2022

I confirm the behavior (bug),

open and change some parameters in the IOC file, save your changes, regenerate the code, at this time the file is saved. At the end of the code generation, the IOC file is again marked as an unsaved file!

And when you compile your project, a pop up asks you again: "Do you want to generate code?".

it's endless end

Andrew Neil
Andrew Neil
Super User
May 19, 2022

but did you check if any changes were made by/during the generation process - as suggested above?

if so, then it's correct that the file has changed!

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.
MFred.2
MFred.2Author
Associate III
May 19, 2022

When the code generation is in progress, a modal window displays the progress, it is impossible to modify anything

Andrew Neil
Andrew Neil
Super User
May 19, 2022

The file is modified by the build process!

Please go back through the earlier replies - it's been said before

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.
Khouloud OTHMAN
Khouloud OTHMAN
Associate
May 20, 2022

Hello @MFred.2​ ,

Thank you for having reported.

It seems that you're facing the same issue reported in this post, could you please check and confirm ?

Otherwise, could you please precise which MCU are you using and how did you exactly reproduced to observe this misbehavior ?

Thanks in advance.

Khouloud.

MFred.2
MFred.2Author
Associate III
May 20, 2022
Hello Khouloud,
Yes, this is the same problem.
I ‘m working with STM32CudeIde 1.9.0 with a STM32Cube example project (STM32U585).
1. Import example project
2. Open IOC file, and change one settings
3. Click save button (menu bar) -> (file saved)
4. In pop up, click yes to generate code
At the end of generation, file appear unsaved !
So, when you compil the projet, a pop up ask you to generate code from ioc file, …
Best regards
Frederic Mathieu
Andrew Neil
Andrew Neil
Super User
May 20, 2022

@Khouloud OTHMAN​ the other thread says there's an internal ticket on this.

Does that include addressing the problems mentioned above with revision control systems?

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.
Terms & ConditionsAccessibility statement