v2.0.0 New tutorials

I just downloaded the Cube IDE (v2.0) and none of the tutorials will play in it, none of the tutorials online match this IDE and I do not have the MX tool because ST said it was included in the Cube IDE. I'm ready to delete all of this mess or can anyone point me to current (as of today, 2/2026) methods to start from scratch. 

 

BTW, yes, I have seen how to import 'older' projects, I've read several other posts, but if ST is serious then the tools ought to work properly or I'd have to consider them (ST and their tools) to uncared-for; i.e. is ST disinterested in selling us some MCUs even if we can't get started with THEIR tools. Either the tools should work and the site's info should be correct or we will have no choice but to look elsewhere. There are plenty of MCUs around these days.

[mƎALLEm]

Hello @Legacy member and welcome to the ST community,

---

@Legacy member wrote:

can anyone point me to current (as of today, 2/2026) methods to start from scratch. 

---

Please read this article STM32CubeIDE 2.0.0 workflow tutorial

I did see that  article at https://community.st.com/t5/stm32-mcus/stm32cubeide-2-0-0-workflow-tutorial/ta-p/864831 by Laurids Peterson . I also watched how ST destroyed the Cube IDE (STWorld) at https://www.youtube.com/watch?v=CfXH1DoZpRk and various Reddit posts to a similar effect. It looks very much like ST has a major problem with the right hand not knowing what the left hand is doing. I have previously developed with Eclipse on other programs, and yes, it's not perfect; but, it's still not as bad as other IDEs. In light of my position here, having put my head on the line for ST (versus its competitors) and now that I've learned a tad more (I re-read where ST said one thing in one website

"Integrated STM32 configurator

STM32CubeIDE embeds the STM32CubeMX capabilities. It allows generating the HW IP initialization code through graphical wizards, keeping the ST source application and driver code updated and generating the STM32CubeIDE project description."​

and a different thing elsewhere. I'm not willing to waste more time flogging a dead horse. We have 158 software programmers/engineers here and I supervise 18 of them and I am not willing to put mine or their careers on the line to use tools for MCU-based systems, no matter how good or bad they may be, when the manufacturer (ST in this case) has so many errors in what it presents to the people who might become customers. I have already loaded and deleted ST tools several times due to inadequate up-front info. I've had to purge junk left over after running the ST uninstaller. I have already spent too many hours trying to get these new ST developer tools to work as advertised but enough is enough. I'm not going to waste any more time on what seems to be inoperative or non-trivial or overly-complicated tools that our people will take an inordinate length of time to become used to.

 

ST should get their act together and MAYBE we will look at ST again in a few years.

 

So, bye.

[Pavel A.]

In your situation, the best is to use the latest version in 1.x  and abstain from updating to 2.x.

To ST devs: when CubeIDE 1.9.x checks for online updates, please check updates within the 1.x branch first.

Do not offer update to 2.x without a prominent warning.

 

I am not willing to use an older version of a development tool as a workaround. ST put out and promotes the STCubeIDE as the thing to do. It is not an alpha or beta or RC version. It is THE main tool and as such it should at least work, even with possible corner-case errors. ST should be ashamed to put out such a bad tool.

 

As I was saying before: thanks but no thanks.

 

Bye.