2011/8/7 chris clark <clac...@gmail.com>: > On Sun, Aug 7, 2011 at 1:24 PM, Wander Lairson Costa > <wander.lair...@gmail.com> wrote: >> 2011/8/7 chris clark <clac...@gmail.com>: >>> 2) reset() problem (slightly different to known issue in readme for >>> libusb-1.0, I guess as I'm using libusb-01). The symptom I see is that >>> the TFT display appears to power off, I get no errors and no hangs. >>> When I try to re-run my script to send a new image I get time outs (it >>> isn't like the device isn't there as it opens fine.. but that may be >>> an artifact about the way libusb drivers work under Windows). Trace >>> back @eom for the 2nd run when the display is "off". Removing reset() >>> is the workaround here too and it works fine, I can re-run my script >>> under Windows and the display updates with the new image. When I ran a >>> debugger over the reset, the first time I got no problem (until this >>> point reset consistently "failed" for me), subsequent runs all "fail" >>> (even if I wait a few secs for each method call) and cause power off >>> at core.py:565 self._ctx.backend.reset_device(self._ctx.handle). Once >>> the TFT powers off I need to reboot the machine (kinda painful, any >>> ideas on how to re-start it or is this device specific?). >>> >> >> Bear in mind that after a reset, you have to do set_configuration >> again, as the device was just plugged in. If you are doing this, this >> may be a firmware problem. Do you face any reset problem under Linux? > > I do not have the same problem under Linux. I'm not even sure how I'd > power it off (assuming that is what happens) under Linux. > > I'm just running the script, it exits, and I run it again. The > set_configuration() is the first thing it does (and that is > successful), its the write that doesn't. > > > My guess is that this is a libusb issue but I wouldn't even know where > to start with that. > > Luckily omitting the reset works fine under Windows (in my simple > run/exit loop, I'm about to do a soak test over night of multiple > writes) > > >>> Slightly off topic, the PyUSB wiki appears to be down/empty (no errors >>> blank screen), http://pyusb.wiki.sourceforge.net/ >>> >> >> PyUSB was moved to Trac, you can access it at >> http://sourceforge.net/apps/trac/pyusb/ > > > Great! I'll have a scan through that. > > Could you update the sourceforge project page with that info? > https://sourceforge.net/projects/pyusb/ links the wiki (and it lists > it as the project page). >
I was sure I updated it, I am going to fix that, thanks to let me know this issue.. -- Best Regards, Wander Lairson Costa ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
