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.

CCS: Moving to CCS v8 - Project does not get to main

Other Parts Discussed in Thread: MSP430F5259

Tool/software: Code Composer Studio

Hi, 

A pretty extensive MSP430/TI-RTOS project is running fine in CCSv7.4 (compiler 16.9.6)

When importing it to CCSv8 (compiler 18.1.1) the project still builds without error.

However, when being loaded into the platform It seems as it starts running instantly, not breaking at main() (even if I set a breakpoint) and the 'pause' icon is grayed out, only 'stop' is enabled.

'Hold watchdog during init' option is set to 'on'.

I looked for CCSv8 porting guideline but didn't find any...

Any advice is appreciated. Thanks

  • Are 7.4 and 8.0 installed on the same machine?  This is not an issue but if they are then there are a couple things we can try.

    First lets try configuring your project in 8.0 to use the 16.9.6 compiler from CCSv7.4.

    To do that you can go into the preferences dialog and using the settings below you can add the path to the 16.9.6 compiler and CCS will discover it.  Note that the compiler would be in something like ccsv7/ccs_base/tools/compiler/

    Once that is done you can change the project to use the compiler by changing the properties of the project here:

    Once that is done build and try to debug the project.  If this works then we know there is something going on with the new compiler that is triggering the issue.  If it is not working then we have something else to try.

    If the above did not work then lets try loading the program that was built by CCSv7.4 into your 8.0 debug session.  One way to do this is to just launch the debugger normally and then click on the load program button and select the program from 7.4.  However if the debugger is getting into a bad state by running the 8.0 version of the program we can avoid that by:

    Open the Target Configurations View from the View menu.  Expand your project and find the target configuration file.

    Right click on it and choose launch selected configuration

    When the debug comes up click on the connect button.

    Then click on the load program button and select the program generated from CCSv7.4

    Does it load and run ok?

    Regards,

    John

  • Hi John, 

    Thanks for your prompt response.

    I've followed your guidelines - 

    • Using compiler version 16.9 within CCSv8 gave the same result (i.e. not breaking in main)
    • Following your second tip (Launch config>Connect>Load program open project-CCSv74.out) did bring me to main() !!

    Whats next?

    Thanks.

  • One last quick thing to check. Use the second method but load the program that was created by v8. I just want to make sure that the program does not get to main() using this method. i.e. I want to make sure that it is an issue with the binary we are creating vs the flow.

    Assuming that does not work then it means that somehow we are creating a different binary between 7.4 and 8.0 even when using the same compiler. Could be an option change. We will need to reproduce in the lab here. I would need to know which MSP430 device it is happening on.

    Regards,
    John
  • tinkering around I've noticed that somehow I've got  two debug config in my project: one named MSP430F5259.ccxml and the second named after my project (This wasn't/isn't the case in CCSv7).

    When I hit the green bug toolbar icon, it runs the first configuration and I don't get to main().

    When actively selecting the 2nd configuration (named after the project) it runs fine.

    I tried to delete the first debug config, but when I click the green bug button, it is recreated...

  • update -

    Not sure what was the exact sequence but after several targetConfig deletions and project clean and rebuilds I've managed to stay with only the desired config...
    It now runs to main() as expected when clicking the toolbar debug button.

    THANKS
  • cool.

    The .ccxml debug configuration would get generated when we do that "Launch selected configuration" action. The one with the project name gets generated when you select a project and hit the bug button. It is safe to delete these. The only time you wouldn't want to delete them is if you were going into that debug configurations dialog and adding custom settings.

    Regards,
    John
  • update 2 -

    guess what... I've reverted back to compiler 18.1, rebuilt and , again, I can't stop at main() (+ no pause/run in toolbar). This time with a single targetConfig...

    Is it something I'm doing wrong?

  • Hi eyalasko,
    I'm thinking that a webex would help resolve this sooner. Can you start a private conversation with me so we can discuss?

    Thanks
    ki
  • Were you able to get past this? We didn't hear anything back on the request for a webex session.

    Regards,
    John
  • As we have not heard back from you I am going to assume that you have managed to get past this and will close the thread. If this is not the case please feel free to reply or to start a new thread.

    Regards,
    John