Skip to main content
KMin .1
KMin .1
Associate II
January 26, 2023
Solved

USB Clock Not surport PLLI2SQ? (STM32F412RE)

  • January 26, 2023
  • 7 replies
  • 3659 views

hello!

USB Clock Not surport PLLI2SQ?

0693W00000Y9CkPQAV.png0693W00000Y9CkUQAV.png0693W00000Y9CkjQAF.png

This topic has been closed for replies.
Best answer by Imen.D

Hi @KMin .1​,

Your project is successfully worked for me (using STM32CubeMX 6.7 and STM32Cube_FW_F4_V1.27.1)

Please make sure to follow this article USB device not recognized, with the solution is to either increase the heap size or configure the USB library to use static allocation.

Check if the USB_OTG_FS_DP and USB_OTG_FS_DM wires are swapped.

Check if you have this driver installed properly!

Hope my answer helps you.

When your question is answered, please close this topic by choosing Select as Best. This will help other users find that answer faster.

Imen

7 replies

I
Imen.D
ST Technical Moderator
January 26, 2023

Hello @KMin .1​,

Could you precise in which release you have found the issue? So, we can verify it.

Imen

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
KMin .1
KMin .1Author
Associate II
January 31, 2023

Hello!

FW version

0693W00000Y9Z9RQAV.pngUSB Device_Only mode. (Virtual Port Com)

Select PLLI2SQ clock.

Unknown USB Device (Device Descriptor Request Failed)

0693W00000Y9Z6SQAV.png​

​

Not Setting PLL48CLK Mux ?​ PLLQ 50Mhz?

0693W00000Y9Z6hQAF.png

I
Imen.D
ST Technical Moderator
February 2, 2023

Hi @KMin .1​ ,

Thanks for sharing the details.

Which CubeMx version are you using?

Please share your ioc file in order to reproduce the case.

Imen

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
Piranha
Piranha
Principal III
January 27, 2023

Most likely CubeMX just didn't configure that setting properly or at all. That is an absolutely normal thing for that broken bloatware generator.

Terms & ConditionsAccessibility statement