On Thu, May 13, 2010 at 8:22 AM, <[email protected]> wrote: > And yes, the warning message is nothing to worry about. I just thought > that it might be useful to have in case somebody ever encountered an > issue with a kernel driver that bound itself to the RF2500's USB > interface (as it is mislabelled as an HID). >
Ah I see. It is a USB composite device which has the CDC-ACM interface and the HID interface. http://mspdebug.sourceforge.net/usb.html BTW, you may need to detach the kernel HID driver before running lsusb. In that case, you should be able to print out the report descriptor. Reference here: http://old.nabble.com/How-to-dump-HID-report-descriptor-under-Linux-td19609562.html It is not really mis-labeled as HID, but rather due to the fact that Windows has built-in HID driver and people want to avoid writing drivers. So many simple device vendors develop such pseudo HID device which has nothing to do with Human Interface. >From the above USB descriptor, there may be some issues with libusb-win32. You have several solutions for the driver. 1) Use the filter driver. In this case, you can continue using the existing TI Windows driver. But be sure to use the later snapshot version and not the 0.1.12.2 version if you are using Vista/Win7. 2) Use the libusb-win32 device driver to be the driver of the whole USB device (use INF wizard). In this case, you lose the UART interface. 3) Use the libusb-win32 device driver to replace the HID driver for the HID interface. In this case, you need to specify the interface number in the INF file (MI_04 for the HID interface). Or you can move to the new libusb-1.0 Windows backend. The HID backend there are not that matured yet. But I think it should work for you. I am also one of the main testers for libusb-1.0 Windows backend. http://www.libusb.org/wiki/windows_backend -- Xiaofan http://mcuee.blogspot.com
