Hi,
I recently ran new code on the STEVAL-PROTEUS1 sensor kit. Before uploading the code, I was able to connect to the STBLE sensor app, but now I can't. I tried a full chip erase using the STM32 CUBE Programmer, and then I re-uploaded the software file (STSW-PROTEUS) through STM32 CUBE IDE. However, the code doesn’t seem to be working correctly because I still can’t connect to the app via Bluetooth. Additionally, after uploading the code, the green LED was on, but after cycling the power, the light no longer turns on.
I’ve checked the memory addresses through the STM32 CUBE Programmer and confirmed that the code was uploaded. I also placed the stm32wb5x_BLE_Stack_full_fw.bin file in the address specified in the release notes, as mentioned in the readme.txt. I noticed some discrepancies in the flash memory sections and their start and end addresses in the datasheet of the STEVAL-PROTEUS1 kit (see the attached image). The BLE stack section appears different from the address mentioned on the website. Additionally, when I only upload the BLE stack binary file, I noticed some data in the FUS section addresses, which has confused me. I would really appreciate your help with this.
Best Regards
Hello,
after loading stack BLE stack into STM32WB55, quite usual issue is, that user verifies stack version, which starts again FUS and does not switch back to stack.
Verification, if stack or FUS is running can be done in option bytes - SBRV is pointing on CPU2 boot address
Checking STSW-PROTEUS package is quite old, integrating old version of STM32WB_Copro_Wireless_Binaries. Up to date version of STM32WB_Copro_Wireless_Binaries has bit optimized size of binaries, so address my differ. You may also check video about FUS/stack update.
Best regards,
Lubos
