Datasheet

NXP Semiconductors

MF0ICU2

MIFARE Ultralight C - Contactless ticket IC

Product data sheet Rev. 3.3 — 30 July 2019

COMPANY PUBLIC 137633 7 / 36

• With the cascade level 1 SELECT command the PCD transits the MF0ICU2 into the

READY2 state where the second part of the UID can be resolved

• With the READ (from page address 00h) command the complete anticollision

mechanism may be skipped and the MF0ICU2 changes directly into the ACTIVE state

Remark: If more than one MF0ICU2 is in the field of the PCD, a read from address 0 will

cause a collision because of the different serial numbers, but all MF0ICU2 devices will be

selected.

Remark: Any other data received in state READY1 state is interpreted as an error and

the MF0ICU2 falls back to its waiting state (IDLE or HALT, depending on its previous

state).

The response of the MF0ICU2 to the cascade level 1 SELECT command is the SAK byte

with value 04h. It indicates that the UID has not been complete received by the PCD yet

and another anticollision level is required.

7.2.3 READY2

In the READY2 state the MF0ICU2 supports the PCD in resolving the second part of its

UID (4 bytes) with the ANTICOLLISION command of cascade level 2. This state is left

with the cascade level 2 SELECT command.

Alternatively, state READY2 state may be skipped via a READ (from block address 00h)

command as described in state READY1.

Remark: If more than one MF0ICU2 is in the field of the PCD, a read from address 00h

will cause a collision because of the different serial numbers, but all MF0ICU2 devices

will be selected.

Remark: The response of the MF0ICU2 to the cascade level 2 SELECT command is

the SAK byte with value 00h. According to ISO/IEC14443 this byte indicates whether

the anticollision cascade procedure is finished (see Ref. 6). In addition it defines for the

MIFARE architecture platform the type of the selected device. At this stage the MF0ICU2

is uniquely selected and only a single device will continue communication with the PCD

even if other contactless devices are in the field of the PCD.

Any other command received in this state is interpreted as an error and the MF0ICU2

falls back to its waiting state (IDLE or HALT, depending on its previous state).

7.2.4 ACTIVE

In the ACTIVE state READ (16 bytes), WRITE (4 bytes), COMPATIBILITY WRITE (16

bytes) commands or an authentication can be performed.

After a successful authentication the state "AUTHENTICATED" is reached, see Section

7.2.6.

The ACTIVE state is gratefully exited with the HLTA command and upon reception the

MF0ICU2 transits to the HALT state.

Any other command received in this state is interpreted as an error and the MF0ICU2

goes back to its waiting state (IDLE or HALT, depending on its previous state).

7.2.5 HALT

Besides the IDLE state the HALT state constitutes the second waiting state implemented

in the MF0ICU2. A MF0ICU2 that has already been processed can be set into this