Xiaofan Chen | 8 Dec 05:53 2014
Picon

Re: Libusb-win32-devel unsubscribe notification

On Mon, Dec 8, 2014 at 12:51 PM,
<sitelist-bounces <at> lists.sourceforge.net> wrote:
> aaguerra11 <at> gmail.com has been removed from Libusb-win32-devel.
>

FYI. The user has already been removed due to sending quite a few spams.

--

-- 
Xiaofan

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
aaguerra11 | 8 Dec 03:05 2014
Picon

[SPAM] Recordatorio: aaguerra11 <at> gmail.com quiere seguirte. ¿Aceptas?

¡Haz clic aquí para descubrir las páginas web favoritas de aaguerra11 <at> gmail.com!
aaguerra11 <at> gmail.com quiere seguirte
Me gustaría añadirte como amigo
-aaguerra11 <at> gmail.com
Aceptar Rechazar
Haz clic aquí para cancelar la suscripción a estos correos electrónicos de aaguerra11 <at> gmail.com y del resto de amigos


P.O. BOX 70928, Sunnyvale, CA 94086
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
aaguerra11 | 4 Dec 00:08 2014
Picon

[SPAM] aaguerra11 <at> gmail.com quiere seguirte. ¿Aceptas?

¡Haz clic aquí para descubrir las páginas web favoritas de aaguerra11 <at> gmail.com!
aaguerra11 <at> gmail.com quiere seguirte
Me gustaría añadirte como amigo
-aaguerra11 <at> gmail.com
Aceptar Rechazar
Seguir a aaguerra11 <at> gmail.com te ayuda a descubrir buenas páginas web que ella recomienda :)
Haz clic aquí para cancelar la suscripción a estos correos electrónicos de aaguerra11 <at> gmail.com y del resto de amigos


P.O. BOX 70928, Sunnyvale, CA 94086
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Mathieu Laurendeau | 27 Nov 21:19 2014
Picon

Windows crash using libusbk and btstack

Hello,

I did not find any bug tracker so I'm posting to this list.
When using the libusbk driver (installed using Zadig Version 2.1.0 Build 
658) and btstack [1][2], I consistently get Windows crashes (most of the 
time with no BSOD).
It works fine with the WinUSB driver.
Below is a report I get using WhoCrashed:

On Wed 11/26/2014 4:33:58 PM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: libusbk.sys 
(libusbK+0x3349)
Bugcheck code: 0xA (0x8, 0x2, 0x1, 0xFFFFF800032EF971)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\libusbk.sys
product: libusbK.sys
company: http://libusb-win32.sourceforge.net
description: libusbK(lusbk) WDF USB Driver
Bug check description: This indicates that Microsoft Windows or a 
kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be 
caused by a hardware problem.
A third party driver was identified as the probable root cause of this 
system error. It is suggested you look for an update for the following 
driver: libusbk.sys (libusbK(lusbk) WDF USB Driver, 
http://libusb-win32.sourceforge.net).
Google query: http://libusb-win32.sourceforge.net IRQL_NOT_LESS_OR_EQUAL

Please tell me what data I can provide to help analyzing/fixing this issue.

Regards,
Mathieu Laurendeau

[1] https://code.google.com/p/btstack/
[2] https://github.com/matlo/btstack

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
mahnaz.n0098 | 16 Nov 07:30 2014
Picon

mahnaz.n0098 <at> gmail.com has indicated you're a friend. Accept?

Click here to discover mahnaz.n0098 <at> gmail.com's favorite websites!
mahnaz.n0098 <at> gmail.com wants to follow you
I would like to add you as a friend
-mahnaz.n0098 <at> gmail.com
Accept Decline
Following mahnaz.n0098 <at> gmail.com helps you discover great websites they recommend :)
Click here to unsubscribe from such emails from mahnaz.n0098 <at> gmail.com or all friends


P.O. BOX 70928, Sunnyvale, CA 94086
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Sandor Otvos | 4 Nov 11:22 2014
Picon

filter-driver installer wizard do not show device

Hi

Filter driver wizard show this:

If your device isn't listed, it may already be filtered, be in a "driverless" state, or incompatible with the libusb-win32 filter driver.

However my device showed with win8/usb3 
My target device is an external hub, if i connect it to win8/usb3 port  ( driven by MS usbhub3.sys )
it works well
If i connect other usb2 port, or used on win7 , libusb-filter-installer do not list my hub device

