On Wed, Apr 14, 2010 at 10:24 PM, Wander Lairson <wander.lair...@gmail.com> wrote:
> 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... > You seem to have two test firmware, one for PIC, one for ARM. I only tried the PIC. You are basing your PIC firmware on the old V1.x stack which may have some issues. http://www.microchip.com/forums/tm.aspx?m=275422 And there are quite often problem like this: first run works and then 2nd run got time out. Typically the issue only happens under Linux. It is mostly related to set_interface command response. In this case, it is under Windows. So maybe the issue is different. -- Xiaofan http://mcuee.blogspot.com ------------------------------------------------------------------------------ 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
