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.

strange problem with defines and CCSv6 - URGENT

Other Parts Discussed in Thread: TM4C123GH6PM, EK-TM4C1294XL, TM4C1294NCPDT

The other day I updated my annual subscription to CCSv6 and I am having problem with the preprocessor descriptions for one project.

I am using some ifdef commends but CCS is not aware of the changes, and the compiled file is generating the same version no matter the define name I use. However the editor is updating (with gray areas properly).

As an example of that, this screen capture. The compiler is hatling at the not defined area!!!

How can I solve this problem?

Thank you.

  • Hello PAk,

    Try a Rebuild All. I once did run into a similar (not a define but an update to one of the files) issue and that solved it.

    Regards

    Amit

  • Amit Ashara said:

    Hello PAk,

    Try a Rebuild All. I once did run into a similar (not a define but an update to one of the files) issue and that solved it.

    Regards

    Amit

    Thank you Amit. But I have tried after cleaning all, rebuilding, restarting code composer and rebooting PC and the problem is still there.

    Any other suggestion?

    NOTE later: It only happens under Debug MODE!!!!

  • Hello PAk,

    Can you please send the information on the CCS version, compiler version (if possible a project that can be imported to CCSv6)

    Regards

    Amit

  •  Version: 6.0.1.00040 

    Compiler: TI v5.1.5 (5.1.8) 

    Then I changed to 5.1.8, now, the a different defined tag is failing, and only in the  file where the main function is....(??)

  • Hello PAk,

    I edited the hello example code as below and I am getting a different error message (but not the same as the one you have). Also how have you set the define in the build flow

    --define=ccs="ccs" --define=FMCW_on --define=PART_TM4C123GH6PM --define=TARGET_IS_TM4C123_RB1

    Regards

    Amit

  • Sorry Amit, forgot to tell you that I am using a 129X device

    -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me -O2 --include_path="C:/ti6/ccsv6/tools/compiler/arm_5.1.8/include" --include_path="C:/CMSIS_v3.20/CMSIS/Include" --include_path="C:/ti/TivaWare_C_Series-2.1.0.12573/examples/boards/ek-tm4c1294xl" --include_path="C:/ti/TivaWare_C_Series-2.1.0.12573" --include_path="C:/CMSIS_v3.20/CMSIS/DSP_Lib/Examples/Common/Include" --gcc

    --define=PART_TM4C1294NCPDT --define=TARGET_IS_TM4C129_RA0 --define=FMCW_on  --define=ccs="ccs"  .............(many other defines).....................................

    --define=ARM_MATH_CM4 --define=__FPU_PRESENT=1 --diag_warning=225 --diag_wrap=off --gen_func_subsections=on --ual

  • Hello PAk

    No change with using a TM4C129X device as well. Can you send over the list of defines?

    Regards

    Amit

  • Consider your assumption might be wrong.

    The grayed-out editor view in this #if / #else / #endif is not the result of the compiler, but a parser which eclipse calls/uses, so you might get fooled. Using another Eclips-based toolchain at my dayjob, I see that kind compiler/parser disagreement ever day.

    When in doubt what the compiler actually sees, add a line like #warning "variable xxx defined, branch yyy taken" to your code, and check the compiler output.

  • Amit Ashara said:

    Hello PAk

    No change with using a TM4C129X device as well. Can you send over the list of defines?

    Regards

    Amit

    Project Attached in a private conversation