|
From: kirkq <kir...@ho...> - 2011-04-09 18:24:40
|
My previous post was not posted to the mailing list, so I am adding an update after subscribing. Continuing from my previous post, we are unsure if the problem exists in the firmware code, the Visual Studio code, or our circuit implementation, or particularly how to go about debugging this. The default response by Windows upon pointing to the driver is to revert to the default driver in Windows\inf\usb.inf with a PID and VID of 0000, which is obviously not correct. We probed with an oscilloscope and determined that one of the D+ and D- lines is being pulled high as expected, but we were unable to observe any synchronization bits or PID bits. -- View this message in context: http://libusb.6.n5.nabble.com/devices-list-is-empty-on-Windows-x64-tp3981870p4293271.html Sent from the LibUSB Dev - Win32 mailing list archive at Nabble.com. |