-
Notifications
You must be signed in to change notification settings - Fork 8
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
pcsc_scan detection for SPI connected PN532 #6
Comments
I am using this with PN532 with SPI connected to Linux board GPIOs. NFC is working. How to integrate and do ifdnfc-activate for the same to integrate with pcsc ? |
EDIT: Having the same trouble here. Only difference is I connected it using i2c (should be no real significant difference i suspect). And I would like to apologise in advance if I attach many redundant info here. I'm fairly new to this thing. Edit: I forgot, my architecture is arm64 in case it helps with something. Here is my output:
nfc-scan-device uses libnfc 1.7.1
1 NFC device(s) found:
- pn532_i2c:/dev/i2c-1:
pn532_i2c:/dev/i2c-1
chip: PN532 v1.6
initator mode modulations: ISO/IEC 14443A (106 kbps), FeliCa (424 kbps, 212 kbps), ISO/IEC 14443-4B (106 kbps), Innovision Jewel (106 kbps), D.E.P. (424 kbps, 212 kbps, 106 kbps)
target mode modulations: ISO/IEC 14443A (106 kbps), FeliCa (424 kbps, 212 kbps), D.E.P. (424 kbps, 212 kbps, 106 kbps)
nfc-list uses libnfc 1.7.1
NFC device: pn532_i2c:/dev/i2c-1 opened
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 04
* UID size: single
* bit frame anticollision supported
UID (NFCID1): b8 6e 5d d9
SAK (SEL_RES): 08
* Not compliant with ISO/IEC 14443-4
* Not compliant with ISO/IEC 18092
Fingerprinting based on MIFARE type Identification Procedure:
* MIFARE Classic 1K
* MIFARE Plus (4 Byte UID or 4 Byte RID) 2K, Security level 1
* SmartMX with MIFARE 1K emulation
Other possible matches based on ATQA & SAK values:
0 Felica (212 kbps) passive target(s) found.
0 Felica (424 kbps) passive target(s) found.
0 ISO14443B passive target(s) found.
0 ISO14443B' passive target(s) found.
0 ISO14443B-2 ST SRx passive target(s) found.
0 ISO14443B-2 ASK CTx passive target(s) found.
0 Jewel passive target(s) found.
Could not find a reader named: IFD-NFC
Cannot find a smart card reader. I also can't help but notice a config file for a reader at /etc/reader.conf.d/ so i made one
and finally a config for the reader itself:
|
@ronie19 I've got it working. I changed the config for the /etc/reader.conf.d/libifdnfc to this value:
AND THEN i started the
|
Awesome. Can you check once for SPI and let me know. I am out of my home lab till next month. |
Unfortunately, I can't. I've broken my SPI connection on the PN532 module. But now I've finally understood how all of this works. The good news is that it is fairly straighforward to do.
The most important thing here is the
Do note that the name doesn't need to be
And here's the log from the daemon:
|
No luck yet. I changed the /etc/nfc/libnfc.conf config file to: and also /etc/reader.conf.d/libifdnfc to FRIENDLYNAME "IFD-NFC" though it shows up in pcsc_scan as Reader 2 but doesn't read rfid card while running pcsc_scan while ifdnfc-activate shows : Any leads ? Some ideas pls |
Hmmm, try to set the log level to debug, then post the output of the |
pi@raspberrypi:~ $ sudo ifdnfc-activate |
this also happened now:
|
Detecting in pcsc_scan but not providing any ATR even with card near the pn532 reader Tue Jan 19 15:42:00 2021 Tue Jan 19 15:42:00 2021 Tue Jan 19 15:42:01 2021 |
Hmmm, insufficient buffer implies that the program (in this case, the |
even for my i2c connection on raspberry pi, it says insufficient buffer. |
this happened: pi@raspberrypi:~ $ pcsc_scan Sat Jan 23 15:48:26 2021 ATR: 3B 80 80 01 01
Possibly identified card (using /home/pi/.cache/smartcard_list.txt): Your card is not present in the database. |
Dumb question: When I try |
I have connected a pn532 board via SPI port. I have successfully installed libnfc and it is able to get detected by nfc-list and nfc-poll.
What do I need to do so that it gets detected by pcsc_scan as well????
The text was updated successfully, but these errors were encountered: