STM32WB5X BLE packets sizes

Ofer · ‎2023-04-08

Hi

I would like to use STM32WB5MMG-DK.

1) I tried to program 1.15 software packages for stack-ble + FUS + SAFEBOOT.

The stack ble file size is 149KB, according to the release note it suppose to be programmed at address 0x080C5000 (or 0x080CE000).

The FUS is suppose to be programmed at 0x080EC000 and the safeboot at 0x080F0000,

but the stack-ble is so big (149KB) so its end is on 0x080F3000.

How can I have all of them ?

2) During my tries I erased all the sections between 0x080C5000-0x080F3000.

Now, any combination of stack/FUS I tried, I don't have ADVERTISE (the code does not get to ADV_Request - but there are RX_IPCC interrupts)

Is there something important that being erased ?

Thanks

Remy ISSALYS · ‎2023-04-25

Hello,

You can look this wiki page which talk about the FUS and you can refer to AN5185. According to this documentation, the FUS start address is 0x080F4000 and the memory between 0x080F4000 and 0x080FFFFF is reserved for the FUS. The wireless stack is under the FUS, in your case if you are using the BLE Full stack, it will be located between the 0x080CE000 and 0x080F4000. The safeboot is an independent part of the FUS that manages specifically one case: option bytes corruption. It can be installed on STM32WB devices where FUS V1.1.0 or FUS V1.1.1 is present. No need to use it on parts where FUS V1.2.0 is present (as these parts already have the latest Safeboot version).

You have erase the wireless stack, that's why your device doesn't advertise. You can refer to this wiki page which explain how to setup the board.

Best Regards

View solution in original post

Remy ISSALYS · ‎2023-04-25

Hello,

You can look this wiki page which talk about the FUS and you can refer to AN5185. According to this documentation, the FUS start address is 0x080F4000 and the memory between 0x080F4000 and 0x080FFFFF is reserved for the FUS. The wireless stack is under the FUS, in your case if you are using the BLE Full stack, it will be located between the 0x080CE000 and 0x080F4000. The safeboot is an independent part of the FUS that manages specifically one case: option bytes corruption. It can be installed on STM32WB devices where FUS V1.1.0 or FUS V1.1.1 is present. No need to use it on parts where FUS V1.2.0 is present (as these parts already have the latest Safeboot version).

You have erase the wireless stack, that's why your device doesn't advertise. You can refer to this wiki page which explain how to setup the board.

Best Regards

Ofer · ‎2023-04-25

Thanks dear Remi

Now, everything is clear.

The addresses are different from the addresses in the C:\Users\me\STM32Cube\Repository\STM32Cube_FW_WB_V1.15.0\Projects\STM32WB_Copro_Wireless_Binaries\STM32WB5x\Release_Notes.html link page.

Please correct the page so other people will not have main issue.

Remy ISSALYS · ‎2023-04-25

Hello,

Which address is different?

Best Regards

Ofer · ‎2023-04-25

The address for the FUS:

In the C:\Users\me\STM32Cube\Repository\STM32Cube_FW_WB_V1.15.0\Projects\STM32WB_Copro_Wireless_Binaries\STM32WB5x\Release_Notes.html link page the address is: 0x080EC000.

In the link you sent (which seems more logical) it is 0x080F4000.

Remy ISSALYS · ‎2023-04-26

Hello,

The address 0x080EC000 in the release note is the download address and the address 0x080F4000 is the address where the FUS is running.

Best Regards