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.

CCS/MSP430F5259: New CCS installation yield "Catastrophic error"

Part Number: MSP430F5259
Other Parts Discussed in Thread: MSP430WARE

Tool/software: Code Composer Studio

Hi, 

I have a working MSP430F5259 CCS project running on my desktop.

I just purchased new laptop and wanted to duplicate my working environment.

I've installed the latest versions of CCS, TI RTOS and MSP430Ware

I've built the drivers for MSP430F5259 as described here  (had to tweak the *.mak file)

On my desktop I've git pushed the project and git pulled it on the laptop.

When trying to build it on the laptop I get a ton of 'catastrophic error' messages, see below an example of such error:

>> Compilation failure
Application/subdir_rules.mk:9: recipe for target 'Application/ChannelManager.obj' failed
"C:/ti/xdctools_3_32_00_06_core/packages/xdc/cfg/global.h", line 39: fatal error #1965: cannot open source file "D:/<Path-to-project>/<ProjName>-Debug/configPkg/package/cfg/<ProjName>_pe430X.h"
1 catastrophic error detected in the compilation of "../Application/ChannelManager.c".
Compilation terminated.
gmake: *** [Application/ChannelManager.obj] Error 1
'Building file: ../Application/EDFFileManager.c'
'Invoking: MSP430 Compiler'
"C:/ti/ccsv7/tools/compiler/ti-cgt-msp430_16.9.1.LTS/bin/cl430" -vmspx --data_model=restricted -Ooff --opt_for_speed=5 --use_hw_mpy=F5 --include_path="C:/ti/ccsv7/ccs_base/msp430/include" --include_path="D:/<Path-to-project>" --include_path="C:/ti/tirtos_msp43x_2_20_00_06/products/msp430_driverlib_2_70_01_01a/driverlib/MSP430F5xx_6xx" --include_path="C:/ti/ccsv7/tools/compiler/ti-cgt-msp430_16.9.1.LTS/include" --include_path="C:/ti/MSP430Ware_3_50_00_04/iqmathlib/include" --include_path="D:/<Path-to-project>/Application" --include_path="D:/<Path-to-project>/Application/NOVAlert" --include_path="D:/<Path-to-project>/Channels" --include_path="D:/<Path-to-project>/Communication" --include_path="D:/<Path-to-project>/Drivers" --include_path="D:/<Path-to-project>/Drivers/HAL" --include_path="D:/<Path-to-project>/DSP" --include_path="D:/<Path-to-shared-Project>/EDFlib" --include_path="C:/ti/msp/MSP430Ware_3_60_00_10/iqmathlib/include" --include_path="D:/<Path-to-shared-project>" --advice:power=all --advice:power_severity=suppress --define=ccs --define=MSP430WARE --define=__MSP430F5259__ --define=ADS131_16BIT_MODE --define=<ProjName> --define=xNOVALERT --undefine=_INLINE -g --printf_support=nofloat --diag_warning=225 --diag_warning=255 --diag_warning=20 --diag_warning=195 --diag_warning=827 --diag_wrap=off --display_error_number --abi=eabi --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU40 --preproc_with_compile --preproc_dependency="Application/EDFFileManager.d" --obj_directory="Application" --cmd_file="configPkg/compiler.opt" "../Application/EDFFileManager.c"

One thing that I noticed is that on the desktop a past MSP430Ware installation (3.50.00.04) is located directly under c:\TI, while the latest MSP430Ware installation is under C:\TI\MSP , 

I see both paths (sepcifcally iqmathlib path, see highlights above) in the error message, however I can't figure out where it comes from as the include option define it only once

Any advise as how to deal with this annoying issue is appreciated.

Thanks in advance.

  • eyalasko said:
    I see both paths (sepcifcally iqmathlib path, see highlights above) in the error message, however I can't figure out where it comes from as the include option define it only once

    Without actually seeing the project itself I can't explain how this happened, but there does appear to be a bit of a mismatch between the include paths set in the Project Properties and what is displayed in the build console. However, I don't think that in itself should be causing the build to fail. I would suggest closely comparing all tool versions and project metadata files to ensure that they match up between the desktop and laptop versions.