• Resolved

CCS/TM4C123GH6PM: CCS v7 Fatal error #1966

Part Number: TM4C123GH6PM

Tool/software: Code Composer Studio

OS:         Windows 7 Home Premium, 64 bit, SP1

CCS:       Version 7.0.0.00042

Hardware:           Tiva C Series TM4C123G LaunchPad Evaluation Kit

Hi,

I have been trying to work through the tutorials found at the “Getting Started with the TIVA™ C Series TM4C123G LaunchPad” wiki found at:

http://processors.wiki.ti.com/index.php?title=Getting_Started_with_the_TIVA%E2%84%A2_C_Series_TM4C123G_LaunchPad&DCMP=tivac&HQS=TM4C123G-Launchpad-Workshop

specifically the workbook pdf linked in the “Workshop Material” section.

I have installed CCS as instructed (albeit v7 rather than v5.5) in the workbook, Lab 1. Also:

TivaWare_C_Series-2.1.3.156 installed into C:\ti\TivaWare_C_Series-2.1.3.156. The C:\ti\ directory attribute is read-only and can’t be changed – don’t know whether this is significant or not.

LM Flash Programmer, Workshop Lab Files, Terminal Program and Windows-side USB Examples also installed as per workbook Lab 1. QuickStart Application verified as working and Stellaris Virtual Serial Port identified as COM3. Communication established with the board via putty.exe. All good so far.

Problems occur when I try to complete Lab 2. I have worked through all the steps in the workbook (allowing for cosmetic differences between CCS v5.5 and v7). Everything appears fine until Step 15 – “Build, Load, Run”. On clicking the Debug button I see fatal errors recorded in the Console view, as follows:

 

**** Build of configuration Debug for project lab2 ****

"C:\\ti\\ccsv7\\utils\\bin\\gmake" -k -j 2 all -O

'Building file: ../main.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --preinclude="C:/ti/TivaWare_C_Series-2.1.3.156" --define=ccs="ccs" --define=PART_TM4C123GH6PM -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi --preproc_with_compile --preproc_dependency="main.d" "../main.c"

 

>> Compilation failure

subdir_rules.mk:9: recipe for target 'main.obj' failed

Fatal error #1966: cannot open source file "C:/ti/TivaWare_C_Series-2.1.3.156": Invalid argument

1 catastrophic error detected in the compilation of "../main.c".

Compilation terminated.

gmake: *** [main.obj] Error 1

'Building file: ../tm4c123gh6pm_startup_ccs.c'

'Invoking: ARM Compiler'

"C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --preinclude="C:/ti/TivaWare_C_Series-2.1.3.156" --define=ccs="ccs" --define=PART_TM4C123GH6PM -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi --preproc_with_compile --preproc_dependency="tm4c123gh6pm_startup_ccs.d" "../tm4c123gh6pm_startup_ccs.c"

 

>> Compilation failure

subdir_rules.mk:16: recipe for target 'tm4c123gh6pm_startup_ccs.obj' failed

Fatal error #1966: cannot open source file "C:/ti/TivaWare_C_Series-2.1.3.156": Invalid argument

1 catastrophic error detected in the compilation of "../tm4c123gh6pm_startup_ccs.c".

Compilation terminated.

gmake: *** [tm4c123gh6pm_startup_ccs.obj] Error 1

gmake: Target 'all' not remade because of errors.

 

**** Build Finished ****

 

I’ve tried searching these forums and general Googling but haven’t found much to help me. I’m guessing that there’s some problem with accessing the TivaWare directory, but my near complete lack of experience with CCS means I could be completely wrong, of course. Any help would therefore be greatly appreciated.

 

Chris.

Chris Hill.

Somewhere in Northern England.

My blog.

  • Hi Chris,

    Chris Hill

    'Building file: ../main.c'

    'Invoking: ARM Compiler'

    "C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-arm_16.9.0.LTS/include" --preinclude="C:/ti/TivaWare_C_Series-2.1.3.156" --define=ccs="ccs" --define=PART_TM4C123GH6PM -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --abi=eabi --preproc_with_compile --preproc_dependency="main.d" "../main.c"

     

    >> Compilation failure

    subdir_rules.mk:9: recipe for target 'main.obj' failed

    Fatal error #1966: cannot open source file "C:/ti/TivaWare_C_Series-2.1.3.156": Invalid argument

    1 catastrophic error detected in the compilation of "../main.c".

    Compilation terminated.

    gmake: *** [main.obj] Error 1

    The error is caused by the part of the build options I highlighted in bold.

    the --preinclude option is expecting a file, not a path. I suspect that you were actually intending to add an include search path instead. That option is --include_path. Check your build options and your include search paths in the project properties. It is a common mixup since the configuration of both the --preinclude and --include_path options are next to each other is the GUI dialog.


    Thanks

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

  • In reply to Ki-Soo Lee:

    Hi Ki,

    Thanks for your rapid response to my question, and apologies for my delay in replying.

    To be honest your answer did go a little over my head, but that is only due to my lack of knowledge/experience of CCS. However, I did get the basic gist of what you were saying, and this put me on the right path to the solution.

    As I mentioned, I was following the "Getting Started with the Tiva™ TM4C123G LaunchPad Workshop - Student Guide and Lab Manual" in pdf format from the Wiki I linked to in my original post. I went back over the "Lab 2 Procedure" section extremely carefully, with particular reference to the part about adding path and build variables (section 8 onwards).

    There is an inconsistency in Section 12 (pdf page 50) between the lab manual screenshot at the bottom of the page and the corresponding window in CCS. The "Specify a preinclude file (--preinclude)" and "Add dir to #include search path (--include_path, -I)" are swapped over in CCS! So if you're not careful (as I wasn't) it's easy to add ${TIVAWARE_INSTALL} as a preinclude file, which doesn't work and was the error you pointed out in my original post. This is quite a subtle inconsistency between the lab manual and CCS and took me some time to figure out. Once that error was corrected in CCS, everything worked as advertised. Are there any plans to update the lab manual pdf? I may not have been the only person to make this mistake.

    Thanks for your assistance once again...

    Chris.

    Chris Hill.

    Somewhere in Northern England.

    My blog.

  • In reply to Chris Hill:

    Chris Hill
    here is an inconsistency in Section 12 (pdf page 50) between the lab manual screenshot at the bottom of the page and the corresponding window in CCS.

    Ah ok. I've seen similar issues before. Sometimes the fields are swapped in the GUI. It depends on the CCS and compiler versions I believe. The inconsistency can cause confusion as it did in your case. I'm not sure if there are any plans to update the PDF. The folks in the TM4C forums can answer that best. The bigger question for me is the inconsistency with the GUI itself. I'll need to see if going forward, it will be consistent...


    Thanks

    ki

    -----------------------------------

    Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

    Having CCS problems? Check out the CCS Troubleshooting Guide

    Looking for CCS Training? Check out the CCS Training Site

    Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal