• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 56 subscribers
  • Views 15868 views
  • Users 0 members are here
Support feedback
Options
Options

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 v5.0 - fatal error: could not open source file "xdc/std.h"

Evan Haas
Intellectual 435 points

I have just installed Code Composer v5.0.2 and imported a project that I've been using with v4.  I'm getting an error: fatal error: could not open source file "xdc/std.h".  I am including <xdc/std.h> in my main.h file.  In the build properties for the project, I do have C:\Program Files (x86)\Texas Instruments\ccsv5\xdctools_3_20_08_88\packages\xdc as listed, which is where the std.h file is located.  Also, if I ctl-click on the <xdc/std.h> in main.h, then the std.h file is displayed, so it seems like the build tools should be able to find the file.  How do I let the compiler know the location of this file?

  • 0
    TI__Guru**** 161560 points

    What happens if you add "C:\Program Files (x86)\Texas Instruments\ccsv5\xdctools_3_20_08_88\packages" to your include paths.  i.e. without the \xdc

  • 0 in reply to JohnS
    Intellectual 435 points

    Well, it still doesn't compile, but I do get a different error:

    "C:/Program Files (x86)/Texas Instruments/ccsv5/xdctools_3_20_08_88/packages/xdc/std.h", line 76: fatal error: #error xdc_target_types__ must be defined to name a target-specific header containing definitions of xdc_Int8, xdc_Int16, ...

  • 0 in reply to Evan Haas
    Expert 2030 points

    I am getting same errors from project imported from ccs v3.

     

  • 0 in reply to RV
    TI__Guru**** 161560 points

    I can see the same thing when creating a BIOS6 project in v4 and importing into v5.

     

    When I look at the console it shows some odd feedback at the beginning that makes it seem like one of the build tools is being called with the wrong parameters.  Let me look into this.

     

    Usage: xs xdc.tools.configuro [--help]

    [-v | -q]

    [-@ optionsfile]

    [-o outdir]

    [-b config_bld | -c codegen_dir | --cb]

    [-t target] [-p platform[:instance]] [-r profile]

    [-Dname=value]

    [-w | -x regexp]

    [--rtsName pkg_name]

    [--cfgArgs args_string]

    [--linkTemplate linker_template]

    [--tcf] [--bios5] [--pkg] [--generationOnly]

    [--compileOptions compile_options_string]

    [--oc compiler.opt] [--ol linker.cmd]

    infile.cfg

    'Finished building: ../hello.cfg'

  • 0 in reply to JohnS
    Intellectual 435 points

    have you had any luck getting to the problem?

  • 0 in reply to Evan Haas
    TI__Guru**** 161560 points

    Evan,

    I heard back from the dev team today.  The problem is coming about because the project system in 4.2.2/3 is in some ways "newer" than what is in 5.0.2/3.  i.e. the 4.x stream is still evolving.  The problem doesn't exist when importing into CCSv5.1.

    So an option is to move to CCSv5.1.  It is not a production tool yet but it is available.  Is that something you would want to pursue?

    Regards,

    John

  • 0 in reply to JohnS
    Intellectual 435 points

    sure, I'm happy to give that a try.

  • 0 in reply to Evan Haas
    TI__Guru**** 161560 points

    You can get the 5.1 M4 build here http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

    We are doing monthly milestone builds for 5.1 so there will be another build in 2-3 weeks.

     

    John

  • 0 in reply to JohnS
    Intellectual 435 points

    awesome, this version built and ran my projects with no issues.

  • 0 in reply to JohnS
    Prodigy 220 points

    Hi Johns

    I have similiar issue of importing ccs4.2.3 to ccs5.0.3 as the attached  building log (fftcTest.build.log) after I directly added the rtsc path into the include option for compiling. I also created a hello RTSC example pjt  from the wizrad and got the same compiling error.  Well there woll be no compiling error if I choose custom c6000 device but not generic c66x from the CCS build ->general option, but in this case, instead I got linking error as the attached log hello.build.log.

    Altough ccs5.1 can get this issue resolved, could you provide any workground for ccs 5.0 too if there is any? (I got suggested that ccs 5.0.3 is a better choice since ccs5.1 may not be so stable as it should be currently)

    BTW: could I have any suggestions on how to stop the disgusting "refresh workspace"in the building process which slows the whole comping progress greatly(I can't manually stop it once fo

    1447.fftcTest.build.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    **** Build of configuration Debug for project fftcTest ****
    C:\Program Files\Texas Instruments\ccsv5\utils\gmake\gmake -k all
    'Building file: ../fftcTest.cfg'
    'Invoking: XDCtools'
    "C:/Program Files/Texas Instruments/xdctools_3_20_08_88/xs" --xdcpath="C:/Program Files/Texas Instruments/bios_6_31_04_27/packages;X:\4gbts_msp\Platform\Export\packages\npc\platforms;C:/Program Files/Texas Instruments/xdais_7_20_00_07/packages;C:/Program Files/Texas Instruments/xdais_7_20_00_07/examples;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66_big_endian -p TCI6616_BBU -r whole_program -c "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000" -Dconfig.importPath=X:/4gbts_msp/Platform/Export\configuration TCI6616_BBU "../fftcTest.cfg"
    Usage: xs xdc.tools.configuro [--help]
    [-v | -q]
    [-@ optionsfile]
    [-o outdir]
    [-b config_bld | -c codegen_dir | --cb]
    [-t target] [-p platform[:instance]] [-r profile]
    'Finished building: ../fftcTest.cfg'
    [-Dname=value]
    ' '
    'Building file: ../MSP_BuildEnvironment.cpp'
    [-w | -x regexp]
    [--rtsName pkg_name]
    [--cfgArgs args_string]
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    r ever)?


    Thanks very much!

    BR/Gavin

    6740.hello.build.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    **** Build of configuration Debug for project hello ****
    C:\Program Files\Texas Instruments\ccsv5\utils\gmake\gmake -k all
    'Building file: ../hello.cfg'
    'Invoking: XDCtools'
    "C:/Program Files/Texas Instruments/xdctools_3_20_08_88/xs" --xdcpath="C:/Program Files/Texas Instruments/bios_6_31_04_27/packages;C:/Program Files/Texas Instruments/ipc_1_22_03_23/packages;X:\4gbts_msp\Platform\Export\packages\npc\platforms;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66_big_endian -p TCI6616_BBU -r whole_program -c "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000" "../hello.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring hello.pe66e from package/cfg/hello_pe66e.cfg ...
    cle66e package/cfg/hello_pe66e.c ...
    lnke66e hello.pe66e ...
    'Finished building: ../hello.cfg'
    ' '
    'Building target: hello.out'
    'Invoking: C6000 Linker'
    "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --diag_warning=225 --big_endian --abi=eabi -z -m"hello.map" --warn_sections -i"C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/lib" -i"C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --reread_libs --rom_model -o "hello.out" -l"./configPkg/linker.cmd" "./hello.obj"
    <Linking>
    undefined first referenced
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    8765.fftcTest.build.log
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    **** Build of configuration Debug for project fftcTest ****
    C:\Program Files\Texas Instruments\ccsv5\utils\gmake\gmake -k all
    'Building file: ../fftcTest.cfg'
    'Invoking: XDCtools'
    "C:/Program Files/Texas Instruments/xdctools_3_20_08_88/xs" --xdcpath="C:/Program Files/Texas Instruments/bios_6_31_04_27/packages;X:\4gbts_msp\Platform\Export\packages\npc\platforms;C:/Program Files/Texas Instruments/xdais_7_20_00_07/packages;C:/Program Files/Texas Instruments/xdais_7_20_00_07/examples;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66_big_endian -p TCI6616_BBU -r whole_program -c "C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000" -Dconfig.importPath=X:/4gbts_msp/Platform/Export\configuration TCI6616_BBU "../fftcTest.cfg"
    Usage: xs xdc.tools.configuro [--help]
    [-v | -q]
    [-@ optionsfile]
    [-o outdir]
    [-b config_bld | -c codegen_dir | --cb]
    [-t target] [-p platform[:instance]] [-r profile]
    'Finished building: ../fftcTest.cfg'
    [-Dname=value]
    ' '
    'Building file: ../MSP_BuildEnvironment.cpp'
    [-w | -x regexp]
    [--rtsName pkg_name]
    [--cfgArgs args_string]
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to gavin peng
    TI__Guru** 116020 points

    Gavin,

     'xdc_target_types__' must be defined to name a target-specific header file (e.g., ti/targets/std.h) that has definitions for the basic types:

     xdc_Int8, xdc_Int16, ...

     For example, to build for a target in the ti.targets package you should

     add the following option to your compiler's command line:

     -D xdc_target_types__=ti/targets/std.h

    If you have set the include paths correctly and if you define the above you will not see the error in CCS 5.0

    Please try this and let us know if this resolves your error.

     

    Regards,

    Rahul

     

     

  • 0 in reply to JohnS
    Prodigy 110 points

    I have code composer  Version: 5.1.0.09000 and have been trying to get the uart_echo example project compiled on my system.  I get the compile error:

    D:\ti\ccsv5\utils\bin\gmake -k all
    'Building file: C:/StellarisWare/boards/ek-lm3s9b92/uart_echo/startup_ccs.c'
    'Invoking: TMS470 Compiler'
    "D:/ti/ccsv5/tools/compiler/tms470/bin/cl470" -mv7M3 -g -O2 --gcc --define=ccs --define=PART_LM3S9B92 --define=TARGET_IS_TEMPEST_RB1 --include_path="D:/ti/ccsv5/tools/compiler/tms470/include" --include_path="C:/projects/9200/uart_echo/inc" --include_path="C:/projects/9200/uart_echo/../StellarisWare/inc" --include_path="C:/projects/9200/uart_echo/../../../.." --include_path="C:/projects/9200/uart_echo" --include_path="c:/StellarisWare/" --diag_warning=225 -me --gen_func_subsections --abi=eabi --code_state=16 --ual --preproc_with_compile --preproc_dependency="startup_ccs.pp"  "C:/StellarisWare/boards/ek-lm3s9b92/uart_echo/startup_ccs.c"
    'Finished building: C:/StellarisWare/boards/ek-lm3s9b92/uart_echo/startup_ccs.c'
    ' '
    'Building file: C:/StellarisWare/boards/ek-lm3s9b92/uart_echo/uart_echo.c'
    'Invoking: TMS470 Compiler'
    "D:/ti/ccsv5/tools/compiler/tms470/bin/cl470" -mv7M3 -g -O2 --gcc --define=ccs --define=PART_LM3S9B92 --define=TARGET_IS_TEMPEST_RB1 --include_path="D:/ti/ccsv5/tools/compiler/tms470/include" --include_path="c:StellarisWare/" --include_path="C:/projects/9200/uart_echo/../../../.." --diag_warning=225 -me --gen_func_subsections --abi=eabi --code_state=16 --ual --preproc_with_compile --preproc_dependency="uart_echo.pp"  "C:/StellarisWare/boards/ek-lm3s9b92/uart_echo/uart_echo.c"
    "C:/StellarisWare/boards/ek-lm3s9b92/uart_echo/uart_echo.c", line 26: fatal error: could not open source file "inc/hw_memmap.h"
    1 fatal error detected in the compilation of "C:/StellarisWare/boards/ek-lm3s9b92/uart_echo/uart_echo.c".
    Compilation terminated.

    I have tried adding all kinds of include formats in every syntax I can think of to try to get it able to see the file hw_memmap.h and have copied the file into other directories - but none of it works.  At the time I imported this project, I remember getting some errors.  I though it would be easier to get one of the example projects for EKK-LM3S9B92 evaluation kit to compile and run.

    Eric Krieg