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.

automatic add include_path="!" -g --define=! --diag_warning=! @mutex in flag set c2000 compiler

Genius 5910 points
Other Parts Discussed in Thread: CONTROLSUITE

The hardest part of development with CCS is keep you environment running especially with Intraspin.  Writing code shout be nice for a change.

So new day new problems.

 If you go to C2000 compiler properties it automatically adds the following options:

  --include_path="!" -g --define=! --diag_warning=! @mutex

Where the compiler fails on:

"c:/ti/ccsv6/tools/compiler/c2000_6.2.8/bin/cl2000" -v28 -ml -mt --cla_support=cla0 --float_support=fpu32 --tmu_support=tmu0 --vcu_support=vcu0 -O3 --opt_for_speed=3 --include_path="c:/ti/ccsv6/tools/compiler/c2000_6.2.8/include" --include_path="I:/workspace/sw/modules/hal/boards/drv8312kit_revD/f28x/f2806x/src" --include_path="I:/workspace/sw/solutions/CremerServo/boards/drv8312kit_revD/f28x/f2806xM/src" --include_path="I:/workspace" --include_path="C:/ti/controlSUITE/device_support/f2806x/v135/F2806x_common/include" --include_path="C:/ti/controlSUITE/device_support/f2806x/v135/F2806x_headers/include" --include_path="C:/ti/controlSUITE/device_support/f2806x/v135/MWare" -g --define=FAST_ROM_V1p6 --define=QEP --diag_warning=225 --diag_warning=! --display_error_number --preproc_with_compile --preproc_dependency="wdog.pp"  "I:/workspace/sw/drivers/wdog/src/32b/f28x/f2806x/wdog.c"
Command-line error: invalid error tag in diagnostic control option: !
1 catastrophic error detected in this compilation.
Compilation terminated.

So where  is: --diag_warning=! defined?

  • Is this with one of the example projects provided by TI? If so, could you let us know which one?

  • If you set something in C2000 compiler -> Set additional Flags.

     CCS change it "automatically"  in  C2000 Compiler > advance options (-> Diagnostic Options)

     So If you change some compiler option. And you like tot change it back,  you have to go to a complete different location in the configure menu. That is a good Idea?

  • If you set additional options via the "Set additional flags" button, then yes they will be automatically reflected in the GUI options. This is done so as to show the users what their current options are, including what they see in the GUI.

    If you then want to change it again, you can either do so from the GUI or go back into "Set additional flags" and edit it from there. Is this what you are referring to or am I missing something?

  • If you add options to "Set additional flags" it add them also in the advanced option. but If you remove them, there aren't removed from the advanced options.  So you have them manually remove them from the advanced options.

  • evs said:

    If you add options to "Set additional flags" it add them also in the advanced option. but If you remove them, there aren't removed from the advanced options.  So you have them manually remove them from the advanced options.

    I cannot reproduce this. I added a new option via "Set additional flags" and confirmed that it showed it under Advanced Options in the GUI. Then I went back to "Set additional flags" and deleted the entry and found that it was removed from GUI Advanced Options as well.

    If you can consistently reproduce this, please provide detailed steps that we can follow to duplicate the behavior.

  • I also tried to reproduce it. If you type the command correctly then is works correctly.

     But I remembered  that I copy and pasta a lot of data in the field. Because It breaks command in parts.  it is easy to overlook what it wrong in the line.

    So I think the problem is, when you make a typo in the command line.  And CCS try to convert it to the correct advance page.

    I don't know what the incorrect command was I used. But put this:   --diag_warning="  in the middle of you're options and see what happens.

    If I experience the problem again, I let you know.

    Thanks for trying to solve the problem and explaining it to me.