Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

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.

Fatal error #1966: cannot open source file

Other Parts Discussed in Thread: TM4C123GH6PM

I'm new to Tiva C series and uses the microcontroler TM4C123G and while i was follow the guide of "TM4C123G_LaunchPad_Workshop_Workbook" in lab 2, when I compiled there are build errors 

and here is my include path

Linker path

and on the left bar, things are all included in my project

but it always shows that 

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

plz help!!

BTW, I placed my project in disk E/: while I put the library and CCS compiler in disk C/:. Does it matter?

  • Hello Chinpo,

    Can you check that the directory driverlib exists at the path C:/ti/TivaWare_C_Series-2.1.0.12573 in your PC

    Regards

    Amit

  • Amit:

    yes, I'm sure

    Also, when I change the path to C:/ti/TivaWare_C_Series-1.1 which is the older version of driverlib, it still have errors

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

     

  • Hello Chinpo,

    I am able to replicate the issue. It is because you had added the --preinclude

    You have to remove it from the Build->ARM Compiler->Include Options

    Regards

    Amit

  • Thanks Amit:

    the problem is solved though I don't know why there's error when something is added in preinclude

    But there's still a warning 

    warning #10210-D: creating ".stack" section with default size of 0x800; use the -stack option to change the default size

    I've searched on the net and knew that it has something to do with cmd file. I had included "tm4c123gh6pm.cmd" isn't that enough for this project?

    thanks 

  • Hello Chinpo,

    The preinclude is for file search for Macro definition resolution and for including source code definition.

    I have pasted a section of cmd file I am using. I do not see any warning message.

    SECTIONS
    {
        .intvecs:   > APP_BASE
        .text   :   > FLASH
        .const  :   > FLASH
        .cinit  :   > FLASH
        .pinit  :   > FLASH
        .init_array : > FLASH

        .vtable :   > RAM_BASE
        .data   :   > SRAM
        .bss    :   > SRAM
        .sysmem :   > SRAM
        .stack  :   > SRAM
    }

    __STACK_TOP = __stack + 512;

    Regards

    Amit

  • This is just a warning caused by the default settings, you can always change it.. here

    You can follow a relevant post here..

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/303501.aspx

  • This doesn't make sense. I need the preincludes to compile. This worked just fine before my last update. Now I just get cryptic error messages

    >> Compilation failure
    gmake: *** [pid.obj] Error 1
    'Building file: ../rc_radio.c'
    'Invoking: ARM Compiler'
    "C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.3/bin/armcl" -mv7M3 --code_state=16 --abi=eabi -me --fp_mode=relaxed --include_path="C:/ti/ccsv6/tools/compiler/ti-cgt-arm_5.2.3/include" --include_path="C:/StellarisWare/inc" --include_path="C:/StellarisWare/boards/dk-lm3s9d96" --include_path="C:/StellarisWare/utils" --include_path="C:/StellarisWare" --preinclude="c:/stellarisWare/inc" -g --gcc --define="ccs" --define=PART_LM3S9D96 --display_error_number --diag_warning=225 --preproc_with_compile --preproc_dependency="rc_radio.pp"  "../rc_radio.c"
    Fatal error #1966: cannot open source file "c:/stellarisWare/inc": Invalid argument
    1 catastrophic error detected in the compilation of "../rc_radio.c".
    Compilation terminated.

    If I take the preincludes out the driverlib starts to complain that it doesn't know what tBoolean is. I just had this working!!!! I haven't changed anything!!!

    Why is it so hard for you guys to get your software to work consistently? I spend more time getting code composer studio to behave than I do writing code. And just when I think I have it working it updates and stops working again.