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.
