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.

CCS/RF430FRL152H: CCS issue

Part Number: RF430FRL152H

Tool/software: Code Composer Studio

I was helped by Ralph Jacobi on the following issues:

https://e2e.ti.com/support/wireless-connectivity/other-wireless/f/667/t/806174

Ralph Jacobi gave me a project.(You can download the project at the address above.)
I tried to debug the project, but there was errors.

Why do occur, how to fix the errors As some of you?

At first, I got this error. I pressed the stop.

I have to press the stop button 8 because there are about 8 error windows.
And then there's this dialog box, and I press the applied button.

Then I can see the following error.

All errors have been copied to text:

<Description>
Description Resource Path Location Type
gmake: *** [Hardware/mcu.obj] Error 2 TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
gmake: *** [Hardware/spi.obj] Error 2 TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
gmake: *** [Hardware/trf79xxa.obj] Error 2 TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
gmake: *** [Hardware/uart.obj] Error 2 TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
gmake: *** [Hardware/VLO_Library.obj] Error 2 TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
gmake: *** [main.obj] Error 2 TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
gmake: *** [NFC/iso15693.obj] Error 2 TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
gmake: *** [system_pre_init.obj] Error 2 TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
gmake: Target 'all' not remade because of errors. TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
Description Resource Path Location Type
Invalid arguments '
Candidates are:
void MCU_delayMillisecond(?)
' main.c /TRF7970ABP_G2ET_FRL_Reader line 123 Semantic Error
Description Resource Path Location Type
Invalid arguments '
Candidates are:
void MCU_delayMillisecond(?)
' main.c /TRF7970ABP_G2ET_FRL_Reader line 133 Semantic Error
Description Resource Path Location Type
Invalid arguments '
Candidates are:
void MCU_delayMillisecond(?)
' main.c /TRF7970ABP_G2ET_FRL_Reader line 140 Semantic Error
Description Resource Path Location Type
Invalid arguments '
Candidates are:
void MCU_delayMillisecond(?)
' main.c /TRF7970ABP_G2ET_FRL_Reader line 169 Semantic Error
Description Resource Path Location Type
Invalid arguments '
Candidates are:
void UART_putIntroReaderMsg(? *, ? *)
' main.c /TRF7970ABP_G2ET_FRL_Reader line 161 Semantic Error
Description Resource Path Location Type
Symbol 'BIT0' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 158 Semantic Error
Description Resource Path Location Type
Symbol 'BIT1' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 129 Semantic Error
Description Resource Path Location Type
Symbol 'BIT1' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 130 Semantic Error
Description Resource Path Location Type
Symbol 'BIT2' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 136 Semantic Error
Description Resource Path Location Type
Symbol 'BIT2' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 137 Semantic Error
Description Resource Path Location Type
Symbol 'BIT7' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 158 Semantic Error
Description Resource Path Location Type
Symbol 'P2DIR' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 129 Semantic Error
Description Resource Path Location Type
Symbol 'P2DIR' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 136 Semantic Error
Description Resource Path Location Type
Symbol 'P2IE' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 158 Semantic Error
Description Resource Path Location Type
Symbol 'P2OUT' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 130 Semantic Error
Description Resource Path Location Type
Symbol 'P2OUT' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 137 Semantic Error
Description Resource Path Location Type
Symbol 'WDTCTL' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 119 Semantic Error
Description Resource Path Location Type
Symbol 'WDTHOLD' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 119 Semantic Error
Description Resource Path Location Type
Symbol 'WDTPW' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 119 Semantic Error
Description Resource Path Location Type
Type '__bis_SR_register' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 155 Semantic Error


<warnings> (1 item)
Description Resource Path Location Type
This project was created using a version of compiler that is not currently installed - 16.9.7.LTS [MSP430]. Another version of the compiler will be used during build - 18.12.1.LTS. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'. TRF7970ABP_G2ET_FRL_Reader properties Problem

What does it matter?

