cancel
Showing results for 
Search instead for 
Did you mean: 

[BUG] STM32CubeProgrammer USB connection to STM32 BOOTLOADER device fails

SBone.3
Associate II

Hi,

we're having some issues while trying to connect a STM32F030C6 to the Stm32CubeProgrammer via USB, through the embedded STM32 Bootloader.

Using the same working sample of one of our devices, we perform several connection tests on different Windows 10 PCs, all set up with the following configuration:

  • STM32CubeProgrammer V. 2.10
  • USB plugged directly in the laptop port
  • STM32 drivers properly installed

All the PCs were able to properly detect the device in bootloader mode, showing "STM32 BOOTLOADER" in "Device Manager" and some of them were able to properly connect to the device, allowing us to perform DFU operations.

However, on some PCs, the following warning appeared, and no matter what we tried (flag set on "read unprotected", power cycles..etc), we weren't able to connect to the device:

0693W00000NsyWRQAZ.png 

Strange thing is, on those problematic PCs, if, instead of using the embedded laptop USB port, we connected the device through an external USB HUB, we were able to connect properly.

This issue is causing us some troubles because some of our customers are stuck and cannot perform the FW update of our devices on the field, and tell them "try to use an USB HUB" is a not viable option.

The issue is sistematic and not related to a specific unit of our device, those problematic PCs always failed, even trying with different units.

The root cause could be in the HW/FW design of our devices, or in the STM32CubeProgrammer toolchain, so:

  • In case the issue is on our side, do you have any idea of what could cause this phenomenon based on your experience? (e.g. bad HW design, STM32 Bootloader jump not performed correctly by the FW..)
  • In case the issue is inside STM32CubeProgrammer toolchain, Is there a way i can help in order to let you further analyze the issue and provide a fix? maybe providing you some log trace that the STM32CubeProgrammer produces on those problematic PCs. From our analysis, it seems that the issue lies inside the DFU_Driver, since even with a custom DFU library we wrote, we got the same result.

Can you please help? thanks!

10 REPLIES 10
Easydogctrc
Associate

I have an FX-4CR with the same problem still today (1/7/2025)..   pse advise resolution progress   currently have FX 1.7