2022-04-28 09:49 AM
In examples I got familiar with RF low level access is controlled by some exact coprocessor firmware. Existing coprocessor binaries provide some higher level of abstraction that seems to not include forcing signal with exact characteristics. Do I missing something or is there any other approach to start continuous signal generation with specified power and frequency?
Solved! Go to Solution.
2022-05-05 03:01 AM
Hello,
In order to perform RF test, you can use STM32CubeMonitorRF tool available here:
https://www.st.com/en/development-tools/stm32cubemonrf.html
Best Regards
2022-05-05 03:01 AM
Hello,
In order to perform RF test, you can use STM32CubeMonitorRF tool available here:
https://www.st.com/en/development-tools/stm32cubemonrf.html
Best Regards
2022-05-05 03:49 AM
>Could you advice me how can this be achieved using some exist coprocessor binary or any other way?
As far as i know ST doesnt want you to thinker with the M0+ core, thats why they offer 0 doumentation and only supply already compiled binarie files.
2022-05-06 07:30 AM
Thank you, at first glance I missed that STM32CubeMonitorRF provides possibility to do the low level tests as we need but actually it is possible with Phy_802_15_4_Cli FW for CM4 + stm32wb5x_Phy_802_15_4_fw.bin for CM0 interacting with STM32CubeMonitorRF
2022-05-11 07:49 AM
Hello,
In order to do radio test for BLE, using Direct Test Mode (DTM), you should use stm32wb5x_BLE_HCILayer_fw.bin coprocessor binary available here:
Best Regards