2019-02-22 04:00 AM
We are looking at sending around 1Mb/s of data with a latency of under 1ms.
2019-02-22 07:28 AM
Hello @AMcGh ,
You should contact your FAE for such request.
Best Regards,
Imen.
2019-02-22 08:14 AM
The wireless group has had poor support/communication in the past, it would help if sales, marketing and support could show up here to promote the STM32W brands if they are being resurrected.
Historically ST has been very cloak-and-dagger when it comes to wireless products and opening things so they might actually be adopted. I will point to Semtech as a counterpoint where the parts are fully documented and the stack is completely open.
Unless the forum is used actively to support products in a more direct way you're going miss the prime opportunities to get the parts integrated into new designs, especially the smaller and niche ones.
2019-02-22 08:27 AM
Obviously not an STM part but why not just use an ESP8266 - that can support most 2.4GHz protocols and comes as a module if you want it.
2019-02-26 09:29 AM
For STM32WB55, the M0+ coprocessor must be used with the wireless stack provided by ST inside the following package: https://www.st.com/content/st_com/en/products/embedded-software/mcu-mpu-embedded-software/stm32-embedded-software/stm32cube-mcu-mpu-packages/stm32cubewb.html
The wireless stacks can be found under the directory Projects/STM32WB_Copro_Wireless_Binaries.
The complete procedure to use them is described inside the same directory.
Concerning your initial request, any proprietary protocol must be implemented on the M4 side. I suggest you refer to the following 2 examples for your specific case:
Those 2 applications must be used with the following wireless stack: