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

CCSv5 does not save Flash Settings?

quark
Expert 2220 points

Hello,

I have a CCSv5 project and it requires custom settings for OSCCLK and Erase Sector Selection.

In one workspace I configured those settings and everything (selective flash erase and load program) works fine.  If I create a new workspace and import that project, all of those settings goes back to the default values.  This is a problem for us because if someone else loads that project, they'll get the wrong settings.

CCSv4 used to save that setting information into the .launches directory and importing a project into a new CCSv4 workspace preserves those settings.  It does not appear that CCSv5 creates the .launches directory.

How can I ensure that another person who imports my project will get the correct "Flash Settings"? 

Thank you.

-Quark

  • 0
    Expert 2220 points

    I found that CCSv5 places the ".launches" directory in the workspace directory under "[workspace_dir]/.metadata/.plugins/org.eclipse.debug.core/.launches"

    I believe that moving .launches to the workspace directory (instead of keeping it in the project directory as in CCSv4) is not such a good idea.  This means, if someone else needs to import my project and use the same Flash Settings, they'll also need to copy the necessary [project_name].launch files into that directory.

    Is there a workaround?

    Thank you.

    -Quark

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

    Quark,

    Please see this post for a suggestion of how to pass around debug launches among multiple users. You can save the launch configuration to a file and associate the file with either a shared dummy project or the specific project you want to share.

    The location where you specify the settings to share to file are shown below (showing an example of modified Flash erase sector selections).

    First create a new debug configuration using the desired .ccxml and modified settings. Then save the configuration as a shared file.