PCB in DFU mode not connecting to Cube Programmer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2020-06-24 05:08 AM
Hello,
We have a made two PCBs with STM32WB55CGU6 Microcontroller in which the sole programming mode is by flashing the program into the Microcontroller by DFU Mode via STM32Cube Programmer.
For the first PCB, we erased all the selected sectors in the PCB and after that, we were unable to recognize the USB device in DFU mode anymore and now we have unknown USB devce with code 43 where it is unable to detect the current device. The error is as shown below.
For the second PCB, we wanted to test out the Bluetooth module where we found that the firmware for the Bluetooth is not up to date and thus, we flahsed the stm32wb5x_FUS_ fw.bin and stm32wb5x_BLE_Stack_full_fw.bin found in the STM file in Github https://github.com/STMicroelectronics/STM32CubeWB/tree/master/Projects/STM32WB_Copro_Wireless_Binaries/STM32WB5x. We then flashed our program into the Microcontroller at the address 0x80000 then after a while we were unable to detect the USB and obtain the first error above. Performing a simple reset on this PCB will make it sometimes work but now we are completely unable to communicate with it.
Do you have any suggestions on how to sole this issue?
Thank you,
Bogdan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2020-08-06 01:57 AM
First a few recommendations
Be sure to set the nSWboot option byte to 1 and have BOOT1 option byte set to 1 in a HW manner.
Then please use the RF stack available in the official deliveries on st.com. The last version is now v1.8.
stm32wb5x_BLE_Stack_full_fw.bin should be flashed at address 0x080CB000.
Do you know the FUS version you flashed on your board?
Can you provide a log of your option bytes.