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.

Evaluation Version of CCS5 compatibility with MSP430F5172

Other Parts Discussed in Thread: MSP430F5172, MSP430F5151

I have an application that I used the F5151 for and the free code-linited version of CCS5 worked fine for that. I switched over to the F5172 due to its easy availablity and now CCS5 "coughs" at this saying chip not recognized or authorized. So this maybe due to the F5172's 32K program memory which exceeds the 16K code limit? My application program size is only 8K. My CCS5 version is 5.1.1.00031 and am using the Launchpad and Spy-Bi-Wire to program.

  • Hi Jim,

    the limit is purely on the code size, not the device size.    Have you verified the code size and optimization settings?

    I would recommend upgrading to the latest version (code limited is still available).  I would install a full fresh installation of v5.4 in a new simple directory.   One main reason ... there have been some fixes to the compiler which might actually help your code size.  

    Please keep us informed.

    Best Regards,
    Lisa

  • Lisa,

    Tks.. I will do as u suggest and report back. Yes, the code size is less than 16K . I am able to load and debug the same code into a F5151 part.  So there maybe some PCB issues on my DIY board. I'm checking into that as well.

    Jim

  • Hi Jim,

    ok, please keep us informed.

    Best Regards,
    Lisa

  • Hi Lisa,

    Thanks to your suggestion to install CCS v5.4, I am now able to load my program into the F5172. When I first tried v5.4 , it failed same as v5.1 but the error message I got had some additonal info in it that v5.1 did not have. It said that my "Target Configuration (MSP430F5151) did not match the actual target (MSP430F5172)". So I realized that I didn't change my CCS5 configuration from the old F5151 I was using to the new F5172 I'm now using. All I had done was change the header file info from msp430f5151.h to msp430f5172.h. Once I sorted all that out (and it wasn't all that easy), I'm "away to the races". I basically started a whole new project designating the F5172 and imported all the C source files and H header files from the F5151 project then did a Build and Debug on them. That's probably what I should have done in the first place! I've noticed also that I get a whole slew of new "Warnings" that I didn't get before. These warnings are all to do with missing ISR handlers. I assume I can ignore these since I'm not using the Interrupt vectors of concern.

    So if it wasn't for the additional info in the error message about the target config not matching the actual target, I would still be floundering! I knew the hardware was working since CCS5 was able to determine that the actual target was an F5172.

    So thanks again and we can close out this thread!

    Jim

  • Hi Jim,

    great, very glad to hear!

    Thanks for the update and all the best with development.

    Best Regards,

    Lisa