I've worked with a bunch of different microcontrollers from a lot of makers, but I feel like ST's IDE has to be the most baffling and frustrating to use given what it is.
For starters, it's Eclipse at its core. Which, while maybe not a bad thing per se (depending on who you ask), the thing that makes it bad is that it is a forked, special version of Eclipse which means that anything made for normal Eclipse will both not work and will also bork your installation completely. The next is that there is no dark mode unless you go out of your way to try to create your own (which I did). Otherwise it's just blindingly bright.
just dont use their IDE. their STM32CubeMX implementation can be pretty broken for other platforms (thinking of CMSIS-Toolbox & KEIL where you need an older version for GPDSC support, and in the case of CMSIS-Toolbox, which ive used more than KEIL because honestly that feels super fustrating to use, while CMSIS toolbox has extensions and can be somewhat easy to script, it tries to generate all the code files in the RTE folder including main. whats more fustrating is that some things are actually seperated (thinking of msp init/deinit functions))
what i tend to do is manually move around the generated code to my project and use it however i want which i guess removes some of the point but CubeMX sucks so much ass and i dont want to use their ide. i guess that can add a lot of time delay when reconfiguring stuff but there doesnt feel a godo way around st's bs 😭😭
also its really fun to see stuff on cohost like this, i try and check the ee tags every so often but the tags arent super active !! i should post some ee stuff when im back on my nonsense.
