-
-
Notifications
You must be signed in to change notification settings - Fork 79
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
HID OMNIKEY 5023 ; ccid_usb.c:888:WriteUSB() write failed (1/14): LIBUSB_ERROR_TIMEOUT #101
Comments
In log_2.txt I only find a ACS ACR1281U reader. No OMNIKEY 5023. I don't understand why you generate so many configurations. In acshk/acsccid#32 @godfreychung already said that your card is not a Mifare card. |
This is the new log for log_2(1).txt. I take "try and error' approach with different configuration since im not very familiar with Human Interface Device integration. Thats why in my 1st scenario I build the package from the package manager . Which is very straight forward and ease for me. Really hoping the PC/SC Workgroup will meet the mission target for standardization . Reason for having ACS driver is, im using ACR1281-u completely for my application at initial. Then I encounter problem mentioned in acshk/acsccid#32 ; highlighting error reading Reason for having OMNIKEY reader is because this the best available reader I can get from my area. Which was told to me that can resolve my issue with ACS reader by the merchant. So my alternate plan is, use ACS reader for extracting securekey from SAM. Pass the extracted key to OMNIKEY Key for accessing the smart card and complete my application purpose. Now, im having an issue with the reader driver for connecting to OMNIKEY. I hope my clarification has been helpful. |
From
The reader does not respond to driver's commands. This is not normal. I can't do much. You can try to contact HID Global OMNIKEY support. Maybe they have a reader firmware update. |
Yes , I think you should move it. I will contact HID team to get support accordingly from them. Thanks, very much appriciated. |
The reader is now in the "Unsupported or partly supported CCID readers" list |
Hello @LudovicRousseau , They manage to get the HID working with the CCID release The HID environment setup as below (screenshot from email reply) ; I did follow the same environment setup on Linux armv7 x64 but FAILED with new error
Included log for reference . It seem to me that the reader not respond to driver's command like you mentioned before . Any comment from you ? |
From your log you are using the CCID driver version 1.4.30, not 1.4.34 or the latest 1.5.0. I also see that a driver is installed in
Maybe your reader uses a firmware different than the one used by HID support team I suggest to test on an x86 platform (standard PC with Ubuntu 22.04 for example) to eliminate possible issues with your ARM platform. |
Hey @LudovicRousseau , And the driver seem to be working for HID OMNIKEY 5023 PC/SC Daemon ; in this Log im using ccid release pcsc-scan tools ;
|
Your log_pcscd.txt does not contain the low level logs. But since you are able to get the card ATR I guess everything works fine. Now you have to debug you USB stack on the beaglebone. I moved the reader back in the "Should work" list. |
Yes , i have to debug my USB in the beaglebone. |
Dear Ludovic,
First of all, I would to express deepest gratitude to the whole team and you for this PCSC , CCID, & Pyscard project.
The project has been very much helpful for those required such as myself 😃
Regarding the above subject, im requesting support for the issue im facing .
The application process
Originally ;
Process flow
Problem
Finding
Alternative ;
using [ACS ACR1281-u reader] & [HID OMNIKEY 5023] with Pyscard API for my application to read write smart card [MIFARE+ 1k ,4k & DESFIRE EV2(contain MIFARE 4k configuration & data)].
Problem
Finding
I have tried in various configuration scenario.
Below is the required information ;
Scenario 1
Driver and middleware were built from Linux apt Package manager.
Version
libccid v1.4.30-1
&libacsccid1 v1.1.6-1
package_info.txtlibpcsclite1:armhf v1.8.24-1
pcscd_ver.txtlibusb-1.0-0:armhf v2:1.0.22-2
1.9.9-2build1-armhf
Platform
Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux
os_info.txtlibpcsclite1:armhf : 1.8.24-1
MIFARE+ 4k SL1
LOG
Scenario 2
Driver and middleware built from current release repository : pcsc-lite-1.9.9, ccid-1.5.0 & libusb v1.0.26
Version
libccid : 1.5.0
ccid150.txtPcscd ; V 1.9.9
pcscd_ver_1.txtPlatform
Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux
[os_info.txt]pcsc-lite v 1.9.9
MIFARE+ 4k SL1
LOG
Scenario 3
Driver and middleware built from current release repository : pcsc-lite-1.9.9, ccid-1.5.0 & libusb v1.0.26
Version
libccid : 1.5.0
[ccid150.txt]Pcscd ; V 1.9.9
[ pcscd_ver_1.txt]Platform
Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux
[os_info.txt]pcsc-lite v 1.9.9
MIFARE+ 4k SL1
LOG
Attachment log_2.txt
Nothing significant , since ccid is build with default configuration
--enable-libusb
The text was updated successfully, but these errors were encountered: