• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 19 subscribers
  • Views 731 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 Evaluation Module and MSPF430F5529 launh pad issues

Francisco da Silva Tavares
Prodigy 140 points

Other Parts Discussed in Thread: UNIFLASH, MSP430F5529, TRF7970A

I bought these two modules from digikey to work in a NFc project.

After installed both f them, I found the following issues:

A) Evaluation Module and MSPF430F552 comes with 2 project

     RW_P2P_CE_1    RW_P2P_CE_2.  None of them are working with launch pad.

    I posted a question a and a user told me that there as a problem with pin configuration and sent me a RW_P2P_CE_1.OUT.     I sent this file to launch pad with Uniflash and it worked.

However, the original projects don´t even compile. They were created in an older CS version which has some differences in MSP430F5529.h

B) TRF7970A Evaluation Module has issues as well. When it is powered it detects my nfc tags but it can´t comunicate with PC gui. I found  out in TI forum that again there is a problem with the firmware.

I downloaded the trf7970a Modified with compiles ok. But I cannot flashed it to TRF7970A Evaluation Module.

Do I need another device just to to this?

I have two TI modules, spent some money and until now none of them are 100% working (sw and Hw)

Does someone have any idea how to solve this issues? I´m considering not using TI tools anymore.

  • 0
    TI__Guru* 91296 points

    Francisco - 

    couple questions back first - did you follow these instructions? 

    http://www.ti.com/lit/ml/slab069/slab069.pdf 

    especially about the jumpers and the com ports and the driver? Meaning, pls make sure it is enumerating as CDC and that you choose that COM port to use with the GUI, and you are running 115200, 8N1 and not at 9600...

    then you should also be using this project and choosing the ..._CE1.out or .hex to load out of the Debug folder.

    0677.NFCLink_1.00.00.02.zip

    then let us know how that goes on your side. 

    thanks!

  • 0 in reply to Josh Wyatt
    Prodigy 140 points

    Josh,

    Like I said this project doesn´t complie on CCS v5.

  • 0 in reply to Francisco da Silva Tavares
    Prodigy 140 points

    I solved the issue. I reconfigured the project setting to use the gpio.obj (that was in the project that you sent) instead of recompiling gpio.c and it worked.

  • 0 in reply to Francisco da Silva Tavares
    Guru 24520 points

    Hi Francisco,

    I also met the same problem which you had met.  I could not complied this project in CCSv5.5 and showed the "#20 identifier "__SFR_FARPTR" is undefined." on CCS.

    So would you please teach me  the solution for this problem?

    Best regards,

    Kaka

  • 0 in reply to Kaka
    Prodigy 140 points

    I reconfigured the project settings to use the gpio.obj (that was in the project already) instead of recompiling gpio.c 

    So if your project has already a compiled .obj (from the correspondent .c file) you can overcome this issue by configuring ccs to use this .obj instead  of using the .c file. Im my case gpio.obj instead of gpio.c

    If your project does not have the .obj I don´t have an simple answer because I tried to modify .c file to the new ccs version and I found out that this means a lot of other modifications as well.

    In this case perhaps you can try to generate the .obj in the original version the .c files were created and them use them in the current ccs version