• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 17 subscribers
  • Views 641 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Compiler/TRF7970A: Probleme with transmission

S.I.D.I.S.F.A
Intellectual 490 points

Part Number: TRF7970A
Other Parts Discussed in Thread: TRF7960A

Tool/software: TI C/C++ Compiler

Hi, 

i have a problem with my transmission between the tag and the TFR7970A.

i use CC26X2R and TRF7970A to do NFC ISO 14443a-3.

In IDLE when  the mcu send REQA command ( the irq status is qual tx complete) and when i receive the anwsers the irq status equal Rx complete).

But in READY 1  MODE  when the mcu send command for the anticollision (the irq statuse is qual tx complete) but i haven't receive complete and after i have protocol error.

Any ideas ?

Best Regards,

SIDI

  • 0
    TI__Guru*** 135355 points

    Hello SIDI,

    Have you checked the SPI lines to see the exact IRQ status you can getting in reply? Also is the Protocol Error occurring on the first command sent (0x93 0x20) or the subsequent SSD resolution commands (0x95 ... or 0x97 ...)?

  • 0 in reply to Ralph Jacobi
    Intellectual 490 points

    Hello Ralph,

    Yes i cheched the spi line.

    I have :

    in a cc26x2:

    In msp432p401R

    I don't nkow why i haven't 0x40.

    this protocol occured when i sent 0x93.

    It's strang to have this error here

    Best Regards,

    SIDI

  • 0 in reply to S.I.D.I.S.F.A
    TI__Guru*** 135355 points

    Hello SIDI,

    So you do a read of the IRQ register and get a 0x80 and reset the FIFO after sending the 0x93 command, but then get a 0xC0 afterwards anyways?

    The issue is you are still get a 0xC0. That will never work well.

    Try and add a dummy read to the reading of the IRQ register... I haven't any issues with the TRF7970A like the TRF7960A with requiring a dummy read to properly clear the IRQ, but it's worth a try here.

    Also check the timing from when you get that 0x80 to when you get the 0xC0, and also how long the IRQ line is high because reading the 0x80.

  • 0 in reply to Ralph Jacobi
    Intellectual 490 points

    Hello,

    It works now, I made some modifications.


    Now I am trying to find out how to read in the registers of the tag with the microcontroller.

    Do you know what function can i use?

    Best Regards,

    Sidi

  • 0 in reply to S.I.D.I.S.F.A
    TI__Guru*** 135355 points

    Hello Sidi,

    I provided feedback on this before: 

  • 0 in reply to Ralph Jacobi
    Intellectual 490 points

    Hello Ralph,

    Yes, I remember this reply.

    When i use t2t_app.c command my nfc state machine fail (THEN ti show : NOT NDEF FORMATTED).

    I try to see a data from my sensor(TEMPERATURE) .

    Best Regards,

    Sidi

  • 0 in reply to S.I.D.I.S.F.A
    TI__Guru*** 135355 points

    Hello Sidi,

    As mentioned: "Your tag needs to be NDEF formatted to be read with that software."

    The message indicates the tag is not formatted.

    Use an Android smartphone app to format the tag by writing a message to the tag, then try again. That would be the simplest/quickest way to format. We do not have code that formats non-TI tags.

  • 0 in reply to Ralph Jacobi
    Intellectual 490 points

    Hello Ralphi,

    Thank you for your help .

    This is what i have:


    But when I add a new read command to read the new data from the sensor which is in the tag i have "Not NDEF formatted".I want to know is the new data(from sensor of the tag board) is not automatically read by the mcu? and therefore in that case I no longer need a new read command because when I changed the value of the NDEF the tag automatically read.

    Best Regards,

    SIDI

  • 0 in reply to S.I.D.I.S.F.A
    TI__Guru*** 135355 points

    Hello Sidi,

    Oh okay, I understand better now what you are trying to do. This is an easy enough problem to solve for you, but you just need to do some adjustments to the application layer!

    What you can do is make your own application to read proprietary data. The out of box application is for NDEF only, but that's just how we have set it up. You just need to adjust the state machine to read non-NDEF tags for your use case. Everything is laid out as far as the process of what reading is done, so it's quite simple to make that change if you take the time to study how the state machine runs! :)

  • 0 in reply to Ralph Jacobi
    Intellectual 490 points

    Hello Ralph,

    Thank you, it runs now like i want.

    Best Regards, 

    Sidi