• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 16 subscribers
  • Views 504 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.

TRF7962A: TRF7962A Read Multiple Blocks Failure failure

malco lee
Prodigy 20 points
Part Number: TRF7962A

I used TRF792A to read multiple blocks  and use read multiple blocks command(0x23) . I found that there was no problem in reading several blocks. When  read 28 blocks, TRF7962A can't read success。sometimes,  Call  inventory command, TRF7962A can't  inventory tags. when I reset  the hardware，TRF7962A work normally!

I try to read blocks separately, read 20 blocks first and then read 8 blocks , now I can read 28 blocks OK，However, there is a problem. TRF7962A will not work after  read 28 blocks continuously for a period of time.

At the same time, I went to test the detection EAS feature, and the same problem occurred，TRF7962A stopped working。

When TRF7962A cannot work properly, the MCU can work normally. Use oscilloscope to test TX pin  circuit waveform， The waveform is correct。

So I want to know how to solve this problem？

  • 0
    TI__Guru*** 129700 points
    Hello Malco,

    What firmware base are you using for your project? Is it TI developed firmware, or something you developed yourself?
  • 0 in reply to Ralph Jacobi
    Prodigy 20 points

    Refence TI developed firmware. Dectect  EAS add by myself,   I see the log ,  detect EAS 31980 times,  TRF7962 not work

  • 0 in reply to malco lee
    TI__Guru*** 129700 points
    Hello Malco,

    EAS 31980? Is that a specific tag? I tried googling it and found nothing.

    The issue you are having is almost guaranteed to be a software issue, unless the tag you are using is not ISO15693 in some manner.

    You mention a hardware reset fixes the issue, but I think that is too extreme. A small software reset is much more efficient. If you followed TI code closely, you should have implemented that.

    Soft reset is done with 0x03 and 0x00 direct commands which are SOFT_INIT and IDLE respectively. Once those are issued, wait 1 ms, and then configure device registers. That should be standard process for handling any errors that occur.