On Tue, Aug 24, 2010 at 3:43 PM, Max Teo <max...@gmail.com> wrote: > Surprisingly as I had mentioned previously in the comments above, using a > bus analyzer, the CSW status can be retrieved if I > were to use another standalone Microsoft program to get the status back. > What do you think could have caused this? > > Something is preventing within this version that's preventing to read back > the CSW. I still think using lib-usb1.0 is a great start > and would like to contribute back if I were to find anything. > > Otherwise, what would you recommend?
I think libusb-1.0 should work if the other program works. A few suggestions. 1) Post your pyusb program and Wander or others may point out whether your python pyusb code is correct or not. 2) Enable debugging. libusb-1.0 Windows backend has the togglable debugging information (by calling libusb_set_debug(4)). pyusb should have similar things. 3) Or you can directly use libusb-1.0 and C for testing purpose. Since you have the bus analyzer, you can see the differences on the wire. -- Xiaofan ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ pyusb-users mailing list pyusb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pyusb-users
