but on Windows, it does not work with nEndpoint = 0x81


-----Original Message-----
From: Wim De Kimpe [mailto:wim.deki...@medecbenelux.be] 
Sent: vrijdag 15 februari 2013 15:15
To: libusbx-devel@lists.sourceforge.net
Subject: [SPAM] - Re: [Libusbx-devel] opening generic device EP in bulk 
transfer - difference between Linux and Windows - Email found in subject - 
Email found in subject

tried 0x81, same result.

Wim


-----Original Message-----
From: Wim De Kimpe
Sent: vrijdag 15 februari 2013 15:14
To: libusbx-devel@lists.sourceforge.net
Subject: RE: [SPAM] - Re: [Libusbx-devel] opening generic device EP in bulk 
transfer - difference between Linux and Windows - Email found in subject

Mmm

good question - but it does!

One difference I forgot to mention: when using it under windows, the software 
needs to detach from the kernel, hence attached = 1.
Does this make a difference.

Going to try it now with 0x81.
could you please tell me why nEndpoint needs to be 0x81 rather than 0x01, and 
on EP2 this needs to be 0x02?

Best regards

Wim


-----Original Message-----
From: Xiaofan Chen [mailto:xiaof...@gmail.com]
Sent: vrijdag 15 februari 2013 15:10
To: libusbx-devel@lists.sourceforge.net
Subject: [SPAM] - Re: [Libusbx-devel] opening generic device EP in bulk 
transfer - difference between Linux and Windows - Email found in subject

On Fri, Feb 15, 2013 at 9:59 PM, Wim De Kimpe <wim.deki...@medecbenelux.be> 
wrote:
> I have a custom USB device that is using bulk transfer on 2 endpoints,
> EP1 is in, EP2 is out.
>
>             int nEndpoint = 0x01;
>             int nTimeout = 500; //in milliseconds
>             int BytesWritten = 0;
>             unsigned char OutputPacketBuffer[64];
>             OutputPacketBuffer[0] = SET_LEDS;
>             OutputPacketBuffer[1] = 0x02;
>             libusb_interrupt_transfer( handle, nEndpoint, 
> OutputPacketBuffer, 2, &BytesWritten, nTimeout );

Hmm, if you want to use EP1 for Interrupt IN transfer, the nEndpoint should be 
0x81. If you want to use EP2 for Interrrupt OUT transfer, then nEndpoint should 
be 0x02. How can your program work under Windows?


--
Xiaofan

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 and get the 
hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 and get the 
hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

Reply via email to