>> ====================================================================== >> ERROR: runTest (test_integration.DeviceTest) >> ---------------------------------------------------------------------- >> Traceback (most recent call last): >> File "c:\cygwin\home\mcuee\mcu\pyusb\pyusb\tests\test_integration.py", line >> 59 >> , in runTest >> self.test_write_read() >> File "c:\cygwin\home\mcuee\mcu\pyusb\pyusb\tests\test_integration.py", line >> 12 >> 0, in test_write_read >> ret = utils.to_array(self.dev.read(ep[1], len(data))) >> File "c:\cygwin\home\mcuee\mcu\pyusb\pyusb\usb\core.py", line 632, in read >> self.__get_timeout(timeout) >> File "c:\cygwin\home\mcuee\mcu\pyusb\pyusb\usb\backend\libusb10.py", line >> 461, >> in bulk_read >> timeout) >> File "c:\cygwin\home\mcuee\mcu\pyusb\pyusb\usb\backend\libusb10.py", line >> 549, >> in __read >> timeout)) >> File "c:\cygwin\home\mcuee\mcu\pyusb\pyusb\usb\backend\libusb10.py", line >> 344, >> in _check >> raise USBError(_str_error[retval.value]) >> USBError: Operation timed out >> Deeper investigation showed that it is caused by calling set_configuration twice when device is connected. Example:
import usb.core d = usb.core.find(idVendor=0xfffe) d.set_configuration() d.write(1, '0123456789') d.read(0x81, 10) The first time after connecting the device you run this script, it works fine, but next tries cause timeout error. If you disconnect and connect the device again, it works again. I suspect this is a test firmware bug. Keep investigating... ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
