• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 88 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.

CCSTUDIO: CCSv20 - Launch Target Configuration File

Scott Specker
Intellectual 310 points
Part Number: CCSTUDIO

Tool/software:

CCS Eclipse (v18) provided the ability to "Launch Selected Configuration" .ccxml file. This launched the debugger without connecting to the target or loading a program.

Does CCSv20 support this option? The closest I can find is either:

  • Right-click on .ccxml file and selecting "Start project-less debug".
  • View -> Connected Targets, then click "Debug" and click the Debug Icon in the Connected Targets toolbar

Both methods seem to start the debugger but I cannot tell if the target is connected. I am guessing that it is not connected because I get the following error when I try to Load a program:

GEL: Target must be connected before calling the function

As a side note, when I tried using:

  • Run -> Start Debugging from the menubar

At first, the same result mentioned above happened. But after "debugging" my code using the "Debug Project" toolbar button, this option jumped right into the debugger, the same as if I hit the "Debug Project" button.

To summarize:

  1. Is project-less debug similar to using the "Launch Selected Configuration"?
  2. If so, am I missing a way to "Connect to Target" (like we had in CCSv18)?
  3. Or should we just be able to go straight to loading a program (but that feature is broken)?

Thanks Much,
Scott

  • 0
    TI__Guru**** 464751 points

    Hi Scott,

    Scott Specker said:

    Does CCSv20 support this option? The closest I can find is either:

    • Right-click on .ccxml file and selecting "Start project-less debug".
    • View -> Connected Targets, then click "Debug" and click the Debug Icon in the Connected Targets toolbar

    Yes, these would be the equivalent functionality.

    Scott Specker said:
    Both methods seem to start the debugger but I cannot tell if the target is connected. I am guessing that it is not connected

    The target is not connected by default. This would mimic CCS Eclipse behavior.

    You can modify the generate launch configuration to have it auto-connect to the target:

    https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-main.html#launch-configurations

    Scott Specker said:
    At first, the same result mentioned above happened. But after "debugging" my code using the "Debug Project" toolbar button, this option jumped right into the debugger, the same as if I hit the "Debug Project" button.

    Yes, once a launch configuration is generated, the option would be available.

    Scott Specker said:
    Is project-less debug similar to using the "Launch Selected Configuration"?

    Yes.

    Scott Specker said:
    If so, am I missing a way to "Connect to Target" (like we had in CCSv18)?

    You can modify the generate launch configuration to have it auto-connect to the target:

    https://software-dl.ti.com/ccs/esd/documents/users_guide_ccs/ccs_debug-main.html#launch-configurations

    Scott Specker said:
    Or should we just be able to go straight to loading a program (but that feature is broken)?

    Not by default. But this can be configured by modifying the launch configurations

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 310 points

    If we do not modify the launch.json to auto-connect, is there a "Connect to Target" button like we had in Eclipse? Or to get this to work, do we need to invoke it through the json file?

    BTW, the page you referenced actually states that autoconnect is TRUE by default.

    • autoConnect: Boolean value that determines if the debugger should automatically connect to this core during debugger startup. Default value is true.

    In the end, I can see that this new methodology is probably much more flexible. (And the way it's done in Theia.) But since I don't really need this feature right now, I'll probably just remove it from the Appendix where we talk about this in the new course Eric and I are getting ready to release. Without a few more examples, it just seems like it will take a lot of trial and error to figure it out. That said, I appreciate your help in clarifying things a bit.

  • +1 in reply to Scott Specker
    TI__Guru**** 464751 points
    Scott Specker said:
    If we do not modify the launch.json to auto-connect, is there a "Connect to Target" button like we had in Eclipse? Or to get this to work, do we need to invoke it through the json file?

    It needs to be configured in the json file.

    Scott Specker said:
    BTW, the page you referenced actually states that autoconnect is TRUE by default.

    The description is incomplete in the document. It is TRUE for a project debug. It is FALSE for a project-less debug. I'll have the document corrected. Thank you for pointing it out.

  • 0 in reply to Ki
    Intellectual 310 points

    Thanks!

    When they fix the documentation. It might be nice to include a simple launch.json example. One where you do a project-less debug (with connection), where we can then simply use the CCS Run menu to load our project code.

    I know that seems so simple as to sound meaningless, but for me, those simple examples make it easier for us to demonstrate how the mechanisms work. And from there, it's easier to figure out how to build the more complex examples.

    Thanks again,
    Scott