2024-06-05 07:50 AM
Hello
The Nucleo/Dongle pair did not do the demo.
So downloaded and updated them with P2Pserver and Client hex files.
Still didn't work.
Am now trying to upgrade the FUS in the dongle from .53 to current using stm32wb5x_FUS_fw_for_fus_0_5_3.bin, using 0x080EC000 as listed in Release notes, and it fails.
10:39:11 : Erasing memory corresponding to segment 0:
10:39:11 : Operation exceeds memory limits
10:39:11 : failed to erase memory
Dongle has the STM32WB55CGU6 MCU.
Looks like the start address is wrong, but what should it be and where do I find this info.
Thanks
Giri
Solved! Go to Solution.
2024-06-06 07:22 AM - edited 2024-06-06 07:27 AM
Many thanks for the data.
Look like your device is still with FUS v0.5.3
I don't see any corruption, thus from my perspective the device is not damaged.
However, I just noticed on your screenshot that the FUS file stm32wb5x_FUS_fw_for_fus_0_5_3.bin you are trying to download doesn't have the correct size.
I read Size=276KB, which is too big.
Extract from your screenshot:
Correct size of the file is around 24KB.
Below the test I have just done on my dongle:
Please, as pointed by my colleague, can you precise exactly where you are getting this stm32wb5x_FUS_fw_for_fus_0_5_3.bin file?
From which version of the STM32CubeWB firmware package?
In addition, which version of STM32CubeProgrammer tool are you using?
Best Regards,
Alan Porte
ST MCU Support Team
2024-06-05 10:22 AM
Hello @GRama.2
Could you please try using the FUS file from the STM32CubeWB V1.19.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.
2024-06-05 10:32 AM
Thanks for your response.
But the FUS file is from that directory. The FUS versions ae listed as Release v1.11.1
3 years ago | ||
3 years ago |
2024-06-06 06:39 AM
Dear @GRama.2,
Many thanks for the info.
Please, can you share Option Bytes values of your Nucleo dongle?
Specially SFSA, FSD, C2OPT, SBRV (in "Security Configuration Option bytes") and ESE.
It will give us an idea of how the device is configured.
Best Regards,
Alan Porte
ST MCU Support Team
2024-06-06 07:00 AM
Alan
ESE - checked
SFSA Value=0xF6, Address = 0x080F6000
FSD - unchecked
C2OPT - Checked
DDS - Checked
NBRSD Unchecked
SNBRSA: Value=0x19, Addr = 0x2003C000
BRSD - Checked
SBRSA - Value=0x0, Addr = 0x20030000
SBRV Value=0x3D800, Addr = 0x003D80
Thank you.
Giri
2024-06-06 07:22 AM - edited 2024-06-06 07:27 AM
Many thanks for the data.
Look like your device is still with FUS v0.5.3
I don't see any corruption, thus from my perspective the device is not damaged.
However, I just noticed on your screenshot that the FUS file stm32wb5x_FUS_fw_for_fus_0_5_3.bin you are trying to download doesn't have the correct size.
I read Size=276KB, which is too big.
Extract from your screenshot:
Correct size of the file is around 24KB.
Below the test I have just done on my dongle:
Please, as pointed by my colleague, can you precise exactly where you are getting this stm32wb5x_FUS_fw_for_fus_0_5_3.bin file?
From which version of the STM32CubeWB firmware package?
In addition, which version of STM32CubeProgrammer tool are you using?
Best Regards,
Alan Porte
ST MCU Support Team
2024-06-06 07:35 AM
path for my download is
Alan - Thanks for bringing up the invalid size.
I was right-clicking and save, versus using the GitHub download.
This caused the bad download.
With the new download I was able to update the dongle.
Thank you much for staying with me on this.
Giri
2024-06-06 07:48 AM
Many thanks for the feedback.
Glad to read that the FUS update went well.
Hope it will solve the problem with the P2PServer/Client demo.
Best Regards,
Alan Porte
ST MCU Support Team