acr122_usb fails on touchatag

[GoogleCodeExporter]

nfc-list uses libnfc 1.6.0-rc1 (r1446)
trace   libnfc.general  0 device(s) found using pn53x_usb driver
trace   libnfc.driver.acr122_usb    device found: Bus 001 Device 022
trace   libnfc.general  1 device(s) found using acr122_usb driver
info    libnfc.driver.acr122s   Serial auto-probing have been disabled at compile 
time. Skipping autoprobe.
info    libnfc.driver.arygon    Serial auto-probing have been disabled at compile 
time. Skipping autoprobe.
trace   libnfc.driver.acr122_usb    3 element(s) have been decoded from 
"acr122_usb:001:022"
debug   libnfc.driver.acr122_usb    ACR122 PICC Operating Parameters
trace   libnfc.driver.acr122_usb    TX: 6b  05  00  00  00  00  00  00  00  00  ff  
00  51  00  00  
trace   libnfc.driver.acr122_usb    RX: 83  00  00  00  00  00  00  41  05  00  
trace   libnfc.chip.pn53x   GetFirmwareVersion
trace   libnfc.driver.acr122_usb    TX: 6b  07  00  00  00  00  00  00  00  00  ff  
00  00  00  02  d4  02  
trace   libnfc.driver.acr122_usb    RX: 83  00  00  00  00  00  00  41  07  00  
error   libnfc.driver.acr122_usb    Too small reply
trace   libnfc.general  Unable to open "acr122_usb:001:022".

Original issue reported on code.google.com by darksk...@gmail.com on 18 Jul 2012 at 11:09

[GoogleCodeExporter]

I have the same problem and I'm going crazy to fix ...
 Can anyone tell the solution??? THANK YOU

root@bt:~# nfc-list
nfc-list uses libnfc 1.6.0-rc1 (r1447)
nfc-list: ERROR: Unable to open NFC device: acr122_usb:004:002

Original comment by albertit...@gmail.com on 22 Aug 2012 at 6:43

[GoogleCodeExporter]

I think this is the same problem as in bug #202 already solved in SVN.

Original comment by ludovic....@gmail.com on 22 Aug 2012 at 8:08

[GoogleCodeExporter]

Same problem here with driver acr122_usb and touchatag reader...

greg@pc-bureau:~/libnfc-read-only$ utils/nfc-list
/home/greg/libnfc-read-only/utils/.libs/lt-nfc-list uses libnfc 1.6.0-rc1 
(r1447)
trace   libnfc.driver.acr122_usb    device found: Bus 005 Device 002
trace   libnfc.general  1 device(s) found using acr122_usb driver
trace   libnfc.driver.acr122_usb    3 element(s) have been decoded from 
"acr122_usb:005:002"
debug   libnfc.driver.acr122_usb    ACR122 PICC Operating Parameters
trace   libnfc.driver.acr122_usb    TX: 6b  05  00  00  00  00  00  00  00  00  ff  
00  51  00  00  
trace   libnfc.driver.acr122_usb    RX: 83  00  00  00  00  00  00  41  05  00  
trace   libnfc.chip.pn53x   GetFirmwareVersion
trace   libnfc.driver.acr122_usb    TX: 6b  07  00  00  00  00  00  00  00  00  ff  
00  00  00  02  d4  02  
trace   libnfc.driver.acr122_usb    RX: 83  00  00  00  00  00  00  41  07  00  
error   libnfc.driver.acr122_usb    Too small reply
trace   libnfc.general  Unable to open "acr122_usb:005:002".
lt-nfc-list: ERROR nfc-list.c:130
lt-nfc-list:     Unable to open NFC device: acr122_usb:005:002

Original comment by gregoire...@gmail.com on 9 Sep 2012 at 12:04

[GoogleCodeExporter]

Ok I looked in the code and found that Touchatag is not really supported yet.
I personnaly patched the acr122_usb.c file to support my touchatag.

But my patch breaks the compatibility with previously supported devices

Maybe something more pretty can be done...

Original comment by gregoire...@gmail.com on 12 Sep 2012 at 9:55

Attachments:

• libnfc_trunk.patch

[GoogleCodeExporter]

The init_frame that I send in acr122_usb_init seems to fix the problem seen 
here :
http://www.libnfc.org/community/topic/687/acr122u-new-usb-driver/

Original comment by gregoire...@gmail.com on 12 Sep 2012 at 10:01

[GoogleCodeExporter]

This issue was closed by revision r1460.

Original comment by romu...@libnfc.org on 3 Oct 2012 at 4:21

• Changed state: Fixed