:wrench: STM32 Samples: A Developer’s Time Sink
I’m not a novice in software at all — and this isn’t just about one sample. It’s about STM’s consistent failure to respect developer time across their software stack especially modules of other vendors like MXCHIP EMW3080.
Take this gem from the B-U585I-IOT2A sample:
How to use it?
WARNING: Before opening the project with any toolchain be sure your folder installation path is not too in-depth since the toolchain may report errors after building.
Open your preferred toolchain
Build all files and load your image into target memory
That’s the entire instruction. No toolchain version. No dependency list. No build script. No error map. Just “don’t put it too deep” and “open your preferred toolchain.”
STM is not a software company — and it this proves it. No UMLs. No sequence diagrams. Even no consistent pin configs. No architectural overview of how module like the MXCHIP 3080 interact with U585 - wake, notify, etc. Just megabytes of samples and a scavenger hunt to make them work.
STM does not care how many weeks developers waste trying to compile and run their demos. This isn’t onboarding — it’s obstruction. What a shame
