BUG: MX-cube / Cube-IDE goes into an infinite loop and corrupts the .ioc file

[matt-crc]

When I try and enable UART5 in the  .n657_dk2.ioc file,  the development system seems to go into an infinite loop with the mouse cursor spinning endlessly.

Bug1: To replicate,

1- open the n657_dk2.ioc file

2- goto the connectivity section

3- enable UART5 in FSBL

4- change mode to Asynchronous

5- set Hardware Flow control to RTS/CTS.

system hangs....

Bug 2: if you try and save the file, it corrupts the file and you cannot edit the .ioc file anymore.

.ioc file attached

IMPORTANT!!! I need a fast work around so I can go to layout this week....

[Ghofrane GSOURI]

Hello @matt-crc 

After following your scenario to replicate the issue, I found that the problem described above and in the other thread is the same, but appears under two different scenarios. Both scenarios have been escalated to the development team for further investigation (internal ticket number 220572 ).

CubeMX hangs , and if you then try to save the .ioc file, it becomes corrupted because CubeMX is no longer functioning correctly. Therefore, I believe your scenario is invalid, and the main issue is the underlying problem that caused CubeMX to crash in the first place

THX

Ghofrane

[matt-crc]

Hello @Ghofrane GSOURI 

Regarding Bug2:  you should consider this a real serious bug.  Corrupting user files is a REAL BIG issue, regardless whether the CubeMX task has stopped functioning.  You really need to implement some sort of safety mechanism instead of wiping out user files.  Please escalate.   

Note: it takes a lot of time to re-enter all the data.... ask me how I know.

Can you also acknowledge BUG 3 where the clock pins cannot be allocated properly and creates a bunch of errors when attempting to do this.  This was brought up in another post (which you were mentioned/tagged in).

thanks

Matt

[Ghofrane GSOURI]

Hello @matt-crc 

Thank you for your feedback. I agree that corrupting user files is a serious issue. Even if we add safety mechanisms, they may not always work if CubeMX crashes or hangs unexpectedly. In such cases, there is still a risk that user files could be affected.