• State
  • Locked Locked
  • Replies 13 replies
  • Subscribers 83 subscribers
  • Views 520 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.

CODECOMPOSER: false compilation problems when using eclipsec commnand

Miguel Angel EV
Prodigy 70 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CCSTUDIO, TMS320F28386D, C2000WARE

Hello all

In a CI/CD framework, we are compiling via command line (eclipsec) a 28386D. Sometimes, we get at the end of the compilation log a Project error but when reading the log there is not a concrete code error to fix (I copy an extract of the compilation log below). Besides, If we compile same code again, the error disappears.

The command is the following:


eclipsec -noSplash -data "C:\\myWorkspace_dsp_hemgen3" -application com.ti.ccstudio.apps.projectBuild -ccs.workspace "${WORKSPACE}\\Sistemas" -ccs.buildType full -ccs.configuration MOCKUP_CPU1 >> ..\\Sistemas\\Compilation_MOCKUP_CPU1.log 2>&1

***********************************


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
CCS headless build starting... [Thu Jul 07 15:28:08 CEST 2022]
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

================================================================================
Pre processing...


================================================================================
Building...


**** Clean-only build of configuration MOCKUP_CPU1 for project core_hem_plus ****

"C:\\ti\\ccs1030\\ccs\\utils\\bin\\gmake" -k -j 4 clean -O

gmake: *** No rule to make target 'clean'.

**** Build Finished ****

**** Build of configuration MOCKUP_CPU1 for project core_hem_plus ****

"C:\\ti\\ccs1030\\ccs\\utils\\bin\\gmake" -k -j 4 all -O

C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/script/clean_old_version_outputs.bat DEBUG

Building file: "../APP_CPU1/source/XXXXX.c"
Invoking: C2000 Compiler
"C:/ti/ccs1030/ccs/tools/compiler/ti-cgt-c2000_20.2.5.LTS/bin/cl2000" -v28 -ml -mt --cla_support=cla2 --float_support=fpu64 --idiv_support=idiv0 --isr_save_vcu_regs=on --tmu_support=tmu0 --vcu_support=vcrc -O0 --opt_for_speed=2 --fp_mode=relaxed --include_path="C:/ti/ccs1030/ccs/tools/compiler/ti-cgt-c2000_20.2.5.LTS/include" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/common_modules_plus/Inc/Faults_Warnings_Events" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/APP_CPU1/include" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/APP_CPU1/include/com_up" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/APP_CPU1/include_private" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/APP_CPU1/include_private/com_up" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/common_modules_plus/Inc/Remote_Upgrade" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/common_modules_plus/Inc/Spi_commons/shared_bit_definitions" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/common_modules_plus/Inc/Spi_commons" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/common_modules_plus/Inc/Spi_fast" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/common_modules_plus/Inc/Spi_slow" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Config" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Drivers" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Kernel" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Public" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Services" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Services/AUTOTEST_service" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Services/COM_UP_service" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Services/FILTER_service" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/Services/CONTROL_service" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/TI" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/TI/driverlib" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/TI/f2838xD" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include/TI/VCU" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include_private/Services/AUTOTEST_service" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include_private/Services/FILTER_service_private" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include_private/Services" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include_private/Config" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include_private/Drivers" --include_path="C:/Jenkins/workspace/DSP HEMGEN3/Sistemas/CORE/include_private/Kernel" --advice:performance=all --define=CODEINRAM --define=MOCKUP --define=CPU1 -g --c11 --diag_suppress=10063 --diag_warning=225 --diag_wrap=off --display_error_number --emit_warnings_as_errors --gen_func_subsections=on --gen_data_subsections=on --abi=eabi --ramfunc=off --preproc_with_compile --preproc_dependency="APP_CPU1/source/anti_islanding.d_raw" --obj_directory="APP_CPU1/source" "../APP_CPU1/source/XXXXX.c"
Finished building: "../APP_CPU1/source/XXXXX.c"

.....................


<Linking>
Finished building target: "HEMGEN3_DSP_APP.out"

.................

**** Build Finished ****


