Skip to main content
Visitor II
April 25, 2023
Solved

CR95HF FAST_READ Command using NTAG213 (14443A)

  • April 25, 2023
  • 2 replies
  • 1053 views

We are using the CR95HF over SPI and communicating with a single NTAG213 tag.

I can successfully configure the reader and read 4 pages of user memory reliably using the READ command:

00 04 03 30 04 28. // Reads 16 bytes from Addr 0x04

We would like to read multiple blocks using the FAST_READ command but the following command structure gives an 0x87 error;

00 04 04 3A 04 07 28

Any idea why this doesn't work?

    This topic has been closed for replies.
    Best answer by Brian TIDAL

    Hi,

    I've tried the 04 04 3A 04 07 28 command on my side and I've received:

    80 15 30 30 30 30 32 38 FF FF 06 FF FF FF 07 FF FF FF A4 A5 08 00 00

    Can you check the Frame Delay Time in your protocolSelect command? It should be at least T_ACK/NACK (see the Tag Datasheet).

    See also https://community.st.com/s/question/0D50X0000AFqKjkSQF/why-does-my-cr95hf-respond-with-0x87-timeout-or-no-tag-after-successfully-writing-to-a-ntag216-nfc-forum-type-2-compliant-tag

    Rgds

    BT

    2 replies

    Technical Moderator
    April 25, 2023

    Hi,

    I've tried the 04 04 3A 04 07 28 command on my side and I've received:

    80 15 30 30 30 30 32 38 FF FF 06 FF FF FF 07 FF FF FF A4 A5 08 00 00

    Can you check the Frame Delay Time in your protocolSelect command? It should be at least T_ACK/NACK (see the Tag Datasheet).

    See also https://community.st.com/s/question/0D50X0000AFqKjkSQF/why-does-my-cr95hf-respond-with-0x87-timeout-or-no-tag-after-successfully-writing-to-a-ntag216-nfc-forum-type-2-compliant-tag

    Rgds

    BT

    TGree.2Author
    Visitor II
    April 25, 2023

    The increased T_ACK helped - thank you!

    Regards

    Tony