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.

CODECOMPOSER: compiler problem during project transfer

Part Number: CODECOMPOSER
Other Parts Discussed in Thread: MSP430F5342, MSP-TS430RGZ48B

We have a project from an old version of CCS (project transfer) that I am trying to run.

The microcontroller is:  MSP430F5342

The previous engineer is giving me the following steps to perform to run it this way.

Keep in mind this steps from tutorial:
1-Download same Code Composer Studio version (Version: 7.4.0.00015 Release date: 12 Dec 2017)

Version: 7.4.0.00015
Release date: 12 Dec 2017
https://www.ti.com/tool/download/CCSTUDIO/7.4.0.00015


2-Open "Code Composer Studio 7.4.0" and create a new project folder (Project name:  VPplusV01)
3-Close "Code Composer Studio 7.4.0" and replace created project folder by the project folder we sent you (same name and same path)
4-Open "Code Composer Studio 7.4.0" and compile (project--> build)

Program (debuging) device:

  • Conect MSPFET programmer and cable
  • Connect JTAG interface to probe
  • Keep Pressing ON button all time while firmware is programming
  • Press debug icon

  

  • If this Windows shows, click proceed
  • If programmer is ok you should see something like this

what I am instead getting is the following

There are 2 errors.

one is about the wrong complier and the other about an include problem

Ive reinstalled CCS a few times without any luck.

The Debugger is an MSP FET made via JTAG

I do have a MSP-TS430RGZ48B dev kit and am able to run example and create new projects on this without problems.

Any help is appreciated

  • here are some settings screen shots

    I assume this needs to point somewhere else but I dont know where

  • these are some of the actual paths

  • so one of the problems is that the path for the include does not exist

    I dont know how to fix this 

  • Hi Jim,

    As you suspected, those warnings you are seeing due to differences in your setup between the engineer that gave you the code and yourself. They don't appear to be preventing you from building and loading this old project. You could ignore them and see if they cause you any issues down the line. 

    If you want to try and fix them, for the compiler version warning you could try installing an older version of the MSP430 Code generation tools to use: https://www.ti.com/tool/download/MSP-CGT/4.4.8

    The version used in that old project (4.2.3) doesn't appear to be available for download anymore, so you probably can't eliminate that warning, but using a compiler version closer to the one used originally might prevent issues down the line, or it might cause them. 

    For the DriverLib path warning, you don't appear to have MSP430 DriverLib installed at that location. I actually don't think the default directory for installation is inside the CCS folder anymore. That said, the code you have displayed there may not be using DriverLib based on the lack of errors. When I installed CCSV7 and created a project this include path was not present, so it may be something your colleague configured at some point in the project settings. 

    If you aren't using DriverLib, you could just delete that search path from the include options and processor options and that warning should go away. 

    Best Regards,
    Brandon Fisher

  • hi Brandon

    How do I tell if i am using that driverlib?

    I will try to download the tools you recommend.  

  • Hi Jim,

    I would expect an include directive like the below to be in your project files somewhere, in our examples its almost always above main.

    #include "driverlib.h"

    Best Regards,
    Brandon Fisher

  • Brandon.

    Im still having problems, really could use some help with this.  I feel we are somehow closer though

    The library warning is now gone and we are working on the complier issue.

    I have downloaded the version you have recommended (4.4.8) It was on the very bottom of the link to the webpage that you sent. It must be very old.

    I have updated the complier in the project.  Is this the correct place?

    and the drop down is set to this new version.

    I am still getting the same warning but now for a different compiler

    I am at a loss here to what is keeping this project from running. 

    There should be an LED that is blinking when the project is running.  The LED is not blinking when i enter debug mode but it will blink when I use the MSP flasher utility.

    I also have a DEV board for the same micro.      I can toggle the LED on MSP-TS430RGZ48B dev kit on and off, with the example program in resource expolorer  "MSP430F534x Demo - Timer0_A5, Toggle P1.0, Overflow ISR, 32kHz ACLK"  while in debug mode.     This works the way I would expect it.

    This project that is causing difficult has 2 different sets of files.  Another set of files is for the production environment (for MSP flaser) and this works as expectged.   .   Its just debug mode and the seperate set of files that seems to hang up without error.

    In debug mode, I can try to step through a few lines from the start point.  For example, I can step for the first line.   But then i try to go down 5 lines, it is hanging up as shown.   Any ideas on what is going on?

    Im really confused with this.

  • Hi Jim,

    I am still getting the same warning but now for a different compiler

    Yeah, as you mentioned this is an old compiler. We no longer host version 4.2.3 online, probably just because of age or because it was deemed not as reliable as that 4.4.8 release. That warning will remain because you have a slightly different compiler version, but in theory it doesn't prevent you from building and running the code. That said, if this were me, I would try to get this code to run in the latest version of CCS with the latest compiler, depending on how complex the project is. 

    In debug mode, I can try to step through a few lines from the start point.  For example, I can step for the first line.   But then i try to go down 5 lines, it is hanging up as shown.   Any ideas on what is going on?

    Did you encounter this debug issue when using V16 before?

    This GEL_Go command is the debugger trying to run to a specific address. In this case it seems like your code is never reaching that line for some reason.

    Are you using the Run to line feature, or are you stepping down 5 lines? If the former, if you try to step down to that line does it hang somewhere before that? 

    Best Regards,
    Brandon Fisher