Document Version 1.00
Last revised on
Page 31 of 87
2020-04-10
Reference Manual for uTrust 3720F and uTrust 3721F Readers
6.
Commands description
6.1.
Generic APDU
6.1.1.
Working with DESFire and MIFARE Plus tokens
To work with DESFire EV1 and MIFARE Plus tokens, please refer to the according application notes
[AN337] and [AN338], respectively.
Please note that, since these application notes contain information available only under NDA with NXP,
you’d need to sign an NDA with NXP to be allowed to receive them.
6.1.2.
PAPDU_GET_UID
GET UID will retrieve the UID or SNR or PUPI of the user token. This command can be used for all
supported technologies.
Command APDU:
CLA
INS
P1
P2
Lc
Data in
Le
0xFF
0xCA
0x00/0x01 0x00
-
-
XX
Response APDU:
Data
Status Word
Requested bytes of UID
SW1, SW2
Setting P1=0x00 and Le = 0x00 can be used to request the full UID or PUPI is sent back. For ISO14443A
single 4 bytes or double 7 bytes or triple 10 bytes shall be returned. For ISO14443B 4 bytes PUPI shall
be returned. For ISO15693 tags 8 bytes for ISO15693 tags. For LF tags, the raw data blocks shall be
returned.
Setting P1=0x01 and Le=0x00 is specific to LF tags. When P1=0x01 reader interprets the raw data from
card, matches it against one of the pre-defined formats and returns the processed data. Processed
data would be of the form “FAC <space> XX <NUL> YYYYYY <NUL> CSN <space>” where <space> is
ASCII space character (0x20) and <NUL> is ASCII NUL character (0x00).
For example, “FAC 27 40037 CSN” would be returned as
0x46 0x41 0x43 0x20 0x32 0x37 0x00 0x34 0x30 0x30 0x33 0x37 0x00 0x43 0x53 0x4E 0x20 0x90 0x00
Setting P1=0x01 for HF cards would return status word 0x6A81 indicating that this function is not
supported.
