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?