Due to the reported problem in CCSv6 / MSP430-FET430UIF Debugger no longer stops at start of program, where a program compiled with gcc_msp430_4.9.14r1_167 worked but when the same program was compiled with gcc_msp430_4.9.14r1_364 it failed, I attempted to repeat the problem.
Used a 6.1.1.00022 installation under Windows in which gcc_msp430_4.9.14r1_167 was installed, and used the CCS App Center to update the MSP430 GCC compiler.
After performing the update and restarting CCS the App Center says the "MSP430 GCC" is now Up to Date. However, the CCS Compiler Discovery is only finding the gcc_msp430_4.9.14r1_167 compiler:
Both compilers are installed:
C:\Users\Mr_Halfword>dir c:\ti_ccs6_1\ccsv6\tools\compiler\*gcc_msp430*
Volume in drive C has no label.
Volume Serial Number is C694-45E6
Directory of c:\ti_ccs6_1\ccsv6\tools\compiler
02/08/2015 10:23 <DIR> gcc_msp430_4.9.14r1_167
03/01/2016 13:57 <DIR> gcc_msp430_4.9.14r1_364
0 File(s) 0 bytes
2 Dir(s) 2,831,269,888 bytes free
When compiling a MSP430 project the CCS Project Properties Compiler version only allowed one GNU compiler - "GNU v4.9.1 (Red Hat)", which used gcc_msp430_4.9.14r1_167 during the compilation.
The directory name of the gcc_msp430_4.9.14r1_167 compiler was changed by adding a leading underscore:
C:\Users\Mr_Halfword>dir c:\ti_ccs6_1\ccsv6\tools\compiler\*gcc_msp430*
Volume in drive C has no label.
Volume Serial Number is C694-45E6
Directory of c:\ti_ccs6_1\ccsv6\tools\compiler
03/01/2016 13:57 <DIR> gcc_msp430_4.9.14r1_364
02/08/2015 10:23 <DIR> _gcc_msp430_4.9.14r1_167
0 File(s) 0 bytes
2 Dir(s) 2,831,794,176 bytes free
When CCS was restarted it then only detected the gcc_msp430_4.9.14r1_364 compiler, which was used during compilation:
i.e. it appears that the CCS 6.1.1 compiler discovery can't tell the difference between the gcc_msp430_4.9.14r1_167 and gcc_msp430_4.9.14r1_364 compiler installations, since they both get identified as "GNU v4.9.1 (Red Hat)".
