lsnfc tags detection weirdness

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Put a MIFARE Classic 1k and a MIFARE Classic 4k an NFC device (tested with a 
touchatag and a snapper);
2. Run lsnfc
3. Run the mifare-claissic-format example in libfreefare.

What is the expected output? What do you see instead?

lsnfc should list both tags with relevant information.  mifare-classic-format 
should ask the user to format both tags.

Instead, lsnfc does not display information about one tag:
% lsnfc
device = ACS ACR 38U-CCID 01 00 / ACR122U102 - PN532 v1.4 (0x07)
  ISO14443A: Unknown ISO14443A tag type: ATQA (SENS_RES): 0000, UID (NFCID1): 0ab4139a, SAK (SEL_RES): 08
  ISO14443A: NXP MIFARE Classic 4K (UID=0cbc1547)
2 tag(s) have been found.
device = Philips / USB TAMA - PN531 v3.4
2 tag(s) have been found.

However, mifare-classic-format can access both tags without any problem:
Found Mifare Classic 4k with UID 0cbc1547.  Format [yN] y
Formatting 40 blocks....10....20....30....40 done.
Found Mifare Classic 1k with UID 0ab4139a.  Format [yN] y
Formatting 16 blocks....10... done.

If each card is on it's own device, the problem does not occur.

Original issue reported on code.google.com by romain.t...@gmail.com on 27 Jun 2010 at 6:50

[GoogleCodeExporter]

This problem is due to ATQA collision and the lsnfc's way to detect tags. As 
libfreefare, lsnfc should have a new way to detect the card type of ISO14443-A 
tags.

Original comment by romu...@libnfc.org on 12 Aug 2010 at 1:01

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by romu...@libnfc.org on 12 Aug 2010 at 1:08

• Added labels: Component-nfcutils

[GoogleCodeExporter]

This is now fixed: lsnfc doesn't rely on ATQA to identify targets.

Original comment by romu...@libnfc.org on 18 Aug 2010 at 3:33

• Changed state: Fixed