Reference Manual Preliminary
Prox–DU & Prox–SU
www.gemalto.com Release for first samples Do not use for final design
DOC118569A Public Use Page 49/134
The response is formatted as follows:
Data SW1 SW2
NN bytes 1 byte 1 byte
Where:
INF Info type
INF = 00h means: Card serial
number (UID or PUPI) is returned
INF = 01h means: All historical bytes
from the ATS of a ISO14443 A card
without CRC are returned
NN Expected length of the data
NN = 00h means: Return full length
of the UID (e.g. for ISO14443-A
single 4 bytes, double 7 bytes, triple
10 bytes, for ISO14443-B 4 bytes
PUPI)
Data Serial Number
For ISO14443-A smart cards:
UID0-UID1-UID2-UID3 or
UID0-UID1-UID2-UID3-UID4-UID5-
UID6 or
UID0-UID1-UID2-UID3-UID4-UID5-
UID6-UID7-UID8-UID9
For ISO14443-B smart cards:
PUPI3-PUPI2-PUPI1-PUPI0
The UID is exposed as a string of
the expected length. If the expected
length is greater than the actual
length the rest of the string is filled
with zero-value padding bytes.
No cast must be done over the UID
or parts of it. For example, casting
four bytes of the UID to a 32-bit
Integer is illegal.
The order of the bytes within the
string matches the order of bytes
received from the card during the
anti-collision process.
Consequently,
the first byte received will be at
index zero.
The bit order of the string bytes must
be such that the LSB (MSB)
matches with the LSB (MSB) of the
card-defined UID.
Historical bytes of the ATS
Refer to ISO14443-A standard.
For a MIFARE
®
or ISO14443-B card
that command is not supported.
SW1-SW2 Command execution status
Command executed successfully 90h 00h
Others Refer to the error codes table below
Load Keys command
This command is used to load the MIFARE
®
secret keys into the contactless reader/writer.
Up to 160 keys can be loaded to support all the keys pairs needed for the Mifare 4K cards
(2 keys for each sector):
To Next Page
Loading...
