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 project migration problem : CCS 3.3 -> CCS 5.1

Hi, folks,

I'm trying to build the 'userspace-dspbridge' dsp sample code under CCS environment.

I managed to compile the code under CCS 3.3 environment, but failed to test it with my beagleboard-XM because CCS 3.3 does not support XDS100 series JTAG. 

So, I imported the CCS 3.3 project to CCS 5.1 and encountered the following error message when I build it;

**** Build of configuration Debug for project ddspbase ****

/workspace/devel/TI/CCS/ccsv5/utils/bin/gmake -k all
Building file: ../ddspbase.tcf
Invoking: TConf Script Compiler
"/workspace/devel/TI/CCS/bios_5_33_04/xdctools/tconf" -b -Dconfig.importPath="/workspace/devel/TI/CCS/bios_5_33_04/packages;
/workspace/devel/TI/userspace-dspbridge/source/dsp;/workspace/devel/TI/userspace-dspbridge/source/dsp/ti/dspbridge/dsp;
/workspace/devel/TI/userspace-dspbridge/source/dsp/ti/dspbridge/dsp/tconf;/workspace/devel/TI/userspace-dspbridge/source/dsp/ti/dspbridge/dsp/tconf/platforms;
/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/packages;
/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/framework_components_1_10_04/packages-bld;
/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/framework_components_1_10_04/fctools/packages;
/workspace/devel/TI/userspace-dspbridge/source/samples/dsp;" -Dconfig.chipType=3430 "../ddspbase.tcf"

Adding Framework Components for platform: 3430
Enabling power management...
Caution : Hibernation timeout value is not a multiple of TIMERPERIOD
Enabling PWRM Load Monitor...
Finished building: ../ddspbase.tcf

Building file: ddspbasecfg.s??
Invoking: C6000 Compiler
"/workspace/devel/TI/CCS/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6400+ -g --define=_DBG_;DBC_ASSERTS=1;
_DEBUG --include_path="/workspace/devel/TI/userspace-dspbridge/source/dsp/ti/dspbridge/dsp/bridge_product/exports/include"
--include_path="/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/framework_components_1_10_04/packages-bld"
--include_path="/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/framework_components_1_10_04/packages-bld/ti/sdo/fc/dskt2"
--include_path="/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/packages" --include_path="/workspace/devel/TI/CCS/ccsv5/tools/compiler/c6000/include"
--include_path="/workspace/devel/eclipse_pjt/ddspbase/Debug" --include_path="/workspace/devel/TI/CCS/bios_5_33_04/packages/ti/bios/include"
--include_path="/workspace/devel/TI/CCS/bios_5_33_04/packages/ti/rtdx/include/c6000" --include_path="/workspace/devel/TI/CCS/xdais_7_21_01_07/packages/ti/xdais"
--include_path="/include" --display_error_number --diag_warning=225 --abi=coffabi --preproc_with_compile --preproc_dependency="ddspbasecfg.pp" "ddspbasecfg.s62"

>> ERROR: no source files, nothing to do
/bin/sh: _DEBUG: not found
gmake: *** [ddspbasecfg.obj] Error 127

I don't understand what >> ERROR: no source files, nothing to do means exactly. So, I searched the forum and found two similar queries before.

http://e2e.ti.com/support/development_tools/compiler/f/343/t/119304.aspx

This one is very similar to my case. But, it seems that the thread ends up without any final conclusion. (Also, in my case, I do not have any luck with the command line compilation
which was a workaround for the original poster.

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

This is a second case. For me, I don't use any c++ code(I mean, in the original code I downloaded), so it seems not to be my case.

Is there anybody who can help me with my problem? For me, if required, I can upload the entire project because I stared this based on the open source.  :-)

