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

TRF7970A NFC Transceiver LaunchPad/BoosterPack Configurations + Programming Questions

Cole Harding
Prodigy 35 points
Other Parts Discussed in Thread: TRF7970A, MSP-EXP430F5529LP, DLP-7970ABP, UNIFLASH

Hello all,

I am currently looking at the TRF7970A NFC Transceiver for an NFC Reader/Writer application I am creating. I would like to purchase one of the recommended  LaunchPad/BoosterPack Configurations for prototyping purposes. In the Near Field Communication (NFC) reference PDF, I found three possible options including:

1. MSP-EXP430F5529LP + DLP-7970ABP

2. MSP-EXP432P401R + DLP-7970ABP

3. MSP-EXP430F5529 + TRF7970ATB

My question is, while I know these are great options for getting familiar with the functionalities of TRF7970A NFC Transceiver IC without having to worry about developing the RF section and the NFCLink software firmware library, will I be able to write custom code and program the controllers on these devices? I not only need to implement the full ISO/IEC 14443 processes, but also need to create a ISO/IEC 7816-4 challenge-response authentication model. Is this possible on these devices? Also, is there any support for doing something like this?

Thanks!

  • 0
    TI__Guru*** 128125 points

    Hi Cole,

    Thanks for looking into our NFC solution for your application!

    If you are using our Standalone NFC Stack solution from our Reader/Writer app note, then yes, you will be able to write custom code and program the controllers. However, you will need a Code Composer Studio Version 6.1 or newer license to do so as the code size far exceeds the 16kB limit on the free version.

    The source code from sloa227 is open source so you can see the deeper layers of the NFC Stack. It also provides API's for ISO7816-4 which will allow you to customize your responses and handle those challenge-response authentication applications.

    The firmware from sloa227 comes with some example applications which can be found in the nfc_gui_statemachines. These are used along with the GUI which comes with sloa227 in order to read out tag data from different tag types. In your case, you will want to look at the t4t_app.c file for a basis on how to begin structuring your application.

    This will include ISO7816-4 API calls for Select, Read Binary, and Write Binary. You can also send custom APDU's using the ISO_7816_4_sendAPDU function.

    We can provide guidance as you go along with your application architecture. The sloa227 app note can be a useful resource at times, but for API calls we also have an API User Guide which you can find in the installed software at: C:\TI\msp430\TRF7970A_RW_1.02.05\doc (presuming default install location on a Windows system)

    I do want to clarify one thing, you mentioned NFCLink and I wasn't sure if you meant the software found at http://www.ti.com/tool/nfclink when saying so - if you did, then that is a different package than what is provided in sloa227. This solution is used for those who need to use the NCI protocol in a host-based system. If you need that NCI functionality, then we can provide suggestions on how to communicate with NCI to achieve the use case, but the NFCLink NCI source libraries cannot be edited. Hence why I am suggesting the sloa227 firmware which is open source for you to edit as you desire.

    Regarding the three evaluation platforms you mentioned:

    1. This is our most commonly used system, it is a low cost evaluation option and operates at 3.3V. The F5529 is 16 bit MCU.
    2. This is our evaluation options for the MSP432 platform which is an ARM processor - if you are using ARM, then this is the recommended platform
    3. This is our 'high end' evaluation system for the F5529 - the biggest advantage you get with this over the LaunchPad is that the TRF7970ATB board will operate at 5V which will result in more RF output power, longer read ranges for tags, etc.

    Hopefully that will help you decide which of the platforms best fit you to start evaluating.

    Let us know if you have any questions about this!

  • 0 in reply to Ralph Jacobi
    Prodigy 35 points
    Ralph,

    Thank you for your response! So, If I were to purchase MSP-EXP430F5529LP + DLP-7970ABP bundle, I would be able to program the F5529 using the standalone NFC stack solution? The various documents on the TRF7970A all use examples that use NFClink, not sloa227.

    Also, besides the help documents in the zip file and the PDF you attached, are there any resources for getting started with sloa227?

    Thanks!

    Cole H.
  • 0 in reply to Cole Harding
    TI__Guru*** 128125 points

    Hi Cole,

    The reason for that is the sloa227 firmware was released last year and we have not had the time to create similar documentation for it.

    We are in the process of finalizing a Quick Start Guide for sloa227 which will give you basic details like the NFCLink documentation about how to set it up, work with the GUI etc. Let me try and get a draft version I can share with you sometime today.

    Regarding your question of "So, If I were to purchase MSP-EXP430F5529LP + DLP-7970ABP bundle, I would be able to program the F5529 using the standalone NFC stack solution?"

    To program the MSP430 LaunchPad you would have two options:

    • One is to use the binary image we have included in the firmware with CCS Uniflash, this is available to anyone in order to evaluate with our demo application.
    • The other is to use Code Composer Studio V6.1 or newer to load the program into the LaunchPad. This requires a license for the full version of CCS.
      • This is also the only way you can modify and customize the firmware. Without a full license for CCS, you will not be able to compile the firmware projects and thus cannot make changes to them.
      • This is the same for the NFCLink firmware solution as well.