Re: [Libusb-win32-devel] Bulk USB transfers works with USB3.0 ports and not with USB2.0

[Aymen J. <jeb...@gm...>]

Thanks for your help Xiofan,

The problem is due to the fact that the isolator supports only Full speed
USB transactions.
But the SAM3U is high speed. The SAM3U can switch to full speed.

Now the problem I think is with the SAM3U firmware and USB descriptor
configuration.
Using an USB protocol analyser, when plugging in the device, I see this
error:

URB *Select Configuration *failed

*Device Object *

USBPDO-7

*Driver Object *

usbhub

*URB Function *

URB_FUNCTION_SELECT_CONFIGURATION

*URB Status *

USBD_STATUS_INVALID_PARAMETER

*Configuration *

1
The problem was with the Full speed configuration of the USB descriptor.
I was using 512 as a maximum bulk transfer size.
Problem disappear when setting this value to 64.

Thanks for your support,
Aymen



2014-09-30 4:58 GMT+02:00 Xiaofan Chen <xia...@gm...>:

> On Tue, Sep 30, 2014 at 10:56 AM, Xiaofan Chen <xia...@gm...> wrote:
> > On Mon, Sep 29, 2014 at 10:29 PM, Aymen JEBALI <jeb...@gm...>
> wrote:
> >> 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.
> >
> > Is your device recognized by Windows and is configured properly
> > under Windows? Configuration 0 means that the device is not
> > configured. You should try to call usb_set_configuration(1) before
> > calling usb_claim_interface(0) to see if that helps. If not, most likely
> > it is a problem with the USB isolator or your device.
> >
> > You shou
>
> Send too fast. You should also make sure that without the isolator your
> device work properly for both USB 3.0 ports and USB 2.0 ports for
> different PCs, then in that case, you can probably try to contact the
> USB isolator cable vendor for help.
>
>
>
> --
> Xiaofan
>
>
> ------------------------------------------------------------------------------
> 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
> Lib...@li...
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel
>



-- 
Aymen Jebali
Embedded Systems Engineer
jeb...@gm...