Reply To: Problem authenticating a MIFARE Ultralight EV1 tag

Forum MIFARE SDK Problem authenticating a MIFARE Ultralight EV1 tag Reply To: Problem authenticating a MIFARE Ultralight EV1 tag

Re: Problem authenticating a MIFARE Ultralight EV1 tag

2. February 2017 at 14:19
Hi Jorge,

An expert notice me that in a case of failure the tag goes into the HALT state which can be interpreted as “end of communication” or “tag lost” (see state diagram on page 8 of the datasheet). But the datasheet shows on page 35 (command PWD_AUTH) that there is a dedicated NAK reply. It is still open, whether this reply is handled properly in the NFC driver implementation, means it is detected and sent back to TapLinx properly. This must be checked.

I reported this as bug report. Anyway, in the meantime you should catch the “tag lost” exception and handle it in your software. Unfortunately you have to deal with “tag lost exceptions” always. The device running your software can be removed from the tag at any time—before the transaction is finished.

The TapLinx team
+ 0  |  - 0