Is libusb filter compatible only MS usbhub3.sys driver ?
Any other combinations wont work for me. 

How can i install filter driver to external hub on win7 ?

Thanks for any advice on this.....
------------------------------------------------------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Chris Chaffey | 30 Oct 20:59 2014

Packets that are exactly a multiple of the EP size fail

Hi All,

 

I’m using LibUsb-Win32 version 1.2.6 to communicate with a device that I am trying to reverse engineer.  When the device sends data to me that is not equal to a multiple of the endpoints wMaxPacketSize, I never receive that packet.  I have used a program called freeusbanalyzer that has given me the following output (with some annotations on my part):

 

<-------------- In the middle of streaming download from device

00000348            30.10.2014 16:24:47.289               +0.094   UP          0x00000000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Streaming data

00000350            30.10.2014 16:24:47.392               +0.100   DOWN  0x00000000               URB_FUNCTION_ABORT_PIPE

00000351            30.10.2014 16:24:47.392               +0.0       UP          0xc0010000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Zero byte

00000352            30.10.2014 16:24:47.392               +0.0       UP          0x00000000               URB_FUNCTION_ABORT_PIPE

00000354            30.10.2014 16:24:47.488               +0.094   UP          0x00000000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Streaming data

00000356            30.10.2014 16:24:47.591               +0.100   DOWN  0x00000000               URB_FUNCTION_ABORT_PIPE

00000357            30.10.2014 16:24:47.591               +0.0       UP          0xc0010000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Zero byte

00000358            30.10.2014 16:24:47.591               +0.0       UP          0x00000000               URB_FUNCTION_ABORT_PIPE

00000360            30.10.2014 16:24:47.688               +0.095   UP          0x00000000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Streaming data

00000362            30.10.2014 16:24:47.791               +0.100   DOWN  0x00000000               URB_FUNCTION_ABORT_PIPE

00000363            30.10.2014 16:24:47.791               +0.0       UP          0xc0010000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Zero byte

00000364            30.10.2014 16:24:47.791               +0.0       UP          0x00000000               URB_FUNCTION_ABORT_PIPE

00000366            30.10.2014 16:24:47.894               +0.100   DOWN  0x00000000               URB_FUNCTION_ABORT_PIPE

00000367            30.10.2014 16:24:47.894               +0.0       UP          0xc0010000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Zero byte

00000368            30.10.2014 16:24:47.894               +0.0       UP          0x00000000               URB_FUNCTION_ABORT_PIPE

00000370            30.10.2014 16:24:47.899               +0.002   DOWN  0x00000000               URB_FUNCTION_CONTROL_TRANSFER

00000371            30.10.2014 16:24:47.899               +0.0       UP          0x00000000               URB_FUNCTION_CONTROL_TRANSFER

00000372            30.10.2014 16:24:47.900               +0.0       DOWN  0x00000000               URB_FUNCTION_CONTROL_TRANSFER

00000373            30.10.2014 16:24:47.900               +0.0       UP          0x00000000               URB_FUNCTION_CONTROL_TRANSFER

00000374            30.10.2014 16:24:47.901               +0.0       DOWN  0x00000000               URB_FUNCTION_CONTROL_TRANSFER

00000375            30.10.2014 16:24:47.901               +0.0       UP          0x00000000               URB_FUNCTION_CONTROL_TRANSFER

00000376            30.10.2014 16:24:47.902               +0.0       DOWN  0x00000000               URB_FUNCTION_CONTROL_TRANSFER

00000377            30.10.2014 16:24:47.902               +0.0       UP          0x00000000               URB_FUNCTION_CONTROL_TRANSFER

00000378            30.10.2014 16:24:47.997               +0.094   DOWN  0x00000000               URB_FUNCTION_ABORT_PIPE

00000379            30.10.2014 16:24:47.997               +0.0       UP          0xc0010000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Streaming data; never receive this "chunk"

00000380            30.10.2014 16:24:47.997               +0.0       UP          0x00000000               URB_FUNCTION_ABORT_PIPE

00000382            30.10.2014 16:24:48.099               +0.100   DOWN  0x00000000               URB_FUNCTION_ABORT_PIPE

00000383            30.10.2014 16:24:48.099               +0.0       UP          0xc0010000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Zero byte