Ilkyoung.

  • Hello,

    Usually when such an error occurs after importing a legacy *.pjt, it is because the import had some errors and some of your build options (usually search paths for the compiler and linker). Carefully check your build options. In your case check your include search paths for the compiler. They all start with "/workspace". It looks like it got truncated somehow.

    Thanks

    ki

  • Hello, Kisoo.

    Thank you so much for your responding. Actually, I did not expect such prompt responding from anybody because it was weekend.  ;-)

    As you pointed out, I was suspicious that the compiler could not find the source files at all, for some reason. When I see the makefile script output as follows,

    **** Build of configuration Debug for project ddspbase ****

    /workspace/devel/TI/CCS/ccsv5/utils/bin/gmake -k all
    Building file: ddspbasecfg.s62
    Invoking: C6000 Compiler
    "/workspace/devel/TI/CCS/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6400+ -g --define=_DBG_;DBC_ASSERTS=1;_DEBUG
    --include_path="/workspace/devel/TI/userspace-dspbridge/source/dsp/ti/dspbridge/dsp/bridge_product/exports/include"
    --include_path="/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/framework_components_1_10_04/packages-bld"
    --include_path="/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/framework_components_1_10_04/packages-bld/ti/sdo/fc/dskt2"
    --include_path="/workspace/devel/TI/userspace-dspbridge/source/dsp/bdsptools/packages"
    --include_path="/workspace/devel/TI/CCS/ccsv5/tools/compiler/c6000/include"
    --include_path="/workspace/devel/eclipse_pjt/ddspbase/Debug"
    --include_path="/workspace/devel/TI/CCS/bios_5_33_04/packages/ti/bios/include"
    --include_path="/workspace/devel/TI/CCS/bios_5_33_04/packages/ti/rtdx/include/c6000"
    --include_path="/workspace/devel/TI/CCS/xdais_7_21_01_07/packages/ti/xdais"
    --include_path="/include"
    --display_error_number --diag_warning=225 --abi=coffabi --preproc_with_compile
    --preproc_dependency="ddspbasecfg.pp" "ddspbasecfg.s62"

    >> ERROR: no source files, nothing to do
    /bin/sh: _DEBUG: not found
    gmake: *** [ddspbasecfg.obj] Error 127

    The compiler seems to say that it can not find the source file 'ddspbasecfg.s62'. The common part of '/workspace/devel' is part of the directory structure for my beagle board based development project.

    There are three points I don't quite understand. It would be great if you can answer some of them.

    1. I do have 'ddspagecfg.s62' file. 

    zooliet@vb-ubuntu-10:/workspace/devel/eclipse_pjt/ddspbase/Debug$ ls -l
    total 636
    -rw-r--r-- 1 zooliet zooliet 471 2012-02-19 04:53 ccsObjs.opt
    -rw-r--r-- 1 zooliet zooliet 444 2012-02-19 04:53 ccsSrcs.opt
    -r--r--r-- 1 zooliet zooliet 428113 2012-02-18 03:59 ddspbase.cdb
    -rw-r--r-- 1 zooliet zooliet 5142 2012-02-18 03:59 ddspbasecfg_c.c
    -rw-r--r-- 1 zooliet zooliet 13035 2012-02-18 03:59 ddspbasecfg.cmd
    -rw-r--r-- 1 zooliet zooliet 701 2012-02-18 03:59 ddspbasecfg.h
    -rw-r--r-- 1 zooliet zooliet 6644 2012-02-18 03:59 ddspbasecfg.h62
    -rw-r--r-- 1 zooliet zooliet 89000 2012-02-18 03:59 ddspbasecfg.s62
    -rw-r--r-- 1 zooliet zooliet 29065 2012-02-18 03:59 ddspbasecfg.xml
    -rw-r--r-- 1 zooliet zooliet 4913 2012-02-19 04:53 makefile
    -rw-r--r-- 1 zooliet zooliet 249 2012-02-19 04:53 objects.mk
    -rw-r--r-- 1 zooliet zooliet 1859 2012-02-19 04:53 sources.mk
    -rw-r--r-- 1 zooliet zooliet 30973 2012-02-19 04:53 subdir_rules.mk
    -rw-r--r-- 1 zooliet zooliet 3634 2012-02-19 04:53 subdir_vars.mk

        This file is generated when I compile my ddspbase.tcf file as you can see above. However, the file is located at the '$PJT_ROOT/Debug' directory. Do I have to instruct the compiler to look for the 'Debug' directory?

        If then, how can I do that? I presume that 'Debug' directory is something like mandatory place for CCS to search for. Also, this *cfg.s62 file is an automatically generated one. Am I wrong?

    2. I cannot find the 'ddspbasecfg.pp' file anywhere in the project directory. Is it O.K.? or do you think this is contributing to my problem as well?

    3. The last part of my include path is designated as '/include' above.

        What is configured in my CCS exactly is "${C6000_CSL_CG_ROOT}/include" and '/include' is what I actually get.

        Where is ${C6000_CSL_CG_ROOT} defined? The only path that is not valid in my 'include options' of 'C6000 compiler' section is it.

        (I cannot upload the screenshot of my CCS 5.1 property window. I don't know if this is because of the terribly low internet speed here in Qatar or problem with my Mac.)

    Have a wonderful weekend.

    Ilkyoung.

  • another possible reason for the

    >> ERROR: no source files, nothing to do

    message can be a fault in the compiler settings, for example a " too much in an include path. An error in a path environment variable definition lead to the following instruction:

    -include_path="D:/prj/viper"/include"

    resulting in "ERROR: no source files, nothing to do"

  • Thanks; I too faced a similar issue & by removing the unmatched ", i could fix the problem; the issue here can also come in general for any unmatched " in the macros, include paths, library search paths etc;