Radio Peripheral Documentation

Radio IP is usually tightly held, you'd need to be a customer of merit, have a history of radio stack work and have NDA's, etc in place.

Discuss with your local sales office.

​Clive is right.

On top of that, we do not want to open the M0+ core to customers in order to keep control on the RF stack and all the high real time constraints associated with it.

Opening this space would require much more support from us and we dont want to go that way.

​No there is no plan, at least not that I know.

We had such discussion last year as other customers were asking for the same thing.

In the end the anwser was "not for now and not even for the mid-term".

Is there a way you could provide the radio IP as a static library that could be linked against for user-built M0 firmwares?

This is not possible as the complete upgrade process is managed by the CPU2 core and the STM32WB chips are sold with a secure environment already loaded on it.

So no way for a customer to bypass this mechanism handled by the CPU2 core if he wants to load its own RF FW.

Just a suggestion, but certain other company doesn't open their radio core for regular customers too, but they provide API for sending and receiving packets in generic format to support custom stacks. Maybe you can implement this functionality too.

You "may" use your own RF stack but you won't benefit from the M0+ core as a RF coprocessor as it only executes code located in the secure part of the flash memory and this secure part is not accessible to any user code.

Your own RF stack would only run on the M4 core, which for sure, would limit the performance and reactivity of your device. The flexible architecture of the STM32WB would be of no interest for you as you would use one core only.

Hi, we're looking for the same. We have the solution ready on Nordic platform, but from historical pov we used STM asm MCUs for our product. We we're curious if we can use STM for our proprietary RF solution. So is there any descriprion of RF module - even if you dont give us access to the M0+?

WOW! That is so disappointing. On all of the device summary and advertisement brochures/flyers you loudly say "And Proprietary 2.4GHz" in addition to the BLE, Thread and 802.15.4. You should remove that information to not mislead users, or better to live up to those promises. What real commercial use does a compulsory pre-built black-box solution have if you can not put your own stacks on it?! It is not an Arduino to have everything obfuscated and pushed into APIs, it is a tool for real applications. What a disappointment...

​It is anyhow still possible to run its own 2.5GHz protocol on the M4 core using the LLD BLE or MAC 802.15.4 layer running on the M0+ core. This would be a partial but effective portability.