Hi Eric,
On 2013.01.31 18:45, Eric Lundby wrote:
> It seems that the error I was encountering is related to issue #78
> ("[winusbx_claim_interface] failed to auto-claim interface 0"). When I
> manually claim interface 0 before claiming interface 1 I no longer
> receive an error.
Yeah, as far as I could test, it looks like we have an issue with
composite devices when claiming an interface that is not 0, and 0 is not
assigned to anything we recognize (at least when using the libusb-win32
driver).
> Using USBlyzer I did notice that when using Microchips driver, there
> are several Control Transfers sent to 'Set Line Coding' and 'Get Line
> Coding' before my messages are sent or received. Does anyone know if
> this could be why my basic communication could be failing with libusb
> (because I'm not setting line coding)?
I'm not exactly familiar with CDC, but maybe the tips from [1], for a
problem that look similar to yours, can help.
Regards,
/Pete
[1]
http://e2e.ti.com/support/microcontrollers/stellaris_arm_cortex-m3_microcontroller/f/471/t/106729.aspx
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
