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.

TRF7964A: Design Help with regard to Pin SYS_CLK, MOD , ASK/OOK

Part Number: TRF7964A
Other Parts Discussed in Thread: TRF7970A

Hi  I am designing an NFC  Tag Reader and Writer CIrcuit that should be able to Read and Write NFC  Tags of tag2 Type.  In my System,  the host controller (ATTINY1617) will interface with the TRF7964A over 

SPI Bus, from the Data Sheet I am not able to understand the functionality of the  

MOD PIN- Do I need to connect to the Host controller or can simply be pulled down to GND by some 10K resistor, I  saw in some reference circuit they are pulling it down to GND

SYS_CLK : My Host controller has it own clock,  do I need to connect the SYS_CLK to the Host controller, if  not should I leave it floating or PULL to VI or GND

ASK/OOK - DO I need to connect this pin to the HOST controller. 

Any help will be appreciated. Look forward for support

Thanks & Regards

Orvi

  • Hi,

    because I am currently out of office I will give you a feedback on Monday. 

    Best Regards,

    Helfried

  • Thanks for your response.  I am using the  TRF7964A  for NFC Tag  (Tag2  type tag) Reader and Writer Application, my host controller is ATTINY and I will be communicating with the TRF7964A over the SPI BUS, I need your help with regard to the above pins as I have only fewer pins free in ATTINY. So does grounding the PIN  MOD, ASK/OOK will Work. 

    Also, it would be of great help if you can point me to a reliable READER  and Writer  C Source code for writing and reading  NFC TAgs of Type Tag2.  I came also across a number of reference source codes but most implement only READ functionality,  Write functionality is missing. Also not sure f these codes work. I really do not have access to costly devices like oscilloscopes etc to debug. 

    In case you only deal with Hardware Support, pls do forward my queries to the appropriate team. 

    Best Regards

    Kanchan

  • Hi Kanchan,

    I see you has opened a few threads which I try to answer here in one and close the others because the handling for us is easier.

    You want to use the Mifare Ultralight (C) tags which are type 2 tags and requires ISO14443A support. The 'C' type has also the 3DES feature which we can not support, but this can be done with a 3DES library. Also the MCU you use is not a TI one, so I can only point you to source-code for mainly TIs MSP430 MCUs.

    The Mifare Ultralight does not require any of the so called 'direct modes'. The pins MOD and ASK/OOK should be connect with a 10k resistor to GND and need not to be connected to the MCU. The SYS_CLK pin can be left open. 

    For your firmware implementation you can use the following firmware as base which contains also the WriteSingleBlock function for T2T (ISO14443A):

    https://www.ti.com/lit/zip/sloc297

    A second option would be to use the source code that can be found in our NFC demo package. The link to that can be found on the first page of the following document:

    https://www.ti.com/lit/an/sloa227b/sloa227b.pdf

    About the memory usage I can not give you any information because at first I don't no your MCU and also it depends on the ISO14443A subset of our code example that you implement.

    Hope that helps.

    Best Regards,

    Helfried

  • Hi  Helfried, 

    Thank you very much for the response. Yeah, I actually opened multiple threads as you were on leave and I thought someone from the community might help during this time. One more questions

    1.  Do we need to connect the EN2 Pin to GND or can leave it open. -- pls recommend 

    2. I have connected the IRQ  pin to the host controller I/O Pin., is this correct to do ?

    Also thanks for sharing the link to the Tag2 Reader and Writer firmware stack, I have downloaded the same and will check it. My concern is the code footprint for  tag2 read and write. I will do the porting from TI host controller to  ATTiny. 

    Based on your input I have designed the Board and would like to get the TI expert opinion on the components Placement and Antenna Design ( followed TI  Antenna Design Guidelines ). Just wanted to know if you only look after the software side or hardware as well. 

    Best Regards 

    Kanchan

     

  • Hi Kanchan,

    the EN2 pin has also to be connect with 10k to GND. See the datasheet chapter 6.6.3 Power Modes. When connected to GND the TRF will need minimum power when disabled with EN.

    The TRF IRQ output must be connected to the MCU in a way that it can interrupt the MCU.

    For the reader PCB layout we provide some guidelines:

    https://www.ti.com/lit/an/sloa139a/sloa139a.pdf

    Best Regards,

    Helfried

  • Hi  Helfried, 

    Good Morning,  I  tried build the sola227b.zip source code, but  gettign the following error ..  Looks like some permission related issues 

    ANy help or pointer to help  will be helpful 


    <Linking>
    warning #10366-D: automatic library build: using library "C:\ti\ccs1031\ccs\tools\compiler\ti-cgt-msp430_4.4.8\lib\rts430x_lc_ld_eabi.lib" for the first time, so it must be built. This may take a few minutes.
    error: errors occurred while reading
    c:/users/kanch/appdata/local/temp/ti2bc6~1/obj/nexttoward.ob


    >> Compilation failure
    Makefile:1092: recipe for target 'c:/users/kanch/appdata/local/temp/ti2bc6~1/obj/nexttoward.obj' failed
    gmake.exe[1]: *** [c:/users/kanch/appdata/local/temp/ti2bc6~1/obj/nexttoward.obj] Error 1

    >> Compilation failure
    Makefile:1092: recipe for target 'c:/users/kanch/appdata/local/temp/ti2bc6~1/obj/isdigit.obj' failed
    error: unable to rename C:\Users\kanch\AppData\Local\Temp\065362 to
    c:/users/kanch/appdata/local/temp/ti2bc6~1/obj/isdigit.obj: Permission
    denied
    gmake.exe[1]: *** [c:/users/kanch/appdata/local/temp/ti2bc6~1/obj/isdigit.obj] Error 1

    >> Compilation failure
    makefile:250: recipe for target 'F5529LP_TRF7970A_ALL_NFC_MODES.out' failed
    gmake.exe[1]: Target 'library' not remade because of errors.

  • Hi Kanchan,

    from my understanding there is a problem with the permissions on your computer. Because I am not an expert for the CCS I would ask you to put a request in the CCS E2E forum.

    Best Regards,

    Helfried