MX cube corrupts .ioc on save (Windows 11)

[edwal]

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.

[TDK]

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.

[edwal]

Possible, but I have not had these types of issues with other apps, editors and tools that are used in a similar manner on the same NAS and using the same VPN. I'm not sure I buy this being the fault of the NAS/VPN.

[Pavel A.]

>  corporate NAS behind a VPN

Some corporate "security" or "DLP" junk-ware is installed? These pests often cause problems.

 

[edwal]

Similar to above reply, if I were subjected to disruptions like that due to corporate monitoring apps, I should see it on other apps/tools and I am not.

[Andrew Neil]

---

@edwal wrote:

Has anyone else experienced thest types of issues?.

---

Yes, I have seen issues where remote stuff causes problems.

[Pavel A.]

So this hints to problem in java runtime libraries? Probable though not too much.

 

[Christian N]

This post has been escalated to the ST Online Support Team for additional assistance. We'll contact you directly.