SYS/BIOS CCS project build errors

Selcuk Bahtiyar,

Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages. Be sure to search those for helpful information and to browse for the questions others have asked on similar topics.

I am sorry to hear you are having trouble with building this example project. Two things will make it easier for you to get the best answers from the forum: first, since this is a software question specifically about building a SYS/BIOS example project, this question should be posted to the Embedded Software -> BIOS Forum instead of this C66x Multicore Forum for hardware questions (we do not do a good job of explaining the purpose of the various forums, so we understand it is difficult for you to guess at this), and second please add as much detail as possible such as the target device and the steps you went through to reach the failure point of your question.

After my attempt to help you here, we will have this thread moved to the BIOS forum for better help. They might want it in the Code Composer Forum, but I think BIOS is the best place.

The picture is pretty blurry when I try to enlarge it enough to read the device, but it looks like C66x. I opened CCSv5.1.0.09000 and tried the same thing with the EVMC6678 as my target. I was able to build the project successfully the first time without doing anything. When I right-click Properties on the test project I created, click the General item in the left pane and the RTSC tab, I see the following versions:

• XDStools 3.22.4.46
• IPC 1.23.5.40
• SYS/BIOS 6.32.5.54

The only thing I had to select was the Platform, for which I chose ti.platforms.evm6678. The project built the first time.

So my guess is that you either have a problem with your installation or you made a wrong choice somewhere in the New Project sequence.

The steps I went through were:

1. New CCS Project

2. RTSC Config Settings (I did not change any from the default, in my case):

3. Build the project. Here is a slightly cleaned listing from the build:

C:\TI\CCSv51\ccsv5\utils\bin\gmake -k all

'Building file: ../mutex.cfg'
"C:/TI/CCSv51/xdctools_3_22_04_46/xs" --xdcpath="C:/TI/CCSv51/bios_6_32_05_54/packages;C:/TI/CCSv51/ipc_1_23_05_40/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r release -c "C:/TI/CCSv51/ccsv5/tools/compiler/c6000" --compileOptions "-g --optimize_with_debug" "../mutex.cfg"

'Building file: ../mutex.c'
"C:/TI/CCSv51/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="C:/TI/CCSv51/ccsv5/tools/compiler/c6000/include" --display_error_number --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="mutex.pp" --cmd_file="./configPkg/compiler.opt"  "../mutex.c"

'Building target: TaskTest.out'
"C:/TI/CCSv51/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --display_error_number --diag_warning=225 --abi=eabi -z -m"TaskTest.map" --warn_sections -i"C:/TI/CCSv51/ccsv5/tools/compiler/c6000/lib" -i"C:/TI/CCSv51/ccsv5/tools/compiler/c6000/include" --reread_libs --rom_model -o "TaskTest.out" -l"./configPkg/linker.cmd"  "./mutex.obj" -l"libc.a"

'Finished building target: TaskTest.out'

The process was very simple for my case. How does this dffer from your procedure?

Regards,
RandyP

If you need more help, please reply back. If this answers the question, please click  Verify Answer  , below.

Hi Randy,

Thanks for your reply. I have the same environment, so I expect a very simple and clean build as you have.

Hard/soft setup:

TMDXEVM6678L evalution module
CCS v5.1.0.09000
BIOS-MCSDK 02_00_04_16

Project steps:

I followed these steps. I didn't add any header file or library to the project.

Building the Project:

I have tried the same procedure with 2 computers, but the results didn't change. When i build the projects i got the below console log,  do you have any idea?

**** Build of configuration Debug for project taskmutex_test ****

 C:\Program Files\Texas Instruments\ccsv5\utils\bin\gmake -k all
'Building file: ../mutex.cfg'
'Invoking: XDCtools'
"C:/Program Files/Texas Instruments/xdctools_3_22_04_46/xs" --xdcpath="C:/Program Files/Texas Instruments/bios_6_32_05_54/packages;C:/Program Files/Texas
Instruments/ipc_1_23_05_40/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r release -c "C:/Program Files/Texas Instruments/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: ../mutex.cfg'
' '
'Building file: ../mutex.c'

'Invoking: C6000 Compiler'
"C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="C:/Program Files/Texas Instruments/ccsv5/tools/compiler/c6000/include" --display_error_number --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="mutex.pp" --cmd_file="./configPkg/compiler.opt"  "../mutex.c"
>> ERROR: Cannot open command file './configPkg/compiler.opt': No such file or directory
"../mutex.c", line 7: fatal error #5: could not open source file "xdc/std.h"
1 fatal error detected in the compilation of "../mutex.c".
Compilation terminated.

>> Compilation failure

gmake: *** [mutex.obj] Error 1
gmake: Target 'all' not remade because of errors.
**** Build Finished **** 

Setting up the environment was pretty simple. Am I missing any configuration of the software environment or project build steps.

Thanks,
Selcuk

Selcuk,

You may have to wait until someone from the BIOS team joins in. Hopefully that will happen soon, but they probably have a lot of questions since the past week may have been lightly supported due to USA holidays.

I cannot determine any more from this than you can, by both of us reading the 'make' output. The first problem is that the configuro step did not execute, so it has some syntax or path error. Because configuro did not run, there is no compiler.opt file for the next step. The second problem is that xdc/std.h was not found, which you can track down with a desktop search.

Check all of your paths, both in the command lists above and in your CCS Properties pages.

Regards,
RandyP

Selcuk,
your configuro command line is missing the config script at the end. I don't know why would that happen, and the only way I could reproduce it was to go to the project's Build Options->CCS Build->XDCtools, and remove ${inputs} from the dialog there:

Can you check that dialog box and verify that it looks the same as in my project's properties?

I see a similar message reported here: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/148875/538217.aspx#538217 in the Code Composer Studio forum, but there is no answer there yet. Since it's an example project you should be able to delete it and create a project again easily. Have you tried that and do you still get the same error from configuro?

Hi Sasha,

Thanks for the reply. But your recommendation didn't work too. The compiler output is still the same.
By the way, my IPC versions are different from yours(v1.24.0.16 and v1.23.5.40). But I don't think that this is the problem in my case.

I think the problem is related to CCS v5.1.0.9 installation. I have a working project which is built upon the same task mutex example on CCS v5.0.1. That version has came with the TMDXEVM6678L evaluation module.

Thanks,
Selcuk

Hi, 

I am glad that you are unblocked. However, it is not a normal situation to have to manually add source files on build command. We have trouble reproducing this issue on our end, thus could you do us a favour and create a project that has the issue and send us the project? Could you also attach your workspace log? (it should be in workspaceRoot\.metadata and the file is called .log. 

Thank you,

Martin

Hi,

Sorry for the late response.

I have attached the project and the log file.

Project:

2425.taskmutex_test2.rar

Log File:

1362.log.rar