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.
i setup ccsv5.1 and can not built any project. My operating system is windows 7.
it gives this error:
C:\ti\ccsv5\utils\bin\gmake -k all
'Building file: ../clock.cfg'
'Invoking: XDCtools'
"C:/ti/xdctools_3_22_04_46/xs" --xdcpath="C:/ti/bios_6_32_05_54/packages;C:/ti/xdctools_3_22_04_46/packages;C:/ti/ipc_1_23_05_40/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r debug -c "C:/ti/ccsv5/tools/compiler/c6000" --compileOptions "-g --optimize_with_debug"
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: ../clock.cfg'
' '
'Building file: ../clock.c'
'Invoking: C6000 Compiler'
"C:/ti/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="C:/ti/ccsv5/tools/compiler/c6000/include" --display_error_number --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="clock.pp" --cmd_file="./configPkg/compiler.opt" "../clock.c"
>> ERROR: Cannot open command file './configPkg/compiler.opt': No such file or directory
Hello,
Which CCS build are you using? It looks like you might be trying to compile a clock Sys/Bios example that is available from New Project wizard. I tried the same thing on my system(it is also a win7) and it built for me without issues. It looks like xs builder is throwing a message about some invalid or missing command. Comparing your console output to mine it looks like ../clock.cfg is not passed to xs build. (see my build console output below). Could you check whether .cfg file is part of your project? Also, if this is just a new project created from a template then could you zip up and attach the project?
C:\CCSInstalls\CCSv5.1_b9000\ccsv5\utils\bin\gmake -k all
'Building file: ../clock.cfg'
'Invoking: XDCtools'
"C:/CCSInstalls/CCSv5.1_b9000/xdctools_3_22_04_46/xs" --xdcpath="C:/CCSInstalls/CCSv5.1_b9000/bios_6_32_05_54/packages;C:/CCSInstalls/CCSv5.1_b9000/ipc_1_23_05_40/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r debug -c "C:/CCSInstalls/CCSv5.1_b9000/ccsv5/tools/compiler/c6000" --compileOptions "-g --optimize_with_debug" "../clock.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring clock.xe66 from package/cfg/clock_pe66.cfg ...
cle66 package/cfg/clock_pe66.c ...
'Finished building: ../clock.cfg'
' '
'Building file: ../clock.c'
'Invoking: C6000 Compiler'
"C:/CCSInstalls/CCSv5.1_b9000/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="C:/CCSInstalls/CCSv5.1_b9000/ccsv5/tools/compiler/c6000/include" --display_error_number --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="clock.pp" --cmd_file="./configPkg/compiler.opt" "../clock.c"
'Finished building: ../clock.c'
' '
'Building target: BIosClockTest.out'
'Invoking: C6000 Linker'
"C:/CCSInstalls/CCSv5.1_b9000/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --display_error_number --diag_warning=225 --abi=eabi -z -m"BIosClockTest.map" --warn_sections -i"C:/CCSInstalls/CCSv5.1_b9000/ccsv5/tools/compiler/c6000/lib" -i"C:/CCSInstalls/CCSv5.1_b9000/ccsv5/tools/compiler/c6000/include" --reread_libs --rom_model -o "BIosClockTest.out" -l"./configPkg/linker.cmd" "./clock.obj" -l"libc.a"
<Linking>
'Finished building target: BIosClockTest.out'
' '
**** Build Finished ****
Hi MartinS,
I have the same problem, and posted it in here: http://e2e.ti.com/support/embedded/f/355/p/149138/540181.aspx#540181
I have solved my problem with your explanation above.
Although I have the .cfg file in my project, it is not seen at the end of the xs builder command line. So I added it manually, and I have built my project successfully.
Thanks,
Selcuk