• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 423 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.

Errors when Debugging DSS using CCSv4

Joshua Lawes
Intellectual 650 points


Hello,

I followed the instructions found here Debugging Your DSS Script Using CCS using CCSv4.2.3.00004 however each time that Code Composer is opened via the script, the connection is unsuccessful and I see the following error in the error log:

Could not update RTA6 Solution's DP: XDCLogSource

Any ideas on how to get around this (if anybody has seen this before)?

Thanks,

--

Joshua

  • 0
    TI__Guru**** 472461 points

    Hi Joshua,

    I don't think the RTA message is the issue. Were there any other messages? How did you determine that the connection was unsuccessful? Did your script successfully launch CCS but the automation is not reflected in the GUI when a debug session is started?

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 650 points

    Hi Ki,

    The RTA is the only message I'm seeing in the error log (though I'm happy to grab a more informative dump for you if needed).  I've run the script a number of times no problems without the addition of the Code Composer GUI.  The main purpose of this is to assist others in understanding my scripts. 

    Yes, that is exactly what is happening, the GUI is starting (and showing me only the RTA error in the error log) but not reflecting any of the actions in the script (such as loading the target, setting breakpoints, etc.).

    Thanks,

    --

    Joshua

  • 0 in reply to Joshua Lawes
    TI__Guru**** 472461 points

    I gave this a try and it worked for me. I also saw that RTA message but as I expected, it did not have any impact.

    The only thing I can think of is if you launch a debug session in CCS with a different configuration than what you are using in the script. Either that or you didn't set a breakpoint in Rhino and let the script terminate before CCS ever comes up. Can you confirm either of these is not an issue?

    ki

     

  • 0 in reply to Ki
    Intellectual 650 points

    Hi Ki,

    Thanks for your input.

    • When you talk about a different configuration, are you talking about the target configuration files?
    • When you talk about setting a breakpoint and letting the script terminate before CCS ever comes up, do you mean setting a breakpoint in the script immediately after the env.getServer("CCSServer.1").openSession(".*"); line and leaving the target halted there until CCS shows up?

    Cheers,

    --

    Joshua

  • 0 in reply to Joshua Lawes
    Intellectual 650 points

    Hi Ki,

     

    So although the wiki I referenced for instruction states

    "script.getServer("CCSServer.1").openSession(".*");

    This can be added anywhere after the ScriptingEnvironment is created: ",

    in fact it seems to be important that it is done before opening the debug server session.

     

    Though I can now see the script actions (such as code being loaded on the target), the debugger seems to be quite fickle and hangs/stalls quite frequently.

     

    Is there a set way to close the debugger via script, or does one simply do this manually?

     

    Thanks,

     

    --

    Josh