• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 599 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: CCSv9: Cannot edit Launch Configuration

twelve12pm
Genius 4455 points
Other Parts Discussed in Thread: TM4C129ENCPDT

Tool/software: Code Composer Studio

I cannot edit my project's launch configuration in CCSv9.

In Project Properties, going to Run/Debug Settings, selecting the launch configuration, and clicking Edit fails silently. No error message is shown. No dialog box opens.

I'm using CCS v9.1.0 on Linux for TM4C129ENCPDT. My project has its own makefile. I am using the CCS Linaro GCC for ARM compiler. I need my launch configuration to launch the binary that is produced by my makefile. When I create the new project and set it up, the project can build successfully. However, if I go into the launch configuration and set the program name to my binary, then exit that launch configuration dialog, I cannot edit the launch configuration again because clicking that Edit button has no effect, as mentioned before.

Going to Run -> Debug Configurations has no effect either.

I tried deleting the workspace and starting over with a new one, several times.

I tried deleting the CCS project and starting over with a new one, several times.

I was able to get this working before but that CCS project became all messed up because I tried to rename it through CCS. So I have to re-create that CCS project and everything else works, except setting up the launch configuration.

I see that other people have reported issues with this and that one of TI's staff was able to reproduce with CCSv8. It seems the problem continues into CCSv9. Reference: e2e.ti.com/.../760367

  • 0
    TI__Guru**** 173310 points

    The specific issue in the referenced thread was fixed in CCS 9.0. So if there is an issue in 9.1.0 it must be something new or different.

    Could you please share with us a simple project that demonstrates the issue? I have been trying to reproduce it but not been able to so far.

  • 0 in reply to AartiG
    Genius 4455 points

    Can I send you the project privately?

  • 0 in reply to twelve12pm
    TI__Guru**** 173310 points

    Yes, if you hover over my forum ID you should be able to send me a private message. Please attach a zip file of your project to the message. Thanks!

  • 0 in reply to AartiG
    Genius 4455 points

    Sent. Thanks for your help.

  • 0 in reply to twelve12pm
    Genius 4455 points

    After some discussion with AartiG, this is the cause:

    I was trying to set up a Portable Project by not having any absolute pathnames embedded in the CCS project or any of its files. The purpose is to check the project into Subversion and allow it to check out on any computer, at any working copy path, and still function. For this purpose, all paths within the project are either relative paths or use Eclipse variables, such as $PROJECT_LOC, to locate whatever they need.

    It turns out, however, that in CCS v9.1.0, the Launch Configuration contains (non-portable) absolute pathnames. So although all other aspects of the project are using portable variable-based paths, the launch configuration cannot do so. The upcoming CCS v9.2 will make improvements in this area. Until 9.2 is released, there is a workaround for the absolute path portability issue described by TI's Ryan Voogjarv in this thread: e2e.ti.com/.../817528

    Bottom line: If you're reading this because you tried to use variables in your launch configuration's embedded paths and subsequently cannot open the launch configuration to edit it, that's why. You'll need to either delete the launch configuration and make a new one, or alternatively open the launch configuration file in a programmer's text editor and make a manual repair.

    Hope this helps...