CDC Device descriptior request failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-08 8:24 PM
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.
Solved! Go to Solution.
- Labels:
-
STM32F1 Series
-
USB
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-10 6:10 AM
Did you implement CDC_Control_FS handling? See my post in https://community.st.com/s/question/0D50X0000A4nieqSQA/how-to-implement-usb-cdc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-09 10:37 PM
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.
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-10 6:10 AM
Did you implement CDC_Control_FS handling? See my post in https://community.st.com/s/question/0D50X0000A4nieqSQA/how-to-implement-usb-cdc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-10 6:10 AM
And regarding 2) yes, Windows 10 has built-in driver, so no need to install.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-10 11:19 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-16 2:43 AM
Could you please have a check my code?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-16 7:58 AM
I don't have your mcu, so I've copied your code to an empty STM32F103 project. I've managed to reproduce the error, and tried comparing it with my successful code. I've not yet found any differences that could explain it, but I'll have a closer look tonight.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-16 3:02 PM
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...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-16 6:03 PM
Please, this fucntion have taken a long time. Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2019-07-16 6:15 PM
I selected Crystal/Ceramic ReSonatar for HSI and LSE. Do you mean let me try to select BYPASS clock for HSI and LSE?
