-
-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ccid_usb.c:888:ReadUSB() read failed (1/6): -7 LIBUSB_ERROR_TIMEOUT #66
Comments
Please generate a new log as documented at https://ccid.apdu.fr/#support |
I've updated the issue. Here is also the complete log :
|
It looks like your reader firmware is bogus.
The 7th byte is bSeq "Sequence number for command.". The number in the response should be the same as in the command. So the sequence should be:
After that you have:
Which indicates the same problem. Report the problem to Identiv support. |
Thanks a lot for the quick answer, I will report that to Identiv... |
@nicolasbadia can you share where you purchased your reader? Was it purchased directly? I am aware of counterfeit issues with other readers. Do you suspect this is the case, or is it genuine bug? |
@jaredvacanti yes it was a real reader. I believe Identiv submitted a patch for this. |
Here is an issue related to #29 which is still causing me some troubles...
I had initially the issue only on Raspberry Pi, but it now also happens on Ubuntu 18 (with multiple NUC).
I can manage to have PCSC working if the reader is connected and if I restart
pcscd
. But after a reboot or if I unplug and replug it, it does not work anymore. Here are some log.When I unplug it the first time after a pcscd restart:
When I plug back:
When I unplug it again:
04982847 [1965028336] hotplug_libudev.c:645:HPEstablishUSBNotifications() USB Device removed
The reader is a still an "Identiv uTrust 3700 F CL Reader".
Here are the related software versions:
Any idea of what is going wrong ?
Should I contact Identiv ? I'm asking because we recently had a chance to test a reader from another vendor, and it works perfectly...
The text was updated successfully, but these errors were encountered: