|
From: Xiaofan C. <xia...@gm...> - 2011-04-09 23:42:43
|
On Sun, Apr 10, 2011 at 2:24 AM, kirkq <kir...@ho...> wrote: > 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. > You should start a new thread and since your previous post is not accepter by the mailing list, please post that as well. http://libusb.6.n5.nabble.com/devices-list-is-empty-on-Windows-x64-tp3981870p4291905.html Anyway, your problem is totally different from the original thread. You need to solve the "unknown device" problem first before you can install any driver for your device. This is not a libusb-win32 problem. As for "unknown device", it can be hardware or firmware problem. Please post to Microchip forum here for more help. You may need to post your schematics there for hardware check. http://www.microchip.com/forums/f102.aspx -- Xiaofan |