You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
running [email protected] on an STM32H7 with usbd-serial and usbd-hid and everything is working okay on linux, but when connected to windows enumeration is attempted four times then fails with the error:
Windows has stopped this device because it has reported problems. (Code 43)
The USB device returned an invalid USB configuration descriptor.
digging into device manager reports USB\CONFIGURATION_DESCRIPTOR_VALIDATION_FAILURE and somewhat interestingly doesn't seem to correctly parse out the VID:PID (though the device descriptor read appears okay).
i think the next step is to try isolating the hid and serial interfaces to make sure it's not specific to one of them, but i'd definitely appreciate any thoughts!
update: serial or hid each works by itself, but combining the two leads to failures...
The text was updated successfully, but these errors were encountered:
looks like this was related to #102... resolved by increasing .max_packet_size_0(64), swapping to .composite_with_iads(), and making sure the hid interface is initialised and polled before the serial one (the other way around does not work for windows apparently).
hi folks,
running
[email protected]
on an STM32H7 withusbd-serial
andusbd-hid
and everything is working okay on linux, but when connected to windows enumeration is attempted four times then fails with the error:digging into device manager reports
USB\CONFIGURATION_DESCRIPTOR_VALIDATION_FAILURE
and somewhat interestingly doesn't seem to correctly parse out the VID:PID (though the device descriptor read appears okay).here is the defmt log from the device: stm32-usb-log.txt and a pcap captured using a cynthion between the host and device: stm32-usb-pcap.zip
this looks very similar to a couple of prior issues, though PRs suggest these were resolved:
i think the next step is to try isolating the hid and serial interfaces to make sure it's not specific to one of them, but i'd definitely appreciate any thoughts!
update: serial or hid each works by itself, but combining the two leads to failures...
The text was updated successfully, but these errors were encountered: