> "open source" projects out there that are either not really open, are very buggy or just not fitting our applications in controlling essentially all kinds
They are not really open, very buggy, or not very flexible, exactly because
> This is a section of a larger project and i just have to get things to work, not do real software engineering.
Doing things flexible and good requires lots of engineering, read: time, read: money. The motivation for open sourcing is just that much, even if it's not just altruism and self-promotion, but is based on some business model (which in turn is inevitably limited by the potential audience, etc.etc.).
Clicking in CubeMX (or, for that matter, ST has also some clicky motor control framework, I don't know much about that) yields quick results as long as your application fits whatever those clickies author's deemed typical, as their scope/time/money is inevitably limited, too; so the clickies inevitably cover only a miniscule fraction of the almost infinite ways the hardware can be used. If this "fit" happens, you are a happy camper, end of story. But whatever does not fit, you have to go back, relearn what you didn't want to learn at the first place, and then either bend the clicked result (which may or may not lead to desired result), or try to unlearn what you've experienced with the clicky and walk all the path you've deemed hard at the beginning (which is psychologically next to impossible).
And now you've been warned.
JW