On Fri, Nov 30, 2012 at 9:05 AM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Fri, Nov 30, 2012 at 3:06 AM, Arne Pagel <a...@pagelnet.de> wrote: >> Anyway, >> here is the output from USBView, with the Configuration Descriptor Flag on. >> (Other devices show something there) >> >> Device Descriptor: >> bcdUSB: 0x0110 >> bDeviceClass: 0xFF >> bDeviceSubClass: 0x00 >> bDeviceProtocol: 0x00 >> bMaxPacketSize0: 0x40 (64) >> idVendor: 0x16D0 >> idProduct: 0x05BE >> bcdDevice: 0x0100 >> iManufacturer: 0x01 >> iProduct: 0x02 >> iSerialNumber: 0x03 >> bNumConfigurations: 0x01 >> >> ConnectionStatus: DeviceConnected >> Current Config Value: 0x01 >> Device Bus Speed: Full >> Device Address: 0x08 >> Open Pipes: 2 >> >> Endpoint Descriptor: >> bEndpointAddress: 0x81 IN >> Transfer Type: Bulk >> wMaxPacketSize: 0x0040 (64) >> bInterval: 0x00 >> >> Endpoint Descriptor: >> bEndpointAddress: 0x01 OUT >> Transfer Type: Bulk >> wMaxPacketSize: 0x0040 (64) >> bInterval: 0x00 > > You forget to CC the list. Anyway, the USBView > output seems normal and at least your device > enumerated properly.
Just to make sure it is not a libusbx specific problem, you can use klist from libusbK to see if it can print out the descriptor. You can also try to switch the device driver among libusbk.sys, libusb0.sys and winusb.sys using Zadig. libusbk: http://sourceforge.net/projects/libusbk/ Zadig: http://sourceforge.net/projects/libwdi/files/zadig/ -- Xiaofan ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: TUNE You got it built. Now make it sing. Tune shows you how. http://goparallel.sourceforge.net _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
