• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 17 subscribers
  • Views 1095 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.

TRF7960A: NFC

Qianqian
Genius 5010 points

Part Number: TRF7960A
Other Parts Discussed in Thread: CC1310, , TRF7964A, TRF7970A, MSP430G2553

Hello TI Experts,

I have a few questions about TI's NFC~

1. I want to use NFC's  reader/writer function in the E-Lock design,do we have NFC embedded MCU,such as CC1310?

2. If I use TRF7960A + mcu ~ About MCU,besides need SPI interface, what's other requirments? If the MCU Comparator_A  must need? Or any other MCU is OK? I want to find the cheapest MCU that can wok with TRF7960A~

3. I find that their is few people use TI's NFC, Does TI continue to promote NFC? Do we have any advantage VS NXP?

  • 0
    TI__Guru*** 135355 points
    Hello Fawn,

    1) We don't have an NFC embedded MCU, only NFC transceiver like the TRF7960A, or the newer devices like the TRF7964A and TRF7970A. Each of these require an external MCU to control them.

    2) As far as peripherals go, not much else. SPI clock speed of 2MHz, interruptable GPIO for the IRQ signal, and another GPIO for toggling the EN line is all you need really. What you will need to look at for MCU selection is going to be memory size. There needs to be enough code space to support the functionality they want. I can give estimates for how much space specific reader/writer technologies take up on a lower bare bones level, though if they want to use the best firmware for robustness and reliability (which they should if it's for an E-Lock) they are looking at 28kB to 40kB Flash and 2-3kB RAM just for the NFC stack depending on how many tag technologies they support.

    3) Yes we still promote NFC. The advantage vs NXP's NFC embedded MCU's generally is that as an open transceiver, there is a lot more control over the application, but it also comes with more complexity than a 'blackbox' NFC IC. Price also tends to be a good point as with right MCU selection the two chip solutions tends to price out cheaper.
  • 0 in reply to Ralph Jacobi
    Genius 5010 points

    Dear Ralph,

    Thank you very much for your kindly explain~

    1. About MCU, I see the reference design has used MSP430G2553, Ram is 0.5kB,and the price is not cheap~Do you have other better choice(especially the price)

    Usually,if use ST/nuvoton, the software is compatible with MSP430?

    I found their is firmware on the TI's Website, Can the firmware be used in all MCU?

    How about the MCU's  driver and NFC's protocol stack code?

    2. NXP's NFC also needs MCU, I think their best advantage is that many software resources can be found on the Internet~~ The price or other performance TI may be better~

    So I want to know more about the software development~

  • 0 in reply to Qianqian
    TI__Guru*** 135355 points
    Hello Fawn,

    We do not and will not support competitor MCU's as far as firmware goes. Customers are free to port our TI example code for MSP430 processors to other MCU's, but our support for any issues that arise due to the porting will be limited due to no knowledge of other companies MCU's. I can answer technical questions on device operation etc. in such a case, but any issues that are firmware rooted will be up for the customer to solve.

    The MSP430G2553 is an option but it also doesn't allow for a full NFC stack to run so there is a sacrifice of robustness in exchange for the small MCU size. I would recommend no matter what MCU is selected that if this for an E-Lock the customer should look to use our full NFC Stack which has the requirements mentioned in my prior post.

    That Firmware can be found within our comprehensive app note: www.ti.com/lit/pdf/sloa227
  • 0 in reply to Ralph Jacobi
    Genius 5010 points
    Hi Ralph,
    Got it,and one more question, E-lock needs full NFC Stack？ Is it for safety? When we don't need full NFC Stack?

    By the way, when will we use the card belongs to 15693 Protocal? Is the 15693 cards in common use in the E-lock situation?
  • 0 in reply to Qianqian
    TI__Guru*** 135355 points
    Hello Fawn,

    The example for the MSP430G2553 is just a basic RFID reader example which hasn't gone through significant testing in terms of handling errors, read failures, etc. while the NFC stack we have was tested rigorously against NFC Forum Standards. It is more robust and reliable, and will provide the best user experience. Given that an E-Lock as security implications, I would imagine the customer will want the NFC stack that has been thoroughly tested rather than the bare bones example that serves more of a demonstration than being intended to be used in a final product.

    ISO15693 can be used for E-Locks, that is an application specific decision though. Depending the level of security they want, they may look into ISO14443A or ISO14443B tags which have encryption on them (though support for such tags would need to be developed by them as that is again, application specific).
  • 0 in reply to Ralph Jacobi
    Genius 5010 points
    Hi Ralph,
    It's very kind of you to teach me so much~~