• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 16 subscribers
  • Views 781 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.

TRF7970 P2P can not work with NXP chips

jun
Prodigy 95 points
Other Parts Discussed in Thread: MSP430F5438A, MSP430F5529, TRF7970A

Hi,

 

I'm trying to development a firmware using TRF7970 EVM to communicate with

RC-S370 ( using NXP chip PN533) by NFC 106 kbps passive mode.

 

TRF7970 EVM is used as Target, and RC-S370 as initiator. I can get "SDD complete"

interrupt status with TRF7970 EVM, so RC-S370 can detect TRF7970 EVM correctly.

 

But during the protocol activation process, I can not receive the ATR_REQ packet from

RC-S370, only get "RF field changed" interrupt status with TRF7970 EVM.

 

For test,  I confirmed that the target firmware works fine with TI sample firmware, I 

can get ATR_REQ packet correctly.

 

Since RC-S370 can work with Nexus S by NFC 106 kbps passive mode, I believe 

RC-S370 can send ATR_REQ packet properly.

 

Do I need to change some register setting while communicate with NXP chips?

or are there something needed to notice?

 

Any information will be apprecaited.

 

Thanks,

 

Jun

 

 

 

 

  • 0
    TI__Guru* 91206 points

    Jun -

    Please see our TRF7970A NFC BSL app note here and the associated source code (written for the MSP430F5529 and the MSP430F5438A devices) which should help you out here. 

    http://www.ti.com/lit/an/sloa160/sloa160.pdf (app note)

    http://www.ti.com/litv/zip/sloa160 (C code project)

  • 0 in reply to Josh Wyatt
    Prodigy 95 points

    Hi, Josh

     

    Thank you for the helpful information.

    I will check the source to find a solution, and update the result here.

     

    Since I'm using engineering sample chips,  could this be a problem?

     

    By the way, Is there some actual performance using TRF7970A to work with

    NFC chips from NXP ?

     

    Best Regards,

    Jun

     

  • 0 in reply to jun
    TI__Guru* 91206 points

    Jun -

    i have not done 100% testing with all competitive parts - just with the NXP IC that is in the Nexus S phone so far. We put the TRF7970A in card emulation mode (Type 2 and 4) and was able to read it out using an app on the phone. Will continue this sort of activity as well and if we can keep each other updated, that would be great.

  • 0 in reply to Josh Wyatt
    Prodigy 95 points

    Hi, Josh

     

    Thanks for the time.

     

    I have done some investigation and found the direct reason about the problem.


    During my test, I put the TRF7970A in NFC normal modes with automatic SDD enabled.

     

    After RC-S370 reader / writer ( act as NFC 106 kbps Initiator) send SENS_REQ and

    SEL_REQ, it can get the response accordingly.

     

    But the SEL_RES from TRF7970A is "0x00" which means "Type 2 Tag Target",  so the

    software in RC-S370 reader/writer would send "Type 2 Tag Target" compatible command

    not DEP Target command which I expect.

     

    I don't know why SEL_RES from TRF7970A is “0x00” despite the chip is not in card emulation

    mode. Do you have some information about this?

     

    I try to disable automatic SDD function and do SDD process by software, but there is no

    RX interrupt happened after Initiator send SENS_REQ.  Do I need to do  some extra register

    setting when automatic SDD is disabled?

     

    Best Regards,

    Jun

     

  • 0 in reply to Josh Wyatt
    Prodigy 95 points

    Hi, Josh

     

    I'm still working on this problem, but no further progress, will update related

    information here if any.

     

    If possible, Could you send me a copy of the firmware source which can work

    with Nexus S in card emulation mode for reference? 

     

    Thanks,

    Jun