00000384            30.10.2014 16:24:48.099               +0.0       UP          0x00000000               URB_FUNCTION_ABORT_PIPE

00000386            30.10.2014 16:24:48.193               +0.091   UP          0x00000000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Next block of streaming data.  Fails because previous chunk was not received.

00000388            30.10.2014 16:24:48.197               +0.002   DOWN  0x00000000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Stop stream message

00000390            30.10.2014 16:24:48.292               +0.095   UP          0x00000000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Stop stream ACK

00000392            30.10.2014 16:24:48.300               +0.005   DOWN  0x00000000               URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER  <-- Restart at failed chunk

 

The problem pops up at 30.10.2014 16:24:47.997.  This chunk is exactly 64 bytes in length.  It doesn’t matter how many times I request that chunk it will always fail.  This happens in other parts of the stream as well, and it only seems to be when the chunk is a multiple of 64 bytes in length.  The only other difference I see between that chunk and all the other chunks that do go through is that it always has a status of USBD_STATUS_CANCELED (0xc0010000).

 

My code is fairly straight-forward and it is executed in a thread:

 

        int size = maxInSize * 4;

        uint8_t buf[size];

        int len = 0;

        int r = libusb_bulk_transfer(handle, epIn, buf, size, &len, MAX_RECV_TIMEOUT);

        if ((r != LIBUSB_ERROR_TIMEOUT) && (r != LIBUSB_SUCCESS))

        {

                // This method will timeout every MAX_RECV_TIMEOUT milliseconds when no data is available.  No need to log this condition.

                LogLibUsbReturn(r, "libusb_bulk_transfer");

        }

        if ((r == LIBUSB_SUCCESS) && (len > 0))

        {

                std::lock_guard<std::recursive_mutex> lock(readMutex);

               inData.append((char*)buf, len);

        }

 

Thanks for your time,

 

Chris

------------------------------------------------------------------------------
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Aymen JEBALI | 29 Sep 16:29 2014
Picon

Bulk USB transfers works with USB3.0 ports and not with USB2.0

Hi All,
 
I am developping an USB to I2C bridge using the SAM3U4E microcontroller.
The USB communication works fine untill I used the USB isolator cable : https://iftools.com/isolator/isousbcable/index.en.php
 
With this configuration I still have control transfers to work correctly but not the bulk transfers.
But I noticed that the bulk transfers are working fine when I connect the USB cable to an USB3.0 port. but it fails with USB2.0.
 
I am using the libusb-win32 APIs.
 
The failure is always at usb_claim_interface:
[12224] libusb0-dll:err [claim_interface] could not claim interface 0, invalid configuration 0
Could anyone please suggest a solution ?
 
I upgraded to lubsubK drivers 3.0.7.0 but no success.
 
Best regards,
Aymen Jebali
 
------------------------------------------------------------------------------
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Pradeepa Senanayake | 23 Sep 14:26 2014
Picon

LibusbK API clarification for UsbK_ReadPipe

Hello,

I have a quick question.

Are UsbK_ReadPipe and UsbK_WritePipe functions synchronous? 

If I set a timeout using the SetPipePolicy function will these functions wait that time until the timeout or data transfer complete?

During the timeout what is the return value coming from GetLastError() ?

Best Regards,
Pradeepa Senanayake.
------------------------------------------------------------------------------
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=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
samira taremi | 14 Sep 19:18 2014
Picon

Errno:۱۹ _Please Help

Hi
Good time
Excuse me, I want to run a sample by site nfcpy
And library libusb-win32-bin-1.2.6.0 and pyusb-1.0.0a2 and
  pyserial-2.7.win32_py3k.exe and add nfc and bzrlib but unfortunately I did not recognize the usb device and run the following simple command does not show the error below:

import nfc
clf = nfc.ContactlessFrontend ('udp')
print (clf)
The error:

IOError: [Errno: 19] No such device

For libusb-win32-bin-1.2.6.0 file named install-filter-win.exe ran to the library to recognize mobile usb nfc c drive in a folder in the installation program copied Lib pyserial
2.7.win32_py3k.exe file and then run run was added in the library itself pyusb bzr, and I added to my library.

But still the above error is shown
Thank you for helping me get my

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
Stephen B | 25 Aug 22:55 2014
Picon

LibUsbK Isochronous Write C# example

Hello,

