Hi all!
It looks like that the problem was caused by that specific embedded
Linux I was using.
On other Linux and Windows OS everything seems to work fine.
Many thanks to Matthias Bolte for his help and advice.
Regards,
Anguel
--
Hi Matthias,
Thank you for the reply.
Am 23.12.2013 12:15, schrieb Matthias Bolte:
>
> I think there could be two reasons for this problem:
>
> 1) There is a bug in libusbx, your specific usage pattern triggers it
> and in the end your transfer is lost. Are you using the latest
> release/git vers
2013/12/22 Anguel Stankov :
> Hi Matthias,
>
> Thank you very much for your reply and sorry for my delayed answer.
>
> So once again to sum up, I have the following scheme:
> (a) On EP1 I have short periodic status transfers from device to host,
> e.g. every 250 ms. These can be "bulk in" or "inter
Hi Matthias,
Thank you very much for your reply and sorry for my delayed answer.
So once again to sum up, I have the following scheme:
(a) On EP1 I have short periodic status transfers from device to host,
e.g. every 250 ms. These can be "bulk in" or "interrupt in" type.
(b) I have large data tr
2013/12/20 Anguel Stankov :
> Hi!
>
> I have also posted my question in the libusb list but got no reply so far,
> so I try my luck here. I hope that there are more experts reading here. My
> question is whether submitting multiple transfers in parallel and handling
> the results (by checking in th
Hi!
I have also posted my question in the libusb list but got no reply so far, so I try my luck here. I hope that there are more experts reading here. My question is whether submitting multiple transfers in parallel and handling the results (by checking in the callback function which of the tr
