Skip to main content
qwer.asdf
Senior
October 20, 2015
Question

STM32CubeMX ''modified'' status of *.ioc files

  • October 20, 2015
  • 4 replies
  • 2276 views
Posted on October 20, 2015 at 10:24

Hi, it's a small but annoying bug, every time I open my *.ioc project file (which was gradually migrated 5-6 times from older versions) Cube immediately marks the project as modified (asterisk in the title just after the file name) and annoyingly asks to save the file when closing the Cube even when I changed nothing. Even when I agree to save the ''changes'', the next time I open the project it's in ''modified'' state again.

    This topic has been closed for replies.

    4 replies

    stm32cube-t
    ST Employee
    November 26, 2015
    Posted on November 26, 2015 at 18:26

    Dear user,

    Thank you for your feedback. The issue has been logged.

    Best regards

    Sirma Siang
    ST Employee
    November 2, 2016
    Posted on November 02, 2016 at 16:16

    Dear user,

    Thank you for your bug reporting.

    If you still facing this issue, could you please share your .ioc file and the operating system you are using ?

    Thanks in advance.

    Kind Regards

    Sirma

    Jeanne Joly
    Associate
    May 9, 2017
    Posted on May 09, 2017 at 14:59

    Hello

    qwer.asdf

    ,

    This issue is not seen in the last releases.

    Could you please upgrade your CubeMX release in order to avoid this issue?

    BR. Eric

    David Littell
    Senior II
    May 9, 2017
    Posted on May 09, 2017 at 21:27

    Using 4.20.1 under Linux I see the project become 'modified' just by browsing around and looking at things. 

    Jeanne Joly
    Associate
    May 11, 2017
    Posted on May 11, 2017 at 08:51

    ok, using CubeMX-4.21 under windows, we don't have this issue. I will have a look in depth on Linux to see if it is specific to Linux (and perhaps Mac as well).

    I will keep you inform.

    BR. Eric

    Sirma Siang
    ST Employee
    June 30, 2017
    Posted on June 30, 2017 at 12:20

    Hello All,

    I am pleased to inform you that this anoying issue will be fixed in verion 4.23.

    This release will be available in October.

    Kind regards

    Sirma