MSP430F249: Project is not building in CCS 3.2.0.24.2

As per the above snapshot, I could resolve the building error in my project after commenting out the line 32 of Pccom.c (similarly in other 2 files - TimerA_ISR.c and TimerB_ISR.c) under the macro __MSP430__.

But I have question on what is the syntax for defining the interrupt functions for MSP430F249.

Hi Ram,

It looks like most of the errors stem from formatting. I'd take a look at the example code to see the formatting required. It looks like you'll have to handle the errors by scrubbing through and fixing the formats.

Are you missing a Pccom.h file? or does the Pccom.c not include the .h file? I don't know if those declarations are variables or functions but most declarations appear in the .h file associated with your .c. 

Regards,

Luke

Thanks for your suggestions. After updating the vector table with #pragma, the building error is resolved and built successfully.'

Now, I have another issue of downloading the program from CCS Version 3.2.0.24.2 using MSP430 USB-Debug Interface MSP-FET430UIF version V1.4a

It is giving an error message as shown below. But the FET is connected and the green LED glows. There is no issue with FET.

PC Operating system is Windows 7.

Hi Ram,

Can you update to the latest Code Composer Studio? Version 3 is very outdated (current version is 12).

Once this updates you will probably have an update to the MSP-FET430UIF on your first launch. Also to verify you should see the MSP-FET430UIF in your device manager, I would check this to make sure the PC recognizes the connected FET.

Regards,

Luke

Please provide any guide on migrating to latest CCS version. Also, give an overview on the changes to be done from CCS Version 3.2.0.24.2 to Version 12....

Also the PC recognizes it and it shows as one of the COM port under device manager as COM67.

Hi Ram,

CCS version 3 is no longer supported and the last update made to CCS v3 was in 2009. That is 13 years of updates so an overview of changes would be very drastic. There is a specific section on getting CCS V3 on windows 10 which leads me to believe that their might have been an overhaul that your legacy program might need to stay with CCS 3. For converting to CCS 12 I would start by importing the project to CCS 12. If that doesn't work, manual adding the files into an empty CCS 12 is another potential solution. 

I'm going to send this forum to our CCS team in hopes they might have better information. It is the Thanksgiving in the US so it might be a couple days before they can get to this.

Regards,

Luke