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.
Hi desouza and all others!
Just installed CCS v6.2.0.00048 and MSP430 GCC v4.01.00.00 (standalone version) on Linux (OpenSuSE Tumbleweed).
Created a new CCS Project for the MSP430G2553 and added the following lines of code to main():
#ifdef __GNUC__ #warning "__GNUC__ is actually defined" #ifdef __MSP430G2553__ #warning "__MSP430G2553__ is actually defined" #endif #endif
After a build I do get the following picture (click image to view full size):
I do need to activate "CDT Cross GCC Built-in Compiler Settings" in the project build settings (click image to view full size):
and update the command string from
${COMMAND} ${FLAGS} -E -P -v -dD "${INPUTS}"
to
${COMMAND} ${FLAGS} -mmcu=msp430g2553 -E -P -v -dD "${INPUTS}"
After a rebuild and re-indexing I do get the expected behavior back again - when compared to the TI compiler.
This is the end result which should actually have worked out of the box just by creating the project and inserting the code shown (click image to view full size):
The code shown above was extend to:
#ifdef __GNUC__ #warning "__GNUC__ is actually defined" #ifdef __MSP430G2553__ #warning "__MSP430G2553__ is actually defined" #ifdef __MSP430_HAS_ADC10__ #warning "__MSP430_HAS_ADC10__ is actually defined" #endif #endif #endif
Hi Rafael!
To me it looks like that CCS just misses to configure the correct project settings when MSP430-GCC has been selected.
The "CDT Cross GCC Built-in Compiler Settings" provider has not been selected by CCS. Then it needs to update the command line for that provider.
Can't it just configure the correct project settings? Am I wrong?