It cannot be cost effective to embark on a project where the CPU has a 2000 page RM, without having working code examples.
Some people here say so but they are super clever and already know it all.
The proper way would be for ST to spend a totally miniscule % of their $14BN revenue, say $80k, on a "social media specialist" who is also a really good hardware and software dev.
The truth is that they are scared. I have seen this fear all the way back to early 1990s, with Compu$erve forums. These companies never learnt how to manage social media.
A part of my day job is a forum admin and I see the same there now. Companies which dominate that industry, and companies which could and want to compete with them, are too scared. They have (basically) told me so.
And the ones that do participate mess it up by employing stupid people who offer input which is banal, over-simplified, arrogant, downright rude... And then they complain that it didn't work for them!
As a data point, take my project.
32F417
FreeRTOS
LWIP
TLS
FatFS
ETH
USB (MSC & CDC)
A ton of stuff which I mostly wrote e.g. boot loader, loads of essential functionality. Factory test code...
A guy who is more clever than I am spent about 3 years worth of Monday afternoons on all but the last one. He used mostly Cube MX to generate code snippets and then googled all over the place to find patches to make it all work. This is despite e.g. LWIP was an ST port of the generic open source LWIP! He would not post questions on forums, which probably doubled his time spent.
So he spent ~100 full time days (I have allowed a bit for half a day a week being pretty unproductive) making stuff work which should have worked.
Why was he part-time? Because I could not afford someone full time. A very small business, etc. Also it was to some extent a technology demo project, to see what could be done, and the final form defined afterwards.
That amount of work is totally unacceptable.
I spent about 2 years, about a 50% duty cycle but actually many hours and days working at home, doing the last item. Learning C, learning Cube (of which I know about 1%). That's would also be unacceptable in a normal job but it's because it is my company, I am not young, not that clever, and I am extremely careful in writing and testing code (did 30 years of assembler, and hardware, on simpler chips).
There is no easy way. These chips are immensely complex and the above "open source" software varies from great (e.g. FatFS) to not good (LWIP or TLS). And all of it is totally unsupported - partly because it is old (LWIP goes back > 15 years) and the coders sorted out girlfriends years ago and moved on, and partly because the whole open source scene is like that. In some cases people make money integrating OS software but not in this case. I have not seen a "Magento-like" ecosystem in embedded.
As a lone operator, some things you just can't do. A product like this will take a few years to do, if you start with no experience. In the Z80 days, it would be a few months. Today it is 5x longer even for basic code, and much longer if integrating modules (like above) which nobody supports, almost nobody understands, almost nobody can test if you did it right...