-
Notifications
You must be signed in to change notification settings - Fork 911
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown USB Device (Invalid Configuration Descriptor) #3815
Comments
@dimpolo I don't have a u5 mcu to test this out on but could you try replacing PLL1_P to PLL1_Q on line 39 of examples/stm32u5/usb_hs_serial.rs? Could be a timing issue with the PLL setup. this is a shot in the dark, may not fix it. // Use PLL1_Q (48MHz) for the USB clock. |
I only tried this out on the Nucleo so far as the project I'm building with that chip is not yet done on the hw design side and also only got a Linux machine here to test. It does look like the USB stack is coming up just fine but the descriptor looks off. Can you check from Windows what it actually sees and if it matches your configured USB descriptor? |
Thanks a lot for the responses! @guptaarnav PLL1_Q is not a setting I can select. The available values are: pub enum Otghssel {
#[doc = "HSE selected"]
HSE = 0x0,
#[doc = "PLL1 “P” (pll1_q_ck) selected,"]
PLL1_P = 0x01,
#[doc = "HSE/2 selected"]
HSE_DIV_2 = 0x02,
#[doc = "PLL1 “P” divided by 2 (pll1_p_ck/2) selected"]
PLL1_P_DIV_2 = 0x03,
} @MDr164 I'll try to find this information and get back at you |
@MDr164 Next I tried using a Linux machine, but I'm not familiar with it at all. Using usbmon I got these logs
Do you have a recommendation for how to proceed? |
Wow, so under Linux all is working fine. I was able to use minicom and send and receive data on /dev/ttyACM3 |
Most of the USB examples leave the msos descriptor empty. You probably need that one for Windows to correctly detect your device. If you look at the example in the u5 folder try adding an msos descriptor the same way the bos descriptor is added. Also looks like for CDC_ACM you probably also want to add those lines to the example code for Windows in particular to the usb config:
|
I added the config lines. This resulted in Sorry I don't quite follow about the msos. The only examples I found that make use of msos seem to be WINUSB related. Should I copy those? |
I'm having a similar issue with stm32u5a5zj chip on the NUCLEO U5A5ZJ-Q dev board. Here are the logs:
|
I'm trying to get stm32u595ri USB communication working.
After applying these changes I'm running the following:
On Windows 10 I'm seeing:
And this inside Device Manager:

I'm assuming it's not a hardware issue. This is because tying BOOT0 to VDD successfully allows me to interface with the chip using the USB DFU bootloader.
Here's the logs:
The text was updated successfully, but these errors were encountered: