Gemalto Prox–DU Guide

PC/SC Guide
Prox–DU & Prox–SU
www.gemalto.com
DOC119811A Public Use Page 96/129
Interfacing with MIFARE
®
DESFire
Cards
The MIFARE
®
DESFire smart card is based on open global standards for both air interface
and cryptographic methods. It is compliant to all 4 levels of ISO14443-A and uses optional
ISO 7816-4 commands.
The native MIFARE
®
DESFire commands are non ISO7816-4 commands.
A proprietary APDU command is implemented into the Prox–DU and Prox–SU reader/writer
in order to send and receive these native commands.
Warning: Note that the EEPROM configuration parameter byte “T=CL card presence check
behavior” should be set to value “01h” to avoid the reader to send a dummy APDU
command during the selection process, because when the MIFARE
®
DESFire smart card
receives an APDU command after the selection process the native commands are no more
available. Refer to the “Reference Manual” document for more information.
The command is formatted as follows:
CLA INS P1 P2 Lc Data In
FFh DEh
00h
00h N
DESFire
Command
1 byte 1 byte 1 byte 1 byte 1 byte N bytes
The response is formatted as follows:
Data Out [SW1 SW2]
M bytes 1 byte 1 byte
Where:
N Length of the Data In field Length of the native command
Data In DESFire native command Refer to the DESFire datasheet
Data Out
DESFire native response
Refer to the DESFire datasheet
[SW1-SW2] Command execution status
Optional field: SW1 SW2 = 90h 00h
is added by the reader when the
DESFire smart card response is
only one byte Status.
Command executed successfully 90h 00h
Others
67h 00h
6Ah 81h
6Bh 00h
Wrong length
Function not supported
Wrong P1 or P2
As an example, to get the version of the DESFire smart card, the following native command
should be send: 60h
The proprietary command to consider is the following:
FFh DEh 00h 00h 01h 60h

Gemalto Prox–DU Specifications

General

Brand	Gemalto
Model	Prox–DU
Category	Card Reader
Language	English