cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeProgrammer cannot connect to system bootloader over direct USB, but works over USB-hub

leshich-k
Associate II

We faced that issue on a couple of diffeent PCs working under Windows 7/10 x64.

We experience this for some (not all) STM32H7xx and STM32F7xx MCUs.

Trying to connect to system bootloader over USB directly connected to PC we often see something like this:

 14:48:19 : STM32CubeProgrammer API v2.8.0

 14:48:44 : USB speed  : Full Speed (12MBit/s)

 14:48:44 : Manuf. ID  : STMicroelectronics

 14:48:44 : Product ID : STM32 BOOTLOADER

 14:48:44 : SN     : 00000008FFFF

 14:48:44 : FW version : 0x011a

 14:48:44 : Device ID  : 0x0449

 14:48:44 : UPLOADING OPTION BYTES DATA ...

 14:48:44 :  Bank     : 0x00

 14:48:44 :  Address    : 0x1fff0000

 14:48:44 :  Size     : 44 Bytes

 14:48:44 : Error: Uploading Option Bytes bank: 0 failed

 14:48:44 : Error: Initializing the Option Bytes failed

i.e. USB connection exists but some error occurres during read Option Bytes memory.

When we connect USB cable over USB hub - no problems occures:

 15:00:57 : USB speed  : Full Speed (12MBit/s)

 15:00:57 : Manuf. ID  : STMicroelectronics

 15:00:57 : Product ID : STM32 BOOTLOADER

 15:00:57 : SN     : 00000008FFFF

 15:00:57 : FW version : 0x011a

 15:00:57 : Device ID  : 0x0449

 15:00:58 : UPLOADING OPTION BYTES DATA ...

 15:00:58 :  Bank     : 0x00

 15:00:58 :  Address    : 0x1fff0000

 15:00:58 :  Size     : 44 Bytes

 15:00:58 : UPLOADING ...

 15:00:58 :  Size     : 1024 Bytes

 15:00:58 :  Address    : 0x8000000

 15:00:58 : Read progress:

 15:00:58 : Data read successfully

No matter what version of Cube Programmer we use, 2.7-2.9. Looks very much like STM USB driver bug.

Has anyone faced something like this?

2 REPLIES 2

Usually it's hub, docks and poor cables causing issues rather than remediating them.

USB 3.0 ports?

Common design/make of machine with the problem?

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
leshich-k
Associate II

We tried both 3.0 and 2.0. There's no difference.

Mechines are pretty different, with different CPUs and motherbords. We couldn't find dependencies that might lead to a problem.

More likely this is a driver issue