• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 359 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TRF 7970A

laryyg

I have a board with a TRF 7970A chip with a firmware that is the same as TI EVM. When running the TI TRF7970 EVM Control app from the 14443A Tab, with a RFID Tag NTAG 213 from NXP, the Anticollision commands returns the UID, but after the Select command is sent, the response is not as expected:

12:21:53.437 --> 0109000304A0010000
12:21:53.593 <-- 0109000304A0010000
14443A REQA.
(04)[0466A04A52623E808E]
12:22:14.976 --> 0111000304A20466A04A52623E808E0000
12:22:15.133 <-- 0111000304A20466A04A52623E808E0000
14443A Select.
(4400)(04)[00]

The format according the slou321.pdf should be:

(xxxx)[yy]

Does it mean that the current firmware in the board is not compatible with the RFID Tag?  

When sending the the command 010A0003047230110000 (read 4 blocks from address 0x11)

the response is :

13:16:46.059 --> 010A0003047230110000
13:16:46.180 <-- 010A0003047230110000
NFC Type 2 command
[NACK]

Is there a solution that will allow to communicate with the RFID Tag?

Thanks

 

  • 0
    TI__Guru*** 128245 points
    Hello laryyg,

    The reply you got from the Select command seems fine. That reported back an ATQA and the SAK as would be expected. The [00] is probably just an extra couple bytes sent to the GUI for some reason.

    As for the Read command, I used the TRF7970AEVM with an NTAG 213 and the command you provided and I was able to read the Blocks from the tag without issue. I did not use the Select command in between though. The anticollision command is all you need to do before reading block data. That may help a bit?

    Also you may want to try and use one of our newer firmware bases instead: e2e.ti.com/.../493678

    It might be cleaner and easier for you to use than the EVM code unless you require the ability to send host commands as seen with the EVM firmware.