Kevyn-Alexandre Paré wrote:
> I at least need to send 2 bytes to the FPGA to receive back a NAK
> in case of a bad 2 first bytes. In case of a proper trame this will
> send a ACK or data packet.
You can simplify your protocol significantly since USB transfers,
aside from isochronous, are a reliabl
Hi Tim,
Sorry for the delay in the replay was on something else ;)
On 2012-07-24, at 12:41 PM, Tim Roberts wrote:
> Kevyn-Alexandre Paré wrote:
>> Here's the code and output of my test. I'm trying to understand what's going
>> wrong! I mean that I'm expecting the callback function "cb_xfr" from
Kevyn-Alexandre Paré wrote:
> Here's the code and output of my test. I'm trying to understand what's going
> wrong! I mean that I'm expecting the callback function "cb_xfr" from my bulk
> transfer to be called after libusb_submit_transfer is called. I'm
> communicating to a FPGA through a Cypres
>
> I will try to run my test against both git source tree…. Will come back with
> the result.
>
The same result as previously for both git tree (libusb & libusbx).
Any advise?
thx
- KA
--
Live Security Virtual Confe
Hi Peter,
> I think the code looks fine. Try running against libusbx and/or
> libusb git source. (It would be interesting to try both, in this
> case.)
I have tested on both library. The one we have here is
libusb 1.0.9rc3 (f07a4a78533b44d124dfe06cbf42afa7fb267359)
and libusbx 1.0.12
http://so
Kevyn-Alexandre Paré wrote:
> Here's the code and output of my test. I'm trying to understand
> what's going wrong! I mean that I'm expecting the callback function
> "cb_xfr" from my bulk transfer to be called after
> libusb_submit_transfer is called. I'm communicating to a FPGA
> through a Cypress
Hi there,
Here's the code and output of my test. I'm trying to understand what's going
wrong! I mean that I'm expecting the callback function "cb_xfr" from my bulk
transfer to be called after libusb_submit_transfer is called. I'm communicating
to a FPGA through a Cypress USB (FX2) and It's work