On 28 Jun 2012 Pete Batard Wrote: > To eliminate the compiler, can you please download the > libusbx-1.0.12-win.7z from > http://sourceforge.net/projects/libusbx/files/releases/1.0.12/Windows/ > and run the xusb.exe you find there in examples/bin32, prerablly with > LIBUSB_DEBUG=4. If you get the same error, then we can eliminate BC++ > as the possible cause.
> Also the information I get for VID_10C4&PID_0001 according to [1]), is > that it's an HID touch screen kit. Is that correct? The xusb.exe in released 1.0.12 also have the same result. I think the problem mostly was caused by my device. It is a device I had built years ago using Silabs' F8051F320 and their Development tool Version 2.2 with included HID example source. Today I use three utilities(HIDTest.exe, SimpleHIWrite.exe and USBDeview.exe) to check my device. The first two were hung when their "Device Info" or "Info" button was pressed, and has to force to close. The third one works normally but I think it is because it didn't touch the configuration descriptor. Also use the "Advanced USB port monitor" to check. The device was listed as "disconnected"? By double clicks it, a info window pop out shows the Device descriptor and Endpoint descriptor, but no Configuration and Interface descriptors in it. It's my device's problem, have to figure it out. But some hints from you experts should be helpful:-) Best Regards, Jach ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
