But when I change the firmware back to using the VID/PID that I started with, and then connect the device to my development PC, it shows up in Device Manager under "Other devices" with an error icon. Now I've gotten the device to enumerate successfully on Windows 7, 8, and 10 PCs as a WinUSB device, and I've established communication. What are best practices on the (Windows) PC-side for testing/development of USB device firmware, during the stage when device descriptors and metadata are in flux? Is it possible to avoid chewing up PIDs just to avoid the Windows caching?īecause of the way Windows caches USB descriptors and the like from previous enumerations, during firmware development, I was incrementing the device Product ID (PID) in the firmware after each time I made other changes, to ensure that Windows wasn't caching things from previous iterations of the descriptors, and messing up stuff that would otherwise work.Is Windows caching USB metadata the cause of the failed enumeration on this one PC?.How can I get this to work with my desired VID/PID combo on my development PC?.If I change the PID to some other number (new to my development PC), it does enumerate correctly. My development PC had previously tried to enumerate the device when it had the same VID/PID combo, but with different descriptors/metadata.
SERIAL USB MIDI DRIVER WINDOWS 10 WINDOWS 10
The device is enumerated correctly on other Windows 10 hosts, but not on my Windows 10 development PC.
SERIAL USB MIDI DRIVER WINDOWS 10 DRIVER
The device includes Microsoft Windows Compatible IDs (WCIDs) to enable automatic installation of the WinUSB driver on the PC. I'm developing firmware and a PC test application for a custom USB device, using the STM32F072 Discovery board.
0 kommentar(er)
