2025-12-08 7:16 AM - last edited on 2025-12-08 7:36 AM by Andrew Neil
Why, oh why have you separated IDE and MX such that .ioc files can no longer be opened in IDE?
I cannot imagine any benefits and it makes the IDE significantly worse, such that I've felt compelled to revert to version 1.19.0 ( go to Help -> About STM32CubeIDE -> Installation Details -> Installation History -> select version -> Revert)
I couldn't find any other means of feeding back my strong dislike of this change other than a post like this. I hope version 2.1.0 comes out soon and re-integrates MX and IDE!
2025-12-12 1:37 AM
> These are all reasons against any IDE.
Yes, there are.
My company extensively uses CI now, and IDEs are only getting in the way of automated builds on remote servers. Especially if you want to support several architectures and thus several toolchains / IDEs.
We are using make files instead, which are easier to automate and deploy.
2025-12-12 12:54 PM - edited 2025-12-13 12:47 PM
We use Eclipse CDT as IDE and "headless" build tool for CI, for 20 years. Then we did this with Atollic, then with CubeIDE. As machines become faster, so does Eclipse :) But fashion is fashion. New generation obviously cannot like old stuff.
P.S. As for requests to run CubeMX code generation headless - I don't know. For long time I believed it is abuse of CubeMX and wrong idea generally. But now one could wish to use AI assistants with CubeMX as a "skill", in a fast try/test/modify loop... Hmm. From this POV decoupling CubeMX from the IDE looks even better :)
2025-12-23 8:11 AM
OK to sum things up: ST wants to cut costs. End of story.
2025-12-23 2:28 PM
Nothing to do with costs...