I am trying to write isochronous data to my USB device. I tried the xfer-iso c example but had no luck to compile it, and preferably I want to use C# anyway. So I looked at the C# examples and found Read.Isochronous. This compiles and works, but unfortunately there is no Write example.

I tried to create it myself using the c example and the Read.Isochronous example, but with no luck yet. When writing, the following line always returns error 50 (the request is not supported):
usb.IsoWritePipe(pipeInfo.PipeId, dataBuffer, dataBuffer.Length, ovlkHandle, Iso.Handle);

I also can't find any iso out packets with USBPcap.

Does anyone have any idea what's causing this? I have attached my code along with a descriptor report of my device. There are 5 unnecessary endpoints from my base firmware code, but I decided to keep them in for now to prevent causing more bugs, as my device has worked and transferred iso data with libusb in the past.

Thanks in advance for any help!

Kind regards,
Stephen
-Device:
  bLength             :18
  bDescriptorType     :0x01
  bcdUSB              :0x0200
  bDeviceClass        :0x00 (Defined at Interface level)
  bDeviceSubClass     :0x00
  bDeviceProtocol     :0x00
  bMaxPacketSize0     :8
  idVendor            :0x03EB (Atmel Corp.)
  idProduct           :0x2423
  bcdDevice           :0x0100
  iManufacturer       :1 (LaserFX)
  iProduct            :2 (LaserFX USB Interface)
  iSerialNumber       :3 (9CEF79E83953333838362020FF1816)
  bNumConfigurations  :1
!End Device
-Configuration:
  bLength             :9
  bDescriptorType     :0x02
  wTotalLength        :69
  bNumInterfaces      :1
  bConfigurationValue :0x01
  iConfiguration      :0
  bmAttributes        :0xC0
  MaxPower            :50 (100ma)
 -Interface:
    bLength             :9
    bDescriptorType     :0x04
    bInterfaceNumber    :0x00
    bAlternateSetting   :0x00
    bNumEndpoints       :0
    bInterfaceClass     :0xFF (Vendor Specific Class)
    bInterfaceSubClass  :0xFF (Vendor Specific Subclass)
    bInterfaceProtocol  :0xFF (Vendor Specific Protocol)
    iInterface          :0
 !End Interface
 -Interface:
    bLength             :9
    bDescriptorType     :0x04
    bInterfaceNumber    :0x00
    bAlternateSetting   :0x01
    bNumEndpoints       :6
    bInterfaceClass     :0xFF (Vendor Specific Class)
    bInterfaceSubClass  :0xFF (Vendor Specific Subclass)
    bInterfaceProtocol  :0xFF (Vendor Specific Protocol)
    iInterface          :0
   -Endpoint:
      bLength             :7
      bDescriptorType     :0x05
      bEndpointAddress    :0x81
      bmAttributes        :0x03 (Interrupt)
      wMaxPacketSize      :64
      bInterval           :0x01
   !End Endpoint
   -Endpoint:
      bLength             :7
      bDescriptorType     :0x05
      bEndpointAddress    :0x02
      bmAttributes        :0x03 (Interrupt)
      wMaxPacketSize      :64
      bInterval           :0x01
   !End Endpoint
   -Endpoint:
      bLength             :7
      bDescriptorType     :0x05
      bEndpointAddress    :0x83
      bmAttributes        :0x02 (Bulk)
      wMaxPacketSize      :512
      bInterval           :0x00
   !End Endpoint
   -Endpoint:
      bLength             :7
      bDescriptorType     :0x05
      bEndpointAddress    :0x04
      bmAttributes        :0x02 (Bulk)
      wMaxPacketSize      :512
      bInterval           :0x00
   !End Endpoint
   -Endpoint:
      bLength             :7
      bDescriptorType     :0x05
      bEndpointAddress    :0x85
      bmAttributes        :0x01 (Isochronous, No Synchonization, Data Endpoint)
      wMaxPacketSize      :128
      bInterval           :0x01
   !End Endpoint
   -Endpoint:
      bLength             :7
      bDescriptorType     :0x05
      bEndpointAddress    :0x06
      bmAttributes        :0x01 (Isochronous, No Synchonization, Data Endpoint)
      wMaxPacketSize      :128
      bInterval           :0x01
   !End Endpoint
 !End Interface
!End Configuration
Attachment (Write.Isochronous.rar): application/rar, 10 KiB
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Libusb-win32-devel mailing list
Libusb-win32-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

Gmane