• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 569 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.

storage of project launch configurations

mes
Intellectual 530 points

Hi,

I have 2 launch configurations in my CCS5.x project.  One has a target configuration using an XDS560, the other XDS100 jtag.

I see these launch configurations in the project properties under Run/Debug settings but cannot figure out where they are stored.

I need to store launch and target configurations .ccxml files in a common location so others can reuse them.

 

I'm a little new to CCS5.x - Am I right in making these config files common?   We are using the 8148 evm from Mistral and XDS560 and XDS100V2 jtags.

Maybe a more fundamental question:  I assume since I have two separate target configurations (the jtag difference), that I also need two separate launch configurations for engineers to choose between (?)

 

Br,
Matt

  • 0
    TI__Guru**** 463941 points

    Hi Matt,

    mes said:
    I see these launch configurations in the project properties under Run/Debug settings but cannot figure out where they are stored.

    launches are stored in your workspace folder:

    <WORKSPACE>\.metadata\.plugins\org.eclipse.debug.core\.launches

    NOTE that in CCSv5.1, the "Run/Debug" setting under the properties are no longer. You can access them from the drop-down menu next to the "Debug" bug button.

    mes said:
    I need to store launch and target configurations .ccxml files in a common location so others can reuse them.

    It is the ccxml file that you can pass around. A launch configuration is a something that CCS caches when launching a debug session for the first time for that target configuration. If a launch configuration does not exist, one will be generated.

    mes said:
    I'm a little new to CCS5.x - Am I right in making these config files common? 

    The target config files (ccxml), yes.

    mes said:
    Maybe a more fundamental question:  I assume since I have two separate target configurations (the jtag difference), that I also need two separate launch configurations for engineers to choose between (?)

    You just need two separate ccxml files.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Genius 15610 points

    There is also a way of saving launch configuration settings to a file. A dummy project could then be created to store these launch configurations and when that project is imported into a workspace, then those launch configurations will become available from Debug drop down menu. The dummy project could be checked into source control system and shared between team members. However, the only time this would be necessary if there was a need to have some sort of a debugger setting be configured differently from the default. If all settings can be controlled through .ccxml file and debugger default settings work, then Ki's suggestion is the simpler option.  

     

    Martin