• erore
  • New member
  • Offline
  • Registered: 2012-02-14
  • Posts: 1

Topic: no device found-ACR128U-deb_squeeze

The reader is ACR128U on debian squeeze. I compiled with --enable-debug as I am receiving No NFC device found. from nfc-list.

Output of nfc-list:


root:examples$ ./nfc-list
/home/libnfc-1.4.2/examples/.libs/lt-nfc-list use libnfc 1.4.2 (r891)
lt-nfc-list: DBG acr122.c:192
lt-nfc-list:     PCSC device [ACS ACR128U 00 00] is not NFC capable or not supported by libnfc.
lt-nfc-list: DBG acr122.c:192
lt-nfc-list:     PCSC device [ACS ACR128U 00 01] is not NFC capable or not supported by libnfc.
lt-nfc-list: DBG acr122.c:192
lt-nfc-list:     PCSC device [ACS ACR128U 00 02] is not NFC capable or not supported by libnfc.
lt-nfc-list: DBG arygon.c:116
lt-nfc-list:     Serial auto-probing have been disabled at compile time. Skipping autoprobe.
No NFC device found.
root:examples$ No NFC device found.

The driver is installed, pcsc_scan:

root:examples$ pcsc_scan
PC/SC device scanner
V 1.4.16 (c) 2001-2009, Ludovic Rousseau <ludovic.rousseau@free.fr>
Compiled with PC/SC lite version: 1.5.5
Scanning present readers...
0: ACS ACR128U 00 00
1: ACS ACR128U 00 01
2: ACS ACR128U 00 02

Tue Feb 14 12:51:11 2012
Reader 0: ACS ACR128U 00 00
  Card state: Card removed,

Tue Feb 14 12:51:11 2012
Reader 1: ACS ACR128U 00 01
  Card state: Card removed,

Tue Feb 14 12:51:11 2012
Reader 2: ACS ACR128U 00 02
  Card state: Card inserted, Unresponsive card,

Any idea why nfc-list detects no device?

  • rconty
  • Administrator
  • Offline
  • Registered: 2009-04-22
  • Posts: 773

Re: no device found-ACR128U-deb_squeeze

erore wrote:

The reader is ACR128U on debian squeeze.

Any idea why nfc-list detects no device?

Yes, of course : ACR128U is not supported by libnfc.

BTW, it may be more easy than it seems : try to add it at libnfc/acr122.c supported models and see what happend.

Romuald Conty
  • Registered: 2013-04-08
  • Posts: 1

Re: no device found-ACR128U-deb_squeeze

How can ACR128 support can be added to "acr122_pcsc" driver...
pcscd releases context after received CMD_GET_READERS_STATE command from libnfc enabled client.
Can you point me to the right direction...

--
00000008 winscard_svc.c:736:MSGSignalClient() SIGNAL rv=0x0 for client 10
00000110 winscard_svc.c:317:ContextThread() Received command: CMD_GET_READERS_STATE from client 10
00000656 winscard_svc.c:317:ContextThread() Received command: CMD_GET_READERS_STATE from client 10
00000107 winscard_svc.c:317:ContextThread() Received command: CMD_WAIT_READER_STATE_CHANGE from client 10
24202119 winscard_svc.c:309:ContextThread() Client die: 10
00000212 winscard.c:204:SCardReleaseContext() Releasing Context: 0x765672CF
00000140 winscard_svc.c:928:MSGCleanupClient() Thread is stopping: dwClientID=10, threadContext @0x64c580
00000160 winscard_svc.c:934:MSGCleanupClient() Freeing SCONTEXT @0x64c580
--

nfc-list output:
--
info    libnfc.config   Unable to open file: /usr/etc/nfc/libnfc.conf
debug   libnfc.config   Unable to open directory: /usr/etc/nfc/devices.d
unknown libnfc.general  log_level is set to 3
debug   libnfc.general  allow_autoscan is set to true
debug   libnfc.general  allow_intrusive_scan is set to false
debug   libnfc.general  0 device(s) defined by user
nfc-list uses libnfc libnfc-1.7.0-rc7-1-g29c7ef1
debug   libnfc.driver.acr122_pcsc       PCSC device [ACS ACR128U 00 00] is not NFC capable or not supported by libnfc.
debug   libnfc.driver.acr122_pcsc       PCSC device [ACS ACR128U 00 01] is not NFC capable or not supported by libnfc.
debug   libnfc.driver.acr122_pcsc       PCSC device [ACS ACR128U 00 02] is not NFC capable or not supported by libnfc.
debug   libnfc.general  0 device(s) found using acr122_pcsc driver
No NFC device found.
--

  • yobibe
  • Administrator
  • Offline
  • Registered: 2011-04-08
  • Posts: 102

Re: no device found-ACR128U-deb_squeeze

ACR128U is based on NXP RC531 reader chip which doesn't have anything in common with the PN53x family currently supported by libnfc.
So adding (partial, no NFC, no card emulation) support for this reader is not straightforward.
Contributions are welcome.

Phil

yobibe's Website