Cannot flash STM32WB55 dongle with wireless stack or perform mass erase.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-27 7:23 AM
Hi,
Every time I attempt to flash the BLE wireless stack to the chip or I try to perform a mass erase I receive the same error and the USB dongle disconnects.
FYI - I have successfully been able to upgrade the FUS version with no issue:
I attach the logs for both the Wireless stack fail and the chip mass erase fails.
Not sure how to export the options byte (incase they are useful information here) so some guidance on that would be appreciate also.
Thanks very much!
Solved! Go to Solution.
- Labels:
-
BLE
-
STM32WB series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-28 6:27 AM
Reading the log file, it is clear that you did not use the right load address as the CPU tried to erase protected sectors, starting from 0x080F4000, where the FUS is located.
So take a few more margin, I would say, 8 sectors less. This means loading the wireless stack at 0x080C7000 to avoid this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-27 9:17 AM
Hard to read the log when there is too much information.
Please use the lower verbosity level 1.
Regarding the option bytes, just do a screen shot of the secure ones. That should be enough.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-28 1:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-28 6:27 AM
Reading the log file, it is clear that you did not use the right load address as the CPU tried to erase protected sectors, starting from 0x080F4000, where the FUS is located.
So take a few more margin, I would say, 8 sectors less. This means loading the wireless stack at 0x080C7000 to avoid this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-28 7:45 AM
Thank you very much! This seems to have fixed my issue.
Does this solution mean that the address given in the documentation (release notes) is just wrong? This is what I was working off of:
Device info:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-28 7:54 AM
En effet c'est étrange. quelle est la version de WB FW package utilisez vous? V1.13.x ou v1.14.0?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2022-09-28 8:02 AM
Apologies, it seems I was reading the V1.14 notes but trying to flash the V1.13 binaries. Thanks very much for your help I think this is closed now :)
