MF0ICU2_SDS_32 © NXP B.V. 2009. All rights reserved.
Product short data sheet
PUBLIC
Rev. 3 — 19 May 2009
171432 8 of 15
NXP Semiconductors
MF0ICU2
MIFARE Ultralight C
7.5 Command set
The ATQA and SAK are identical as for MF0ICU1 (see Ref. 7 “MF0ICU1 Functional
specification MIFARE Ultralight”). For information on ISO 14443 card activation, see Ref.
3 “MIFARE ISO/IEC 14443 PICC Selection”.
The MF0ICU2 comprises the following command set:
7.5.1 REQA
The MF0ICU2 accepts the REQA command in Idle state only. The response is the 2-byte
ATQA. REQA and ATQA are implemented fully according to ISO/IEC14443-3.
7.5.2 WUPA
The MF0ICU2 accepts the WUPA command in the Idle and Halt state only. The response
is the 2-byte ATQA. WUPA is implemented fully according to ISO/IEC14443-3.
7.5.3 ANTICOLLISION and SELECT of cascade level 1
The ANTICOLLISION and SELECT commands are based on the same command code.
They differ only in the Parameter byte. This byte is per definition 70h in case of SELECT.
The MF0ICU2 accepts these commands in the Ready1 state only. The response is part 1
of the UID.
7.5.4 ANTICOLLISION and SELECT of cascade level 2
The ANTICOLLISION and SELECT commands are based on the same command code.
They differ only in the parameter byte. This byte is per definition 70h in case of SELECT.
The MF0ICU2 accepts these commands in the Ready2 state only. The response is part 2
of the UID.
7.5.5 READ
The READ command needs the page address as a parameter. Only addresses 00h to
2Bh are decoded. For higher addresses the MF0ICU2 returns a NAK. The MF0ICU2
responds to the READ command by sending 16 bytes starting from the page address
defined in the command (e.g. if ADR is ‘03h‘ pages 03h, 04h, 05h, 06h are returned). If
ADR is ‘2Bh’, the contents of pages 2Bh, 00h, 01h and 02h is returned). This is also
applied by configuring the authentication address.
7.5.6 HALT
The HALT command is used to set already processed MF0ICU2 devices into a different
waiting state (Halt instead of Idle), which allows a simple separation between devices
whose UIDs are already known (as they have already passed the anticollision procedure)
and devices that have not yet been identified by their UIDs.
7.5.7 WRITE
The WRITE command is used to program the lock bytes in page 02h, the OTP bytes in
page 03h or the data bytes in pages 04h to 05h. A WRITE command is performed
page-wise, programming 4 bytes in a page.