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.

CCS/AM5728: Running Debug server script automatically while launching target configuration

Part Number: AM5728

Tool/software: Code Composer Studio

We have a usecase to automate device initialization on one of our Sitara devices, where to simplify the device initialization process, we would like to run a DSS script when customer launches the connection using their target configuration file? without this feature, customers have the additional step to run this script from the console on every reset and also need to make sure that the DSS script points to their target configuration file location. Having this option will address both the issues.

Is this possible/supported with CCSv8 ? Does a DSS script always have to be run from Scripting console or are their hooks to launch the script from GEL or from .ccxml?

Appreciate your inputs and support on this topic.

Regards,

Rahul

  • Hi Rahul,
    You can specify a DSS initialization script in the Debug Launch Configuration. See slide 46 of: software-dl.ti.com/.../CCSv6-TipsAndTricks.pptx

    The specified DSS javascript will be automatically executed when the debugger is launched.

    Thanks
    ki
  • Ki,

    Thanks for the quick response here. Is this option same as the Initialization script option that we see under Advanced Tab of the Target configuration file. I had assumed that this is only used to specify the GEL script for the core/SOC and wasn`t aware that this can be used for running DSS scripts.

    One last question, on multi-core devices if we use .dss scripts for different cores, will all of them run at the time of launch or do we need to connect to the core to allow the DSS script to run? Is it recommended to combine the contents of the DSS script into single script and run it from the primary boot core?

    Regards,
    Rahul
  • Rahul Prabhu said:
    Is this option same as the Initialization script option that we see under Advanced Tab of the Target configuration file

    It is not the same.

    Rahul Prabhu said:
    I had assumed that this is only used to specify the GEL script for the core/SOC and wasn`t aware that this can be used for running DSS scripts.

    You are correct, you can only specify GEL scripts in the target configuration file. The "initialization script" in the debug launch configuration is something completely different and is for DSS javascript files.

    Rahul Prabhu said:
    One last question, on multi-core devices if we use .dss scripts for different cores, will all of them run at the time of launch or do we need to connect to the core to allow the DSS script to run? Is it recommended to combine the contents of the DSS script into single script and run it from the primary boot core?

    You can only specify one DSS script for your entire target. Hence you would need to consolidate your scripts into a single script that would apply to all the cores. Unlike GEL (which is a per core level), a DSS javascript initialization script applies to the whole debug instance and can connect to all available cores of that debug instance.

    There is also a wiki that may be useful:

    http://processors.wiki.ti.com/index.php/Debug_Configuration_Initialization_Scripts

    Thanks

    ki

  • Ki,

    Thanks a lot for pointing me in the right direction. I just quickly tried this out with my AM335x setup using the instructions here:
    processors.wiki.ti.com/.../Debug_Configuration_Initialization_Scripts

    I believe that this should work with our setup once we merge everything into a single DSS script.

    Regards,
    Rahul
  • Sounds good. You probably already know this but to confirm - note that you don't necessarily have to have one physical script. You can have a main script that includes a bunch of other scripts. That main script is what you would specify in the debug launch configuration.

    Thansk
    ki