STM32CubeIDE Version: 1.16.1 Build: 22882_20240916_0822 (UTC) less reliable than ever before

[etheory]

Hi there!

Since updating to:

STM32CubeIDE Version: 1.16.1 Build: 22882_20240916_0822 (UTC) I've noticed that changes to the .ioc configuration file performed through the Device Configuration Tool do not reliably propagate to code using the "Do you want generate Code?" (which should be "Do you want to generate Code?"....) option do not generate code that is correct, instead it generates code from a previous configuration.

This particular aspect of STM32CubeIDE seems to get worse in every iteration.

Also, when you use the configuration tool twice in a row, and do a save-generate cycle, it stops working and the "save" option disappears, and you have to close and re-open it. This is time consuming and very frustrating.

This issue is new, and did not occur previously.

It makes STM32CubeIDE even more unreliable than it already was, and someone should fix it with priority.

Also the recent change to require the user to define "USER_VECT_TAB_ADDRESS" in the "C/C++ Build/Settings" Property for a project in order to stop code from crashing due to not defining the vector table, which again, was never previously required, is pretty bad, and will prevent new users from using STM32CubeIDE, since it's unbelievably far from obvious.

Is someone working to resolve these new issues?

Thanks. 

[etheory]

---

@Ghofrane GSOURI wrote:

Hello @etheory 

This behavior is weird.

After multiple tries, I couldn't reproduce the issue from my side.

So let's try to uninstall STM32CubeIDE and reinstall it again. This could help solve the issue.

I will be waiting for your feedback.

THX

Ghofrane

---

Sorry @Ghofrane GSOURI, but as a software engineer by trade, if someone told me this when I logged a bug report, I'd be pretty frustrated. That's the equivalent of "it works on my machine" or "turn it off and back on again".

I have zero faith that re-installing will fix the issue, or if it does, that it won't simply come back again at a later date.

Have you actually logged a bug with your team to actually try and investigate it? Rather than not being able to reproduce it personally then suggesting a re-install as a fix (which, in my experience, almost never fixes an issue?)

Thanks.

[Karl Yamashita]

You can't fix so call bug if it's not reproducible. I think it's been 3+ weeks and I've yet to have 1.16.1 produce bad code and this is on 2 Windows 10 machines. If there were issues that you're reporting, then they'll be more than 1 post  complaining about code generation at least for this version. 

Maybe you have some other software running in the background that is interfering with code generation? Where is your workspace located? Is the project in Dropbox/Drive folder? Try another computer. 

[etheory]

@Karl Yamashita the vast majority of people don't post their issues, at all, so I'm not sure a lack of posts to this specific forum is an indication that there is no issue, as doesn't your individual experience.

I'll try re-installing. But prior to 1.16.1 there were no issues, afterwards, the entire codegen process is completely unreliable. Nothing on my setup has changed aside from the STM32CubeIDE version.

But I will report back after the install. Thanks.

---

[etheory · Accepted solution]

So far a fresh re-install seems to have fixed the issue.

I will report back here if any of the issues re-surface.

Thanks.