I can tell you what I remember, I did use tcl scripts in the past but not recently. Also I don't know the CW debugger for the DSC56800, I did use CF, EPPC and X86 in the past only.
> 3.cmdIDE.exe /d scriptname.tcl executed. The IDE hangs.
Not sure what you mean with "hangs". The ide wont close unless you tell it to do so, there is a scripting command for this.
> 4.Executed by setting a Script point. The .tcl file is opened but no command executed.
Script points execute the script when the underlying breakpoint is hit. Was it hit? Try a simple command like
puts "I was here"
>5.Tried executing the script file through the 'source scriptname.tcl'command in
>the command window. There was an error message output.
Then fix the errors before you try anything else....
Which errors did you get?
>Clarifications:
>1.How should we have the commands in the .tcl file executed?
Not sure what you are asking. Executing them via source, command line argument or via script point should work.
>2.As mentioned in the reference pdf, there was no 'tcld.tcl' file which needs to
>get executed at start up? It is mentioned to be available at %SystemRoot% directory.
Cannot help, never heared of this file. Don't think it is needed.
> 3. Is there any additional software that needs to be installed for the script execution?
No. The needed tcl libraries are provided.
> 4.Is it possible to provide 'values to variables' to be passed to the functions in
> the software through the script?
Not sure that 'values in variables' means. TCL is a progamming language which supports variables, reading/writing files and much more. So if this refers to read setup information into the script via configuration files, then this can be done via standard TCL.
> 5.Can the script consist only of the Metrowerks commands?
TCL commands work too. There are also many TCL libraries.
Daniel