Hello,Since STM32CubeIDE V1.11.0, there is an issue in linker file template, see STM32WB55RGVX_FLASH.ld file. In this file, there is an extra dot for MB_MEM2 section initialization, see this part: .MB_MEM2 :
_sMB_MEM2 = . ;
*(.MB_MEM2) ; ...
The new STM32WBA series comes to complete the STM32 Wireless MCUs portfolio.
The STM32WBA series is brings designers the performance, efficiency, and security required for Bluetooth® Low Energy 5.3-enabled applications.
Certified for Bluetooth® Low...
Hello, A corner case has been recently identified with FUS v1.2.0. It is not possible to upgrade back-to-back a wireless firmware with a new version that is exactly one sector bigger than the installed version. This limitation applies only when the r...
Can you try with the latest version of STM32CubeProgrammer tool (v2.15.0) and follow these steps?
- Start FUS
- Read FUS to check the version
- If a stack version is displayed, perform the firmware upgrade without first install opt...
According to your second screenshot, you tried to flash the wireless stack at 0x0805A000 instead of 0x08051000 as mentioned in the release note. Can you retry with the right address?
To start with a clean setup, you can perform a full chip erase and firmware delete and then flash again the FUS binary if needed and the Zigbee stack. You can refer to this wiki page for more detail on how to proceed.
According to the release note of STM32CubeWB package v1.18.0, see below the install address for STM32WB5xxG:
stm32wb5x_FUS_fw.bin : 0x080EC000stm32wb5x_Zigbee_FFD_fw.bin : 0x080A0000
Indeed, the adv_request function implementation is a bit different in BLE Custom template than in BLE HeartRate. You can implement this mechanism in BLE Custom template by adding a timer and a task to manage this different advertising interval...