Wireshark-bugs: [Wireshark-bugs] [Bug 9333] USB: NFC: Final work on PN532, add PN532_HCI dissect

Date: Mon, 28 Oct 2013 12:52:42 +0000

Comment # 21 on bug 9333 from
(In reply to comment #20)
> Spec-closeness. In PN532 I see only "ATQB". Do you know specification that
> describe next level dissection? (new dissector?)

Aah, I reverse-engineered them from the output of "nfc-list" (included in
LibNFC), but http://wg8.de/wg8n1496_17n3613_Ballot_FCD14443-3.pdf has a small
amount of info (although the PN532 doesn't expose everything according to that
spec).

For a Maxim MAX66040E-000AA+, things look like:

1 ISO14443B passive target(s) found:
               PUPI: a2  a6  02  00  
   Application Data: 30  00  2b  e0  
      Protocol Info: 77  21  71  
* Bit Rate Capability:
 * PICC to PCD, 1etu=64/fc, bitrate 212 kbits/s supported
 * PICC to PCD, 1etu=32/fc, bitrate 424 kbits/s supported
 * PICC to PCD, 1etu=16/fc, bitrate 847 kbits/s supported
 * PCD to PICC, 1etu=64/fc, bitrate 212 kbits/s supported
 * PCD to PICC, 1etu=32/fc, bitrate 424 kbits/s supported
 * PCD to PICC, 1etu=16/fc, bitrate 847 kbits/s supported
* Maximum frame sizes: 32 bytes
* Protocol types supported: ISO/IEC 14443-4
* Frame Waiting Time: 38.66 ms
* Frame options supported: NAD 

For a two different capacities of Atmel CryptoRF:

1 ISO14443B passive target(s) found:
ISO/IEC 14443-4B (106 kbps) target:
PUPI: ff ff ff ff
Application Data: ff ff ff 22
Protocol Info: 00 10 51
* Bit Rate Capability:
* PICC supports only 106 kbits/s in both directions
* Maximum frame sizes: 24 bytes
* Frame Waiting Time: 9.666 ms
* Frame options supported: NAD 

1 ISO14443B passive target(s) found:
ISO/IEC 14443-4B (106 kbps) target:
PUPI: ff ff ff ff
Application Data: ff ff ff 33
Protocol Info: 00 10 51
* Bit Rate Capability:
* PICC supports only 106 kbits/s in both directions
* Maximum frame sizes: 24 bytes
* Frame Waiting Time: 9.666 ms
* Frame options supported: NAD 

Unfortunately, I don't have any more types of ISO 14443-B tag/card; and the USB
cable on my reader is dodgy - but there are examples from these in some of the
trace files that I've uploaded.


You are receiving this mail because:
  • You are watching all bug changes.