Skip to main content
Treacy Yao
Associate III
Jul 9, 2019 3:24 AM UTC
Solved

CDC Device descriptior request failed

I want to realize CDC function to transimit/receive data to/from PC via STM32F105RB. I get the code from Cube. Set clock, enable CDC and modify heap size to 0x1000. But when I power on deivce, "Device descriptior request failed" shown.

1.I don't know where is the problem.

2.By the way, For the PC driver, "Starting from windows 10, the STSW-STM32102 driver is no more adequate and the usage of the native inbox driver is recommanded", I don't konw where can get native inbox drive? This is mean I don't need to install driver in WIN10. Now I'm using win10 to do the testing.

3.I also tired WIN7(32bit), still have the "Device descriptior request failed" problem.

Please help me.

This topic has been closed for replies.
asbjorn.heid
asbjorn.heidBest answer
Visitor II
Jul 10, 2019 1:10 PM UTC

Did you implement CDC_Control_FS handling? See my post in https://community.st.com/s/question/0D50X0000A4nieqSQA/how-to-implement-usb-cdc

27 replies

Tesla DeLorean
Guru
Jul 10, 2019 5:37 AM UTC

Is this on known working hardware?

In BOOT0=HIGH, can you see up a STM32 USB DFU device?

I'm not looking to wade through 18MB of someone else's Cube project. You'll need to debug your own work. Instrument functionality to you can see/understand what is happening.

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
asbjorn.heid
asbjorn.heidBest answer
Visitor II
Jul 10, 2019 1:10 PM UTC

Did you implement CDC_Control_FS handling? See my post in https://community.st.com/s/question/0D50X0000A4nieqSQA/how-to-implement-usb-cdc

Treacy Yao
Associate III
Jul 11, 2019 6:19 AM UTC

Thank you for your response. I have tried as you said and still have the "Device descriptior request failed" in WIN10. I attach my files. Please have a check.

I doubt maybe it is hardware problem, but How can I confirm with oscilloscope? I'm the green hand for USB.

asbjorn.heid
Visitor II
Jul 10, 2019 1:10 PM UTC

And regarding 2) yes, Windows 10 has built-in driver, so no need to install.

Trevor Jones
Senior
Jul 16, 2019 10:02 PM UTC

I fixed this issue yesterday...

the crystal was set to bypass clock, so it used the internal 48MHz and half worked...

Do you have a crystal ? check the frequency on the scope.. it has to be correct in the cube...

Treacy Yao
Associate III
Jul 17, 2019 1:15 AM UTC

I selected Crystal/Ceramic ReSonatar for HSI and LSE. Do you mean let me try to select BYPASS clock for  HSI and LSE?

Trevor Jones
Senior
Jul 17, 2019 3:08 AM UTC

I had to set it to Crystal, and then I checked the crystal was running on the scope at 8MHz

Then set that in the cube, it works now...

T J
Senior III
Jul 17, 2019 7:08 AM UTC

please check your crystal is running with a scope, do you have one ?

please check that inside the cube the crystal is connected to the PLL and running the system clock and the USB port.

I am sure this is the problem, since it half works, just like mine did.

Treacy Yao
Associate III
Jul 17, 2019 11:51 AM UTC

Sorry that I don't understand your meaning clearly. I check the HSE and USB D+ frequency. Please have a check.0690X000009Ypn0QAC.jpg0690X000009YpmqQAC.jpg

Trevor Jones
Senior
Jul 17, 2019 12:18 PM UTC
very difficult to see the voltage of the crystal, and the frequency is not exactly 16MHz ? it should be 16.00 I would expect.
now check in the cube, is the HSE selected as the clock source ?
check it all the way to the usb clock 48MHz inside the cube clock configuration page.