Page
35
of
70
Copyright © Access-IS 2016
6.2 MIFARE cards
When the reader detects NFC media, the application gets the ATR of the media. Since there is no
ATR present for MIFARE media, the NFC module constructs an ATR from the fixed elements that
identify the card.
The ATR for MIFARE media is 20 bytes long. It has fixed values, with the exception of the 15
th
byte,
which indicates the type of MIFARE media. Table 14 shows the ATRs for different types of MIFARE
media.
Table 14. MIFARE media ATR bytes
MIFARE media type
ATR bytes
1K Classic
3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00
03
00 00 00 00 68
4K Classic
3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00
04
00 00 00 00 6F
Ultralight
3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00
05
00 00 00 00 6E
Note that the value of the 15
th
byte indicates the type of MIFARE media.
The application software can look for these specific ATR bytes to detect MIFARE-type media. Once
it detects a MIFARE-type medium, the application can then use the MIFARE commands to
communicate with it.
Refer to
MIFARE media commands and responses
on page 36 for details of the MIFARE media
commands and responses that you can use.
6.3 Contactless microprocessor smartcards
The NFC module detects contactless microprocessor smartcards such as Java cards, ACOS,
Desfire, SmartMX cards and most e-Passports. These media have an ATR, which the NFC module
retrieves. The host application can send APDU commands to these media using the Windows
Smartcard API.
Note:
The format of the command and response APDUs depend on the type of media. Refer to the
media’s user manual for the command and response formats.
