Hey Phil, I really appreciate all your help.
I know this is a separate issue unrelated to the original scope of the original topic of this thread (Ultralight C changing default 3DES key), so apologies for continuing this conversation in here.
I uninstalled libfreefare and libnfc and reinstalled both using the latest SVN revisions.
When I reinstalled libnfc, it was unable to open the NFC reader I'm using (ACR122 ) when I executed the bundled nfc-list, located in the utils directory of libnfc. When looking for a solution fot this, I've came across the issue 208 (http://code.google.com/p/libnfc/issues/ … amp;id=208), which is related to the acr122_usb library, which is a new experimental driver that libnfc is using by default for Touchatag/ACR122U devices.
In order to troubleshoot the issue of my ACR122 reader not been found, I followed the advise in the above mentioned ticket, and recompiled libnfc using support for acr122_pcsc driver (./configure --with-drivers=acr122_pcsc && make clean all). After this, I was able to successfully get the nfc-list example running and properly recognizing the reader device:
ACS ACR122U PICC Interface 00 00 / ACR122U207 opened
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 44
UID (NFCID1): 04 a3 23 99 10 28 80
SAK (SEL_RES): 00
However, when I compile and run a libfreefare example (mifare-ultralight-info.c) that tries to open the reader, I get the same error message I was getting previously, when running the nfc-list example with the new ACR122 driver:
Can this issue be related to the new ACR122 driver that libnfc is using by default?
Many thanks as always