Hi Xiaofan,
Thanks for such a prompt reply. yes, indeed after placing libusb-1.0.dll
(32 bit) into the respective directory mentioned,
I was able to get the usb instantiated.
Another question related to this, I was able to send a mass storage
command using ATA16 passthru.
The first command succeeded however the second similar command got back a
Pipe Error.
...
File "<stdin>", line 1, in <module>
File "usb\core.py", line 273, in read
File "usb\core.py", line 624, in read
File "usb\_debug.py", line 53, in do_trace
File "usb\backend\libusb10.py", line 483, in bulk_read
File "usb\backend\libusb10.py", line 581, in __read
File "usb\backend\libusb10.py", line 353, in _check
usb.core.USBError: Pipe error
Technically, using a usb analyzer, I should be able to get back the CSW
(Command Status Wrapper) indicating that I should
send a SCSI (Request Sense) to retrieve the sense data back from drive
for further diagnose.
The CSW should look like this(using a python enum):
dCSWSignature L
dCSWTag L
dCSWDataResidue L
bCSWStatus B
I have used another product to simulate the same command and able to see
the "Bulk CSW failed" and bCSWStatus indicate 1 which
means that I should issue the Request Sense data to retrieve back the
status.
Could it be the Pipe Error masquerading the CSW? Is there anyway to
disable that?
I do see do_sync_bulk_transfer in sync.c (extracted from git-hub) and not
all too familiar.
Thanks
Max
On Mon, Aug 23, 2010 at 5:28 PM, Xiaofan Chen <xiaof...@gmail.com> wrote:
> On Mon, Aug 23, 2010 at 12:59 PM, Max Teo <max...@gmail.com> wrote:
> > Hi,
> >
> > In case I had missed out the previous forum msgs, just wanted to ask
> why
> > there's no backend available when using
> > libusb10 as the backend.
> >
> > Using zadig as the tool to get the correct drivers installed for XP,
> the
> > mass storage device is correctly recognized in device manager.
>
> You need libusb-1.0.dll as well. You can get it from the binary
> snapshots.
> http://www.libusb.org/wiki/windows_backend
>
> For 32bit Windows, put 32bit libusb-1.0.dll to C:\Windows\system32.
>
> For 64bit Windows, put 64bit libusb-1.0.dll to C:\Windows\system32
> and 32bit libusb-1.0.dll to C:\Windows\Syswow64.
>
>
> --
> Xiaofan
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> pyusb-users mailing list
> pyusb-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pyusb-users
>
------------------------------------------------------------------------------
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
