On 2012.07.24 19:40, Luiz Andrade wrote: > [ 0.937500] [00000264] libusbx: debug [init_device] (bus: 6, addr: 1, > depth: 1,port: 2): '\\.\USB#VID_091E&PID_0003#5&1FD24BBD&0&2' (...) > [ 0.968750] [00000264] libusbx: debug [get_api_type] driver(s): LIBUSB0 > [ 0.968750] [00000264] libusbx: debug [windows_get_device_list] found > existing device for session [2DB] (6.1) (...) > [ 0.968750] [00000264] libusbx: debug [libusb_open] open 6.1 > [ 0.968750] [00000264] libusbx: debug [unsupported_open] unsupported API > call for 'open' (unrecognized device driver)
According to the log, you haven't installed the right driver with Zadig. It appears that you installed the libusb0.sys driver, which is not currently supported by libusb/libusbx, whereas you need to install the the WinUSB one, which is the default. I suggest that you run Zadig again, select Options -> List All Devices, make sure WinUSB is selected on the right and click (Re)Install Driver. Once you have the WinUSB driver properly installed, xusb should succeed in opening the device. Still, I would advise you to follow Tim's advice. An SDK that is intended to make the features of your target device accessible should be the better choice both in reducing the time needing to be spent to achieve what you want and in user-friendliness as you won't have to ask users on Windows to replace the driver then. Regards, /Pete ------------------------------------------------------------------------------ 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