We are in the end game now.

  • Hello,
    Please see the related thread below:
    e2e.ti.com/.../744087

    Also carefully check for any non-alphanumeric character in any of the paths:
    e2e.ti.com/.../740719

    Thanks
    ki
  • An error occurred again, and this time, following the path.
    'out' files are files that I make myself?

     

  • The above error usually happens when the debugger is trying to load an *.out file that does not exist. The *.out file is usually missing because the build failed. Did the build fail with the same exact errors in your first post?
  • No, there were only errors like the text of this article at first.
    So, as you advised, I moved to a new path that contained only English and numbers, and there was a new error.
    This project was given to me by Ralph Jacoby.
    Is there any solution?
  • The *.out file does not exist as you say.
    Do I have to make this myself?
  • When you build a CCS project, the output is typically a *.out file. It is this *.out file that is loaded to your target by the CCS debugger.

    If the *.out file does not exist after you tried to build the project, then it means some build error occurred so that the *.out file could not get generated.

    Can you post all the messages in your build output console?
  • 다음과 같습니다.

    Description Resource Path Location Type
    Invalid arguments '
    Candidates are:
    void MCU_delayMillisecond(?)
    ' main.c /TRF7970ABP_G2ET_FRL_Reader line 123 Semantic Error
    Description Resource Path Location Type
    Invalid arguments '
    Candidates are:
    void MCU_delayMillisecond(?)
    ' main.c /TRF7970ABP_G2ET_FRL_Reader line 133 Semantic Error
    Description Resource Path Location Type
    Invalid arguments '
    Candidates are:
    void MCU_delayMillisecond(?)
    ' main.c /TRF7970ABP_G2ET_FRL_Reader line 140 Semantic Error
    Description Resource Path Location Type
    Invalid arguments '
    Candidates are:
    void MCU_delayMillisecond(?)
    ' main.c /TRF7970ABP_G2ET_FRL_Reader line 169 Semantic Error
    Description Resource Path Location Type
    Invalid arguments '
    Candidates are:
    void UART_putIntroReaderMsg(? *, ? *)
    ' main.c /TRF7970ABP_G2ET_FRL_Reader line 161 Semantic Error
    Description Resource Path Location Type
    Program "make" not found in PATH TRF7970ABP_G2ET_FRL_Reader C/C++ Problem
    Description Resource Path Location Type
    Symbol 'BIT0' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 158 Semantic Error
    Description Resource Path Location Type
    Symbol 'BIT1' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 129 Semantic Error
    Description Resource Path Location Type
    Symbol 'BIT1' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 130 Semantic Error
    Description Resource Path Location Type
    Symbol 'BIT2' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 136 Semantic Error
    Description Resource Path Location Type
    Symbol 'BIT2' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 137 Semantic Error
    Description Resource Path Location Type
    Symbol 'BIT7' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 158 Semantic Error
    Description Resource Path Location Type
    Symbol 'P2DIR' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 129 Semantic Error
    Description Resource Path Location Type
    Symbol 'P2DIR' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 136 Semantic Error
    Description Resource Path Location Type
    Symbol 'P2IE' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 158 Semantic Error
    Description Resource Path Location Type
    Symbol 'P2OUT' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 130 Semantic Error
    Description Resource Path Location Type
    Symbol 'P2OUT' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 137 Semantic Error
    Description Resource Path Location Type
    Symbol 'WDTCTL' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 119 Semantic Error
    Description Resource Path Location Type
    Symbol 'WDTHOLD' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 119 Semantic Error
    Description Resource Path Location Type
    Symbol 'WDTPW' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 119 Semantic Error
    Description Resource Path Location Type
    Type '__bis_SR_register' could not be resolved main.c /TRF7970ABP_G2ET_FRL_Reader line 155 Semantic Error
    Description Resource Path Location Type
    Invalid project path: Include path not found (\Hardware). TRF7970ABP_G2ET_FRL_Reader pathentry Path Entry Problem
    Description Resource Path Location Type
    Invalid project path: Include path not found (\include). TRF7970ABP_G2ET_FRL_Reader pathentry Path Entry Problem
    Description Resource Path Location Type
    Invalid project path: Include path not found (\msp430\include). TRF7970ABP_G2ET_FRL_Reader pathentry Path Entry Problem
    Description Resource Path Location Type
    Invalid project path: Include path not found (\msp430\IQMATHLIB_01_10_00_05\include). TRF7970ABP_G2ET_FRL_Reader pathentry Path Entry Problem
    Description Resource Path Location Type
    Invalid project path: Include path not found (\NFC). TRF7970ABP_G2ET_FRL_Reader pathentry Path Entry Problem
    Description Resource Path Location Type
    This project was created using a version of compiler that is not currently installed - 16.9.7.LTS [MSP430]. Another version of the compiler will be used during build - 18.12.1.LTS. See 'Help > Install New Software' and select 'Code Generation Tools Updates' to check if this compiler is available through a CCS update. Visit <a href="liveaction:OpenAppCenter">CCS App Center</a> to get the latest compiler support. Or <a href="software-dl.ti.com/.../a> and install the compiler, then register it with CCS through 'Preferences > CCS > Build > Compilers'. TRF7970ABP_G2ET_FRL_Reader properties Problem
  • The format is as follows:
    It doesn't seem to have changed much.

  • If you don't mind, can you carry out this project yourself?
    You only need to download the next two things. :
    e2e.ti.com/.../TRF7970ABP_5F00_G2ET_5F00_FRL_5F00_Reader.zip
    www.ti.com/.../MSP-IQMATHLIB
  • Strange. I also imported the project that Ralph attached and it builds fine without issue.

    Can you provide the output in the build console? For example, I copy and pasted my output to the text file attached below:

    /cfs-file/__key/communityserver-discussions-components-files/81/TRF7970ABP_5F00_G2ET_5F00_FRL_5F00_Reader.txt

  • When I press the OK button, the console window disappears, leaving only the Problem window.

  • hyosung kim said:

    When I press the OK button, the console window disappears, leaving only the Problem window.

    You can reopen it via 'View -> Console'

    Also just build the project without launching a debug session via 'Project -> Build Project'

  • 01:03:44 **** Clean-only build of configuration Debug for project TRF7970ABP_G2ET_FRL_Reader ****
    make clean
    Cannot run program "make": Launching failed

    Error: Program "make" not found in PATH
    PATH=[C:/ti/ccs901/ccs/eclipse/jre/bin/server;C:/ti/ccs901/ccs/eclipse/jre/bin;C:/ti/ccs901/ccs/eclipse/jre/lib/amd64;C:\Program Files (x86)\NAT Service;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Windows\System32\OpenSSH\;C:\Users\melon\AppData\Local\Microsoft\WindowsApps;;C:\ti\ccs901\ccs\eclipse;]

    01:03:45 Build Failed. 1 errors, 0 warnings. (took 231ms)


    **** Build of configuration Debug for project TRF7970ABP_G2ET_FRL_Reader ****

    Nothing to build for project TRF7970ABP_G2ET_FRL_Reader
  • hyosung kim said:
    01:03:44 **** Clean-only build of configuration Debug for project TRF7970ABP_G2ET_FRL_Reader ****
    make clean
    Cannot run program "make": Launching failed

    Check the below Builder Settings properties. They should look exactly like the screenshot below:

    Don't forget to click on "Show advanced settings" in the lower left corner to expose the extra options.

  • Finally, I build the following. Thank you very much.
  • It is building successfully now?

  • Finally, I carried out the build. Thank you. I'll be back with another question.
    Before you tell me about a new solution,
    After searching code generation tools update in Help -> install new software, it was solved by installing compilers.

    If I have the same problem again, I'll try the method you suggested.

    Thank you very much  :)

    The reply was too short, so I wrote it again for a long time, but it did not go up because of an error in Ti homepage. Thank you.

  • Ok good to hear. If you have another question, please start a new thread. I will close this one. Thanks!