MFRC522

[RajPadmani]

Hello everyone,

I’m using the MFRC522 reader IC with MIFARE Classic cards.
In my application, sometimes a command (for example, authentication, read, or decrement) fails due to timeout or CRC error.

My question is:

After any command failure, is it mandatory to reestablish communication with the card  (i.e., send REQA/WUPA → ANTICOLLISION → SELECT again), or can I retry the command directly?

I’ve checked the MFRC522 datasheet, but I didn’t find any explicit statement that says the communication must be reinitialized after an error.
However, I know that in ISO/IEC 14443 and MIFARE Classic documentation, the card may return to an IDLE or HALT state after errors or failed authentications, which might require reactivation.

Could you please confirm the correct recovery procedure according to NXP’s official recommendation for the MFRC522?
And if possible, point me to the relevant section in the datasheet, application note, or ISO reference that specifies this behavior.

Thanks.

[jimmychan · Accepted solution]

This is necessary because after a failed command, especially authentication, the card may transition to the IDLE or HALT state, as per ISO/IEC 14443-3 and MIFARE Classic specifications. In such states, the card will not respond to further commands unless reactivated.

The ISO/IEC 14443-3 standard (e.g. referenced in NXP AN10834) describes how a PICC (card) may enter IDLE or HALT states after certain errors, requiring a new activation sequence.