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

TRF7970A: ALL MIFARE Protocol

Takashi Hosokawa
Expert 1455 points

Part Number: TRF7970A

Hi All,

Please let me discuss basic issues.

Can I make a system that makes it correspond to ISO/IEC 14443-A, ISO/IEC 14443-B, and all MIFARE Protolol using TRF7970A?
(ex：MIFARE Mini, MIFARE 1K, MIFARE 4K, MIFARE Ultralight, MIFARE DESFire EV1 and MIFARE Plus)

I saw TIDM-NFC-SDM, TIDM-NFC-DESFIRE-AES and TIDM-NFC-RW, but I did not know whether it corresponds to all MIFARE Protocol.

Are sample programs corresponding to each protocol released?

If it is feasible, what is a good CPU? Is it MSP430F5529? Is it MSP432?

Customers are considering replacing from NXP.

Best Regards,

Takashi

  • 0
    TI__Guru*** 135355 points

    Hello Takashi-san,

    From a hardware level, yes. From a firmware level, the answer is very complicated.

    We don't have a single firmware package that supports Mifare Classic along with other MIFARE protocols. Doing this would require combining firmware packages. Given the NXP statement on MIFARE Classic: https://www.mifare.net/en/products/chip-card-ics/mifare-classic/security-statement-on-crypto1-implementations/ We will not be doing this at any point in the future.

    The best firmware package to start with would be our Reader/Writer example: http://www.ti.com/lit/pdf/sloa227

    This can be run on either MSP430F5529 or MSP432P401R.

    The customer will need to add a lot of application specific details to that firmware. It does not provided application examples related to secure tags such as MIFARE DESFire.

    The MIFARE DESFire example is only to authenticate the tag and does not include encrypted data transfers.

    The SLOA227 package includes API's for the ISO7816-4 commands which are used for such applications.

    The customer can leverage these APIs and build up their custom application from there.

    To add support for MIFARE Classic, the Special Direct Mode example would need to be integrated into the SLOA227 firmware stack: http://www.ti.com/lit/pdf/sloa214

    I will clearly state: This is not trivial. It will take a lot of effort to add SDM into the SLOA227 firmware. Again, we aren't going to do this due to the NXP statement on MIFARE Classic. The customer must take full responsibility for the process of porting the code and validating their system.