TRF7970ABP "program make is not found in path" error

no..iam still getting the same error and also iam getting question marks on #include<msp430.h>,#include<stdio.h>

and #include<stdlib.h>..iam attaching the snap shot..i went through some previous questions on the same error they suggested to check the "use default build command" option in project>>properties>>c/c++ build..should i do that ?

Hey,

I believe the issue is you are missing the basic MSP430 files and possibly the MSP430 compiler.  You probably need to install MSP430ware: http://www.ti.com/tool/msp430ware.  

Below you can see the Include paths.  These 3 files should be in msp430/include and /include.  

The _ROOT's are macro's defined on this tab seen below.  

Check to see if these paths exist.  If you have an older version of CCS, you may need to update this paths to point to your version.  

Thanks,

JD

i installed ccs v5.4 and the code worked fine in CCS...but  after running the main.c in CCS i went to docklight and did the routine steps but after i start the communication , its  not detecting or reading the tag. i have put the snapshot here

is the red LED on the launchpad blinking?

if not, hit play on the CCS or stop CCS and hit reset button...also check and make sure you have the IRQ jumper on the booster pack in the 2 to center position and that you have pulled P1.6 jumper on the LaunchPad. 

Plus here is today's drop...this project now supports: 

Supports automatic:

• tag UID, RSSI and data reading: 256bit Pro or Standard, 2kbit Plus and up to 4kb HF tag (STM) (green LED on Booster Pack)
• NFC Type 2 tag UID, RSSI and data reading  (MFUL, MFULC, etc.) (red LED on Booster Pack)
• FeliCa (RC-S860, -889, -965, -966) (delivers UID, RSSI and can identify which one it is, but no data reading yet) (blue and green flash together)
• NFC-4B (ISO14443B) (gets PUPI and RSSI, but no ATTRIB or NDEF data reading yet) (Blue LED on Booster Pack)
• NFC-4A (ISO14443A) (gets UID, RSSI and selects, but no NDEF data reading yet) (red LED on Booster Pack)

http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/667/1643.TRF7970ABP_5F00_G2553_5F00_v01_5F00_23_5F00_2014.7z

also, you may want to get rid of the RTS/CTS option in Docklight...i just tested it and it worked, but it seemed a little hokey as compared to it not being selected. 

also, don't forget to spin the UART jumpers (if you have v1.5, or wire them correctly on v1.4) so the backchannel UART data can flow through it from the MSP430G2553 on the launchpad...

please see slide 5 ==> http://www.ti.com/lit/ml/slab068/slab068.pdf

hi again, thanks for your updated code.

as you pointed we had put the jumpers for v 1.5. and followed the steps but are still unable to read any tags. docklight only shows that the "TRF7970 has been enabled" but no information of the tag is displayed. i have attached a snapshot of the above.  

please guide me ahead.

double check your IRQ jumper, make sure  the red LED on Launch Pad (the heartbeat is flashing) and also that you have COM port actually still active. and remove the RTS/CTS setting on your docklight. 

which tag type are you trying to use?

yes i have put the IRQ in position 2 as iam using rev 1.5 ,and the led is blinking and yes the com port is active. iam using a type 2 tag which i have got with DLP design Booster Pack. should i put the "flow control"in docklight to off or change it to other than "hardware handshaking-RTS/CTS "?

i have it (handshaking) set for off and i am also using the Type 2 tag which comes in the package with the BoosterPack...does the ISO14443A LED light up at all? did you try any other tags? (in case that one is damaged)

no the ISO14443a led is not glowing when i keep the tag near the booster pack.yes the tag is working fine as i checked it using a smartphone .i went through the main program i see that in line 141 the slave select is made high.shouldnt it be made low to read the tags?

do you have another -G2553 IC? did you load the code using CCS? 

do you have a picture of your setup?

it really sounds like you have a hardware issue now - that is hard to tell about without seeing your setup - maybe double check the DIP package in the socket, too. 

and here is today's drop, which adds text type RTD NDEF reading for Type 4B tags. 

http://e2e.ti.com/cfs-file.ashx/__key/communityserver-discussions-components-files/667/1072.TRF7970ABP_5F00_G2553_5F00_01_5F00_24_5F00_2014.7z

iam putting the pic of msp430 and nfc booster pack

i dont have another msp430 IC and yes i loaded the porgram using CCS v5.4

looks legitimate...for your patience...if you would like i can send you a known good setup from here if you can send me your shipping address at josh.wyatt@ti.com and you can send me the failing unit back afterwards so we can check it out. unless i can ship you another -G2553 MCU and that would work for you. 

let me know. 

thank you sir..i will talk to my mentor and contact you in a day or two.

thank you for your help Sir..the output results are shown in the snapshot

Hi,

I'm have a similar problem.

I'm using a DLP-7970abp connected with a msp430F5438a. I adapted a code for this microcontroler, but I don't understand the final part of code in Main, the interrupt functions.

in code comment appear "" /********** IT'S A TRAP!!!! (ISR'S) **********/ ""
My question is, How adapted this interrupt function for my microcontroler?

I tested and work, the SPI, the enable.. but don't work a IRQ.

Thank you for every help,

Hey Cesar,

The Trap ISR's are there just to catch you encase an ISR somehow fires that you are not expecting.  Basically, you shouldn't end up here, but since you are moving the pins around you may until you get your interrupts setup correctly.

The IRQ pin is setup in trf7970BoosterPack.h in the TRF7970ABP_Demo code.  This is where you could change the actual pin.   

Next step is to update the Interrupt Vector table.  The F5438A might be slightly different than the g2553, but in the Demo code our IRQ ISR is called by the Port2 ISR (because we were on pin 2.0).  This ISR is found in trf7970.c (ln. 358).  

You will have to update the #pragma vector = XXXXXX line.  If this Interrupt is currently one of the "trap" ISR's, then comment out the Trap ISR, to all it to reach our IRQ ISR.  

I hope this helps and isn't too confusing.  :)

If so, let me know, and I can take some screen captures or something.

Thanks,

JD