STM32F412 board used as HID apears in Windows Device Manager as "Unknown USB Device ( Device descriptor Request failed )"

[CSand]

Hello dear ST Community,
I am not sure I can get help here as this topic is related to a WeAct Studio STM32F412 board and not a Nucleo or Discovery board from ST. If not that is fine , no problem.

So, back to my issue : 
For this particular type of project, in the past we used STM32F411 boards but this time we had to change to a board with more RAM's ...

The rest of the code in the MCU works as expected.
When we connect the USB cable to PC in the Device Manager we get this error :
"Unknown USB Device ( Device descriptor Request failed )"

We using CubeMX and STM32Cube in VSCode
In CubeMX I setup now just the basic USB_OTG_FS : Device only
Middleware : USB Device as Human Interface device class (HID)
** We can share code or ioc file if needed …

What I did :
- USB Clock is set 48MHz
- I tried HSI and HSE for the clock - there is said for the USB to work it requires HSE
- I changed the USB cable
- I revert to just basic HID and the default report ( but anyway Windows didn’t asked for it yet … )

Could you please help suggest what can be the cause of this ...

Best Regards,
Cristian

[AScha.3]

Hi,

Is it a board with USB connector soldered or you add it?

Because maybe d+ and d- lines are puzzled.

Check this.

 

And verify your CPU clock, using the MCO and check output with scope.

To be sure about the clock setting is doing what you expect.

 

And try other device settings, VCP .

Will it connect as com port....?

 

[Ozone]

> For this particular type of project, in the past we used STM32F411 boards but this time we had to change to a board with more RAM's ..

I’m a bit confused, since I have a F411 board of this type.
But this board has just a SWD header, and no onboard ST-Link with USB access.
The only USB port is under control of the target MCU, a F412 in your case.
Am I right ?

In this case, this might just be a problem of USB vendor and product IDs Windows complains about.

Have you tried it to connect it to a Linux system (a VM works as well), and checked the “lsusb” output ?