• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 312 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.

launchTIDebugger in CCSv5

MattB
Expert 2025 points

Hi,

I wrote a script for CCSv4 that uses launchTIDebugger.

Is there something I can do in CCSv5 that will achieve the same thing.

Initially I've commented out the call to launchTIDebugger and I launch the debugger from the target configuration and then run the rest of the script!

I'm still only in my 2nd hour of trying to use CCSv5!

Thanks,

Matt

  • 0
    TI__Genius 15860 points

    Hi Matt, 

    I am assuming that you are talking about a js script that run inside of a scripting console. I think the equivalent command in v5 is "debug", I copied the help for this command. 

    Martin

     

    js:> help debug

     

    Description: Start a CCS debug session with a target configuration file

    Syntax: debug launchConfigName targetConfigPath 

    Arguments: 

      launchConfigName - the name of the launch configuration to create for this debug session

      targetConfigPath - the fullpath of the target configuration file

  • 0 in reply to MartinS
    Expert 2025 points

    Hi Martin,

    I've changed my script from:

        if (activeDS === null) {
        print("Launching TI Debugger...");
        launchTIDebugger();
    }

    to:

    //    if (activeDS === null) {
        print("Launching TI Debugger...");
        debug("Texas Instrucments XDS100v2 USB Emulator_0", "D:/Documents and Settings/113007312/user/CCSTargetConfigurations/C6455s_xds100v2.ccxml");
//    }

    and I'm up and running again.

    I'm not sure what to do about the activeDS; I don't think my script did what I wanted anyway so for now I'm not going to do anything!

    Thanks,

    Matt

  • 0 in reply to MattB
    TI__Genius 15860 points

    Hi Matt, 

    activeDS is an internal variable that can be used to refer to selected CPU in debug view. Thus it looks like your script is trying to ensure that the script runs only when there is no active debug session. 

    Having said this, activeDS is not very robust and it works ok in some scenarios. We are adding a new function that will be supported by scripting console that will provide the same information. It is not available in CCSv5 LR, but it will be there in following release. 

     

    Martin

    js:> getSelectedDebugSessions /?

     

    Description: Retrieves the current selections from the Debug View and calls DebugServer.openSession() for each debug context.

    Syntax: getSelectedDebugSessions()

    Returns: An array of Debug Session objects, can be empty.