cancel
Showing results for 
Search instead for 
Did you mean: 

NUCLEO-WB55RG board FW update

majidsurefow
Associate III

Hello, 

I have recently started getting familiarized with the P-NUCLEO-WB55 kit, and I have run to my first big mess up. I was attempting to perform a wireless stack FUS routine over the STLink interface, and I might have set a wrong start address for the FUS_fw.bin file (which I have updated to v 2.00). Hence, it seems that I can no longer do a firmware update over the stlink. 

 

The other main issue that I am also facing is that I cannot seem to get the board to boot up to DFU mode. I have tried the dongle, and it boots to DFU mode normally after toggling the switch. However, and correct me if I am wrong, If I follow the procedure outlined here: https://visualgdb.com/tools/STM32WBUpdater/connecting/ , I should be able to boot into DFU mode in the development board. Yet, it does not work.

 

If this is salvageable, I would greatly appreciate any help/support you can provide.

 

Thanks

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
STTwo-32
ST Employee

Hello All,

This behavior has been solved on the last update of the STM32CubeWB (V1.23.0) using the FUS V2.1.0.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

View solution in original post

14 REPLIES 14
RobK1
Senior

I found that in my P-NUCLEO-WB55 kit, the Boot select bits in the Option Bytes were not correctly set.

This works for me to boot up in DFU mode:

RobK1_0-1750331527301.png

 

You are a life-saver, thank you for that.

 

Now I can boot into DFU mode normally. 

majidsurefow
Associate III

Hello, 

The DFU mode issue is fixed now, but I cannot seem to be able of reflashing the binaries of the wireless stack. Here is what I tried doing:

 

1- I did a firmware delete

2- I am now trying to reflash each part of the wireless correctly starting with the FUS binary, but I am not able of flashing anything, here is an example log I get:

15:32:15 : UR connection mode is defined with the HWrst reset mode
15:32:15 : USB speed : Full Speed (12MBit/s)
15:32:15 : Manuf. ID : STMicroelectronics
15:32:15 : Product ID : DFU in FS Mode
15:32:15 : SN : 207431743831
15:32:15 : DFU protocol: 1.1
15:32:15 : Board : --
15:32:15 : Device ID : 0x0495
15:32:15 : UPLOADING OPTION BYTES DATA ...
15:32:15 : Bank : 0x00
15:32:15 : Address : 0x1fff8000
15:32:15 : Size : 128 Bytes
15:32:15 : UPLOADING ...
15:32:15 : Size : 4 Bytes
15:32:15 : Address : 0x1FFF8070
15:32:15 : Read progress:
15:32:15 : Data read successfully
15:32:15 : Time elapsed during the read operation is: 00:00:00.002
15:32:15 : UPLOADING ...
15:32:15 : Size : 1024 Bytes
15:32:15 : Address : 0x8000000
15:32:15 : Read progress:
15:32:15 : Data read successfully
15:32:15 : Time elapsed during the read operation is: 00:00:00.004
15:32:19 : FUS state is FUS_IDLE
15:32:19 : FUS status is FUS_NO_ERROR
15:32:21 : Deleting firmware ...
15:32:22 : Firmware delete finished
15:32:22 : Firmware delete execution finished
15:32:32 : FUS state is FUS_ERROR
15:32:32 : FUS status is FUS_IMAGE_NOT_FOUND
15:32:34 : FUS state is FUS_IDLE
15:32:34 : FUS status is FUS_NO_ERROR
15:32:37 : Old Firmware delete ...
15:32:37 : Deleting firmware ...
15:32:37 : Firmware delete finished
15:32:37 : FUS state is FUS_ERROR
15:32:37 : FUS status is FUS_IMAGE_NOT_FOUND
15:32:40 : FUS state is FUS_IDLE
15:32:40 : FUS status is FUS_NO_ERROR
15:32:42 : Download Stack/FUS image at address 0x80EE000 ...
15:32:42 : Opening and parsing file: stm32wb5x_FUS_fw.bin
15:32:42 : Memory Programming ...
15:32:42 : File : stm32wb5x_FUS_fw.bin
15:32:42 : Size : 23.89 KB
15:32:42 : Address : 0x080EE000
15:32:42 : Erasing memory corresponding to sector 0:
15:32:42 : Erasing internal memory sectors [238 243]
15:32:43 : Download in Progress:
15:32:43 : failed to download Sector[0]
15:32:43 : failed to download the File
15:32:43 : Failed to download image!
15:32:43 : Connection to device 0x495 is lost
15:32:43 : Disconnected from device.

 

Hello @majidsurefow 

Could you please state the exact steps (with screenshots if possible) on how you have done this update. and a final screenshot similar to this one: 

STTwo32_0-1750334576264.png

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Hello, 

 

Thanks for your reply.

 

I am currently using Firmware 2.0.3

Here is a screenshot of what I get if I am using the DFU-USB Interface to check the FUS status:

majidsurefow_1-1750335979729.png

I am currently using FUS 2.0.0.3 as I have installed it blindly while trying to upgrade my BLE/ZigBee binary. The STM32WB_Copro_Wireless_Binaries directory I am using is the one that results from cloning the https://github.com/STMicroelectronics/STM32CubeWB/tree/master  repo. 

Here is a screenshot of what I have after deleting the firmware:

 

majidsurefow_3-1750336196074.png

I am setting the starting Address to 0x080EE000 as stated in the release notes, and attempting to flash the FUS binary:

 

majidsurefow_4-1750336634313.png

 

Next, I tried flashing a random file which was the stm32wb5x_BLE_HCILayer_fw.bin:

majidsurefow_6-1750337537643.png

This is the only one that flashes correctly. If I try to flash something else, lets say stm32wb5x_BLE_Zigbee_FFD_static_fw.bin, here is what I get:

majidsurefow_9-1750338832553.png

The device disconnects mid-flash, and I have reconnect it using the GUI option.

 

 

 

 

 

 

 

Hello @majidsurefow 

Have you clicked on the First install: No stack delete.

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.

Hello, 

 

It seems that I can flash FUS_v2_only binaries, and any other binary does not flash correctly, and flashing exits midway, and I need 

 

majidsurefow_0-1750339781286.png

 

I have flashed stm32wb5x_BLE_Stack_full_fw.bin, and it works well, but if I try any of the zigbee stacks (which do not have FUS_v2_only), it does not work.

majidsurefow_1-1750341121976.png

 

 

hello, 

 

yes I have tried to install with and without it.

 

Thanks

Hello @majidsurefow 

I've been able to reproduce this behavior and i've escalated this to the concerned team for correction (under internal ticket number 212613).

Best Regards.

STTwo-32

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.