• Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 666 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.

can't change startup debug configuration (ccxml)

Robert Wolfe
Mastermind 7860 points

Hello,

I'm using CCS V5.1.  I have multiple projects, of different processor type, each with thier own .ccxml file.  For instance project A.ccxml and project B.ccxml.  Initially I had been debugging A.ccxml.  But lately, I'm working with B.ccxml.  But no matter how I try to change the startup of CCS to use B.ccxml, it constantly uses A.ccxml.  So then each time I get the usual errors about not being able to connect, etc (because that target is not being used).  If there is a way to change the startup ccxml in CCS V5.1, I've not been able to find it.  Please advise: is there a way to stop using A.ccxml whenever I startup CCS.

Robert

  • TI__Guru**** 464981 points

    Hi Robert,

    I think this post is related to your other post:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/215463.aspx

    The training module on Target Configurations I mentioned in that thread may help answer your question on how to explicitly configure CCS to use the correct ccxml file.

    Thanks

    ki

  • in reply to Ki
    Mastermind 7860 points

    Ki,

    Thanks for the reply.  I saw the training document with Target Configuration before making any posts today, when searching E2E for answers.  But I did not find any information in it, that corrected the problem I describe in this post. 

    Can you please specify the pages that you think will resolve this issue?  Or can you just reply with the information in it, that you think will resolve this?

    Regards,

    Robert

  • in reply to Robert Wolfe
    TI__Guru**** 464981 points

    slides 6 and 8 have the most useful information.

    Basically you can do one of the following:

    -explicitly launch a debug configuration for a ccxml file like in slide 6 (this would guarantee that you are starting the debugger for that configuration)

    -if you do not have the ccxml file as part of your project but in the User Defined shared location, you must specify the configuration as the [Default] like in slide 8

    -if you have the ccxml files as part of the project (according to your description, I think this how you have it set up), you need to make sure that the ccxml in your project is set with the [Active] tag in your project. Normally it is always active when it is the only ccxml file in the project

    Thanks

    ki

  • in reply to Ki
    Mastermind 7860 points

    Ki,

    As you see from the other posts you are working with me on, these steps are not working.  The other project A.ccxml file always remains [Active], which is not the one I am working on, and is causing this trouble, even when I set B.ccxml to Active.  B is the project I am working on, but B.ccxml will not stay [Active] between re-starts of CCS.

    Robert

  • in reply to Robert Wolfe
    TI__Guru**** 464981 points

    Let's consolidate the responses to the other post so there is just one thread. 

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/215463.aspx

    I'll lock this thread.