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

Code Composer Studio Scripting

Anupama Sadanandan
Prodigy 20 points

Hi,

I am using Code Composer Studio 3.3 with F2812 processor. The emulator used is C2000.

I use Visual Basic Scripts interface with the built-in scripting utility of CCS to test the embedded software. It had all been running fine on my target until recently. But when the scripts are run in a continuous batch, the following issues are found alternatively:

- Code Composer hangs when an API call to BreakpointSetAddress or TargetRunAsynch is made

- CCS does not place breakpoint but continue to execute the remaining script

The scripts run well when executed individually.

What would have caused the aforesaid issues? 

Thanks,

Anupama

  • 0
    TI__Guru**** 475381 points

    Hello,

    Without more details, I can only take a guess at some potential causes. One is that the debugger did not properly remove some emulator resources in use before the next script tried to start the debugger again and use the same resource. Another is that target was left in a bad state and did not have a chance to recover. One suggestion is to try adding a target and emulator reset or power cycle of the target between each script run.

    Unfortunately the diagnostic capabilities of CCScripting is very limited so it will be difficult to understand what exactly is the problem (something we addressed with the newer scripting utilities)

    ki

  • 0 in reply to Ki
    Prodigy 20 points

    Hi Ki,

    Thanks for the reply. We open Code composer at the start of a script and connect to the target. At the end of every script we disconnect the target and close the code composer. We also reset the power to the actual hardware in between 2 scripts.

    I would like to know the following:

    1. Is it possible that the APIs return without actually finishing the task? For instance, can this asynchronous behavior be the cause for proceeding with the script without actually setting the breakpoint?

    [Assuming that the Code Composer studio scripting utility APIs invokes built-in Gel commands. This question is being raised in light of the following FAQs: "Is the behavior of TargetEvalExpression() synchronous or asynchronous?" And "Is the behavior of GEL synchronous or asynchronous?"]

    2. The newer version of scripting utilities are java based as could be seen. Is there support available still for the older version of scripting utility to go over the known issues and fixes?

    3. Where can I find the link to known issues with Code Composer Studio Scripting utility for v3.3?

    4. Is there a scripting command for adding target?

    Thanks,

    Anupama

  • 0 in reply to Anupama Sadanandan
    TI__Guru**** 475381 points

    Anupama Sadanandan said:
    1. Is it possible that the APIs return without actually finishing the task? For instance, can this asynchronous behavior be the cause for proceeding with the script without actually setting the breakpoint?

    The vast majority of CCScripting APIs are synchronous. The only two that come to mind that are not synchronous are TargetRunAsynch and TargetEvalExpression (which varies on the GEL call being evaluated)

    Anupama Sadanandan said:
    [Assuming that the Code Composer studio scripting utility APIs invokes built-in Gel commands. This question is being raised in light of the following FAQs: "Is the behavior of TargetEvalExpression() synchronous or asynchronous?" And "Is the behavior of GEL synchronous or asynchronous?"]

    Are you using TargetEvalExpression to call any built-in GEL functions? There are many built-in GEL functions which are not synchronous.

    Also note that if you are using a script timeout, that can force synchronous calls to return before completing execution.

    Anupama Sadanandan said:
    2. The newer version of scripting utilities are java based as could be seen. Is there support available still for the older version of scripting utility to go over the known issues and fixes?

    The older CCScripting utility that you see in CCSv3.3 and earlier is no longer supported and has not been supported in some time.

    Anupama Sadanandan said:
    3. Where can I find the link to known issues with Code Composer Studio Scripting utility for v3.3?

    The best resource for this would be the ReadMe.html doc that ships with CCSv3. It has a revision history and list of fixes for each revision. But there no list of current known issues.

    Anupama Sadanandan said:
    4. Is there a scripting command for adding target?

    There is an API to import an existing configuration (CCSConfigImport)