================================================================================
CCS headless build complete! 1 out of 1 projects have errors.

  • 0
    TI__Guru** 106210 points

    Hello,

    What TI device are you using CCS for?

    Regards,

    Nick

  • 0 in reply to Nick Saulnier
    Prodigy 70 points

    Thanks Nick,

    It is a TMS320F28386D

  • 0 in reply to Miguel Angel EV
    TI__Guru** 106210 points

    Hello Miguel,

    I am sending your thread to the C2000 team. Please ping the thread if you do not get a response within a couple of days.

    Regards,

    Nick

  • 0 in reply to Nick Saulnier
    TI__Guru 50611 points

    Are you running C2000Ware example or it is the custom project?

  • 0 in reply to Santosh Jha
    Prodigy 70 points

    Hi Santosh, it is a custom project

    Thanks in advance

  • 0 in reply to Miguel Angel EV
    TI__Guru 50611 points

    Miguel,

    What is the error? Can you send full build log? or if you have trim-down projectspec which I can use to reproduce that will help.

    Does it work fine when you build within CCS framework or do you observe same behavior?

    Thanks & Regards,

    Santosh

  • 0 in reply to Santosh Jha
    Prodigy 70 points

    Hi again, the error was related with CODAN static analysis.

    I paste below a fragment, because it is a very large log:

    Building target: "HEMGEN3_DSP_APP.out"
    Invoking: C2000 Linker
    .....
    <Linking>
    Finished building target: "HEMGEN3_DSP_APP.out"

    **** Build Finished ****

    ================================================================================

    --------------------------------------------------------------------------------
    Errors for project 'core_hem_plus' (6183):

    APP_CPU1/include/cla_task.h [line 76]: Type 'uint16_t' could not be resolved
    APP_CPU1/include/cla_task.h [line 77]: Type 'uint16_t' could not be resolved

    ================================================================================

    --------------------------------------------------------------------------------
    Warnings for project 'core_hem_plus' (13):

    CORE/include/TI/device.h [line 317]: Variables should be declared one per line to improve readability


    ================================================================================
    CCS headless build complete! 1 out of 1 projects have errors.




  • 0 in reply to Miguel Angel EV
    Prodigy 70 points

    By the way:

    • We have created a dummy Project, attached to the message. When it is executed  “compilation_problem.bat” it is obtained the log “Compilation_RELEASE_CPU1.log” attached, which has not static analysis Errors (Problems has called in CCS)
    • But building the very same Project with CCS,  thare are many Problems.

     

     

    I have launched several times compilation_problem.bat but with no errors. Yo could also try, please.

     

    Anyways, I think it should show same errors/problems as shown CCS, ¿isn´t it?

     

     We have disabled CODAN analysis in the CI/CD framework for the time being.

  • 0 in reply to Miguel Angel EV
    TI__Guru 50611 points

    Can you start with empty_project from the C2000Ware and then add your code. This way, all the include path and project settings are already taken care.

    C:/ti/c2000/C2000Ware_4_01_00_00/driverlib/f2838x/examples/c28x/empty_projects

  • 0 in reply to Santosh Jha
    TI__Expert 4376 points

    Hello Santosh,

    Please find here below a very simple project showing the issue :

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/171/static_5F00_analisis_5F00_problem.7z

    Thank you!

    Best,

    Guillaume

  • 0 in reply to Guillaume Henri
    TI__Guru 50611 points

    Hi,

    I will take a look at it tomorrow and get back to you.  In quick look, it is able to build it properly, however we see much of message similar to what you mentioned. I will get back to you tomorrow.

    f2838x_headers_nonBIOS_cpu1.cmd"  
<Linking>
Finished building target: "HEMGEN3_DSP_APP.out"
 
Building secondary target: "HEMGEN3_DSP_APP.srec"
Invoking: C2000 Hex Utility
"/Users/a0132919/ti/ccs1120/ccs/tools/compiler/ti-cgt-c2000_21.6.0.LTS/bin/hex2000" --romwidth=16 --diag_wrap=off --motorola=3 -o "HEMGEN3_DSP_APP.srec"  "HEMGEN3_DSP_APP.out" 
Translating to Motorola-S3 format...
   "HEMGEN3_DSP_APP.out" .text ==> .text
   "HEMGEN3_DSP_APP.out" .cinit ==> .cinit
Finished building secondary target: "HEMGEN3_DSP_APP.srec"

    Thanks & Regards,

    Santosh

  • 0 in reply to Santosh Jha
    Prodigy 70 points

    Many thanks Santosh,

    Indeed, I could not reproduce the issue launching the “compilation_problem.bat” in loop :( 

    I hope you have more luck

    The problem appears when, do not why and how, errors from codan appears in the build error log causing a build failed as it was shown days ago.

  • 0 in reply to Miguel Angel EV
    TI__Guru 50611 points

    Hi,

    I turned off the CODAN and then all the warning/error went away. Then I checked with our compiler/CCS team.

    Here is input from CCS team.

    You get an unresolved symbol error from the static analysis tool (CODAN) that is built into CCS/Eclipse.

    We intentionally have CODAN turned off by default in CCS as it falsely reports a lot of issues.  We even have the options pretty hidden in both the project and workspace settings to try to prevent people from turning it on.  We do not recommend using this feature.

    Thanks & Regards,

    Santosh