MX cube corrupts .ioc on save (Windows 11)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2025-03-17 10:08 AM
I am using the STM32CubeMX to edit pinout configurations for the STM32U595ZJYxQ. Process worked well for the past few days however on Friday the tool appeared to hang after saving the config. The first time this happened the tool closed on its own after several minutes. The next time this happened today, I restarted the laptop. Once the reboot completed, I tried opening the file again but the contents of the file appeared to have changed. The LTIM core assignments were gone as was a SPI chip select GPIO config.
The IOC was backed up by versions so I picked last friday's version and it opened without those issues. Comparing file versions between working and corrupted, I see a 3kbyte size difference (14K corrupted vs 17K working).
My experience was on a file that was saved on a corporate NAS behind a VPN. I have since copied that file locally and started only making local updates.
Has anyone else experienced thest types of issues? I am running STM32CubeMX v6.14.0 on windows 11.
- Labels:
-
Bug-report
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2025-03-17 3:11 PM
This sounds like a network/firewall issue rather than something STM32CubeMX has control over. Flaky I/O can definitely lead to unintended results such as a program hang.
