• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 2429 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

ERROR: no source files, nothing to do

korobchenko andrej korobchenko andrej
Intellectual 395 points
Other Parts Discussed in Thread: OMAPL138

Excuse for my English. I try to create any project in CCS 4.2.4.00033. At assemblage there is a message that the compiler cannot find source codes of configuration files. An example:

'Building file: aco_modcfg.s??'

'Invoking: Compiler'

"C:/ccs4/ccsv4/tools/compiler/C6000 Code Generation Tools 7.3.1/bin/cl6x" -mv6740 -g --include_path="C:/ccs4/ccsv4/tools/compiler/C6000 Code Generation Tools 7.3.1/include" --include_path="H:/MyWorks/worcs/acoustic/project_analog_board/soft/soft_of_acoustic_board/program 6/Debug" --include_path="H:/MyWorks/worcs/acoustic/project_analog_board/soft/soft_of_acoustic_board/program 6/Debug" --include_path="H:/MyWorks/worcs/acoustic/other/edma3_lld_01_11_02_05/packages/ti/sdo/edma3/../../../" --include_path="H:/MyWorks/worcs/acoustic/other/pspdrivers_01_30_01/packages/ti/pspiom/../../" --include_path="H:/MyWorks/worcs/acoustic/other/edma3_lld_01_11_02_05/packages/ti/sdo/edma3" --include_path="H:/MyWorks/worcs/acoustic/other/pspdrivers_01_30_01/packages/ti/pspiom" --include_path="C:/ccs4/bios_5_41_10_36/packages/ti/bios/include" --include_path="C:/ccs4/bios_5_41_10_36/packages/ti/rtdx/include/c6000" --diag_warning=225 --abi=coffabi --preproc_with_compile --preproc_dependency="aco_modcfg.pp"  ""

>> ERROR: no source files, nothing to do

'Finished building: aco_modcfg.s??'

Inform, please, that I do not so. Thanks. 

  • 0
    TI__Guru**** 173310 points

    Is this a project you created in CCS or a TI example project? It looks like the BIOS generated file (.sxx) is not being passed correctly to the build command.

    Does this file (aco_modcfg.s62) actually exist in the \Debug folder within the project folder? Were there errors when building the BIOS config file (.tcf) that may have prevented the generation of the .s62 file (check the full output in the build console)?

  • 0 in reply to AartiG
    Intellectual 395 points

    Thanks that have responded! I used empty Example of DSP/BIOS v5.xx Examples and one of existing projects DSP/BIOS v5.xx Examples. The result in both cases was identical. After reinstallation CCS all has changed. To the best ! Now this error arises only occasionally at performance of command Build Project. However it arises always at performance of command Rebuild Project. Now it for me is not important. Now there was one more strange error. At attempt to build the project the compiler deduces:

     

    undefined first referenced 
    symbol in file 
    --------- ---------------- 
    _SpiUserInit ./aco_modcfg.obj 
    _Spi_localEdmaTransfer H:\MyWorks\worcs\acoustic\other\pspdrivers_01_30_01\packages\ti\pspiom\spi\lib\OMAPL138\Debug\ti.pspiom.spi_EDMA_OFF.a674<Spi.obj>
    edma3init() ./main_Acoustic.obj 
    _mcaspUserInit ./aco_modcfg.obj 
    _receive_Data ./aco_modcfg.obj 

    error: unresolved symbols remain
    error: errors encountered during linking; "program11.out" not built

    >> Compilation failure
    gmake: *** [program11.out] Error 1
    gmake: Target `all' not remade because of errors.
    Build complete for project program11

     

    Are not resolved a part of functions which I declared mainly in a configuration file aco_mod.tcf. These are functions of initialization of drivers of devices. For example, here a screenshot of a window of program Configuration Tool :

      Here properties of the driver mcasp0 are shown. Initialization function is  mcaspUserInit. Here function is defined:

    This part map a file which causes in me bewilderment:

    It is created two symbols _mcaspUserInit which is not defined, and _mcaspUserInit __ Fv which, on the contrary, is defined. Why it has been created two symbols? What means addition of suffix Fv to a function name? 

    In advance I thank for the answer!

  • 0 in reply to korobchenko andrej korobchenko andrej
    TI__Guru**** 173310 points

    Do you have C++ source files in your project? If so, please see this wiki article and the recommendation on declaring functions with extern "C" when mixing C++ code with C code or BIOS:
    http://processors.wiki.ti.com/index.php/Overview_of_C%2B%2B_Support_in_TI_Compilers#Name_Mangling

    You can also take a look at the "bigtime" BIOS 5 example included with CCS as it uses C++.

  • 0 in reply to AartiG
    Intellectual 395 points

    Yes, I use C ++ source codes. Thanks for the recommended documents. I will attentively study them.

  • 0 in reply to korobchenko andrej korobchenko andrej
    Intellectual 395 points

    Thanks for the help. The reason was in Name Mangling. I am completely satisfied by the answer.

  • 0 in reply to korobchenko andrej korobchenko andrej
    Expert 1575 points

    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"