[quote user="Anupama Sadanandan"]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?[/quote]
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)
[quote user="Anupama Sadanandan"][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?"][/quote]
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.
[quote user="Anupama Sadanandan"]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?[/quote]
The older CCScripting utility that you see in CCSv3.3 and earlier is no longer supported and has not been supported in some time.
[quote user="Anupama Sadanandan"]3. Where can I find the link to known issues with Code Composer Studio Scripting utility for v3.3?[/quote]
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.
[quote user="Anupama Sadanandan"]4. Is there a scripting command for adding target?[/quote]
There is an API to import an existing configuration (CCSConfigImport)