Re: [Libusbx-devel] libusbx: error [cache_config_descriptors] could not access configuration descriptor

2014-09-24 Thread Qian Peng
Sorry for late response.
We have tried the lastest libusb and tested, the problem still exists.
We found not only in the device enumeration phase will be stuck, sometimes
also occur in the bulk transfer phase 995 error code
Related log is as follows:
2014-09-24 14:17:05:[0a28]
os/windows_usb.c:2067:windows_transfer_callback: handling I/O completion
with errcode 995, size 0
2014-09-24 14:17:05:[0a28]
os/windows_usb.c:2090:windows_transfer_callback: detected operation aborted

Errcode 995 always haunts us, we couldn't find the real cause of the
problem.
Could you please give us some ideas or tips to find the cause of the
problem?

Thanks

2014-09-03 21:46 GMT+08:00 Pete Batard p...@akeo.ie:

 On 2014.09.03 09:35, Qian Peng wrote:
  libusbx: error

 Looks like you are using libusbx, which has been superseded by libusb.
 Can you try with the latest libusb (Please visit http://libusb.info), in
 case it fixed that issue.

  the issue looks like
 
 http://sourceforge.net/p/libusbx/mailman/libusbx-devel/thread/1349577786.68914.1354005550176.JavaMail.open-xchange%40com4.strato.de/#msg30149384
 
  How do we avoid or solve the problem?

 As advised in the thread you point out, you may want to have a look at
 what USBView reports.

 Also, the device you are trying to access appears to be a Kingston
 DataTraveler 2.0 Stick (2GB) (http://www.linux-usb.org/usb.ids -
 0930:6544), which is a mass storage device.

 Can you clarify why you are trying to access a regular mass storage
 device using libusb on Windows? This means having to replace the default
 Mass Storage driver with WinUSB and losing native access to device as a
 flash drive, which seems like an odd thing to try to do...

 Regards,

 /Pete


 --
 Slashdot TV.
 Video for Nerds.  Stuff that matters.
 http://tv.slashdot.org/
 ___
 libusbx-devel mailing list
 libusbx-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/libusbx-devel

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel


Re: [Libusbx-devel] libusbx: error [cache_config_descriptors] could not access configuration descriptor

2014-09-03 Thread Pete Batard
On 2014.09.03 09:35, Qian Peng wrote:
 libusbx: error

Looks like you are using libusbx, which has been superseded by libusb.
Can you try with the latest libusb (Please visit http://libusb.info), in 
case it fixed that issue.

 the issue looks like
 http://sourceforge.net/p/libusbx/mailman/libusbx-devel/thread/1349577786.68914.1354005550176.JavaMail.open-xchange%40com4.strato.de/#msg30149384

 How do we avoid or solve the problem?

As advised in the thread you point out, you may want to have a look at 
what USBView reports.

Also, the device you are trying to access appears to be a Kingston 
DataTraveler 2.0 Stick (2GB) (http://www.linux-usb.org/usb.ids - 
0930:6544), which is a mass storage device.

Can you clarify why you are trying to access a regular mass storage 
device using libusb on Windows? This means having to replace the default 
Mass Storage driver with WinUSB and losing native access to device as a 
flash drive, which seems like an odd thing to try to do...

Regards,

/Pete

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel