Difference between launching DebugServer Scripts from IDE versus DSS (command line)

Hello Angelo

Angelo Schneider said:

Now I use the slighly modified java script file( added a line like this:

env = Packages.com.ti.ccstudio.scripting.environment.ScriptingEnvironment.instance();

and at the correct place:

debugServer.setConfig(configFile.getAbsolutePath());

).

 

I load/execute that file now in a DOSshell with this command: "dss DebugServerScriptingDSS.js"

However unlike running inside of CSS this time I get an error:

"SEVERE: Could not open session. No devices found matching: Blackhawk USB560-BP Emulator, 20-pin JTAG Cable_0/CA8"

Detailed exception information:
JavaException: com.ti.ccstudio.scripting.environment.ScriptingException: Could not open session. No devices found matching: Blackhawk USB560-BP Emulator, 20-pin JTAG Cable_0/CA8

Could you describe your environment more? I assume you are indeed using a Blackhawk USB560-BP emulator but please describe your target board - specifically what devices are on the scan chain.

Also please show how you are calling openSession to create your debug sessions?

Thanks

ki

The file I use in CSS looks like this:

---- works in CSS ----

    script      = env.instance();
    debugServer = script.getServer("DebugServer.1");
    script.setScriptTimeout(SPI_SCRIPT_TIMEOUT * 1000);
    try  {
        print("Open a debug session for CortexA8 on VME...");
        debugSessionCA8     = debugServer.openSession("Blackhawk USB560-BP Emulator, 20-pin JTAG Cable_0/CA8");
    }  catch(error)     {
        print("ERROR: Target configuration has not been launched or unexpected EMULATOR/CORE-names in target configuration!");
        print("Detailed exception information:");
        print(error);
        statusOK = false;
    }

--- END ---

The file I use with DSS looks like this

---- FAILS in DSS ---

    env = Packages.com.ti.ccstudio.scripting.environment.ScriptingEnvironment
            .instance();
    script = env.instance();
    debugServer = script.getServer("DebugServer.1");
    debugServer.setConfig(configFile.getAbsolutePath()); // << that path is correct
    script.setScriptTimeout(SPI_SCRIPT_TIMEOUT * 1000);

    try {
        print("Open a debug session for CortexA8 on VME...");
        debugSessionCA8 = debugServer
                .openSession("Blackhawk USB560-BP Emulator, 20-pin JTAG Cable_0/CA8");
    } catch (error) {
        print("ERROR: Target configuration has not been launched or unexpected EMULATOR/CORE-names in target configuration!");
        print("Detailed exception information:");
        print(error);

        statusOK = false;
    }
---- END ----

Screenshot of "Environment" ... the board is a custom made board, not sure if it is based on a certain "standard" board.

My assumption (but that might be bollocks) is: DSS does not find the drivers that are mentioned in the .ccxml file and gives a missleading error message.

BTW: this is not super important.

I modified the TI example "loadti" so far that it does what my original script does. However I have absolutely no clue why my new loadti now works when run from DSS and the slightly modified original file does not (slightly modified to adapt to the fact that it has no IDE as "environment" ... no other changes of course!)

Can you set the config with an explicit hardcoded path + ccxml file name?

Not sure if I get you right, you want to know if it works with a full qualified hard coded path name?

This is what I do:

A part of the path comes from an environment variable. As I don't know if it is in DOS format or in Unix format I use "java.io.File" as a helper to construct the path.

        var Target_Conf_File = "VisionMidEVE_SBL_NoGEL.ccxml";
        String workspaceLoc = System.getenv("WORKSPACE");
        File workspacePath = new File(workspaceLoc);
        File configFile = new File(workspacePath.getAbsolutePath() +
                        File.separator + "/workspace/04_Engineering/03_Workspace/soc" +
                        File.separator + Target_Conf_File);
        checkExists(configFile);    
        debugServer.setConfig(configFile.getAbsolutePath());

There is no difference when I use:

        debugServer.setConfig(("D:\Jenkins\jobs\SW_SMFC400_PR\workspace\04_Engineering\03_Workspace\soc\VisionMidEVE_SBL_NoGEL.ccxml");

As I said in my previous post, it is no longer important. I just wondered if some of the scripts or DSS itself depends on a certain working directory or a certain installation directory of CSS.

There should be minimal difference between launching the debugger via CCS or via DSS. Basically they both sit on top of the same debug server. The only difference is that some debug properties set in the workspace or debug configuration would not apply in the DSS session.

The error you get implies that there is a mismatch between the target defined in the ccxml file and the names of the connection and CPU you are specifying in the openSession call. Are you sure you have the correct names for both? Could you attach your ccxml file? I'd like to check the actual xml source in it.

Thanks

ki

Hi Ki-Soo Lee,

find attached the ccxml file. 8080.DualVisionMidEVE_NoGEL.tar.gz

Best Regards

Angelo

P.S. had to tar it :D

Thanks.

You are using a device that my CCS does not support. Did you install some patch on top of your CCS install to get C6A815x support? If so, could you point me to it?

Thanks

ki

Hello,

I assume you refer to the av_bios_sdk we use? Well, it is from TI, the release notes say this:

Applies to Product Release: 00.07.00.00
Publication Date: Sept 13, 2012

I'm new to CCS so I'm not sure if I understood your question correctly, so I attached two screen shots about the Compilers we have and OS Support Drivers.

Best Regards

Hello,

I have the same problem. I have a .js script to run A8 program in DM814x  that works very good in scripting console in CSS (version 5.5), but I would like to execute it outside  CSS, my script is like this:

if (!withinCCS)
{
importPackage(Packages.com.ti.debug.engine.scripting);
importPackage(Packages.com.ti.ccstudio.scripting.environment);
importPackage(Packages.java.lang);

var script = ScriptingEnvironment.instance();

// Get the Debug Server and start a Debug Session
debugServer = script.getServer("DebugServer.1");
}
else
{
var debugServer = ds;
var script = env;
}

script.traceWrite("Configuring debug server...");
debugServer.setConfig("myfile.ccxml")

script.traceWrite("Opening a debug session for A8 core...");
debugSession = debugServer.openSession("Spectrum Digital XDS510USB Emulator_0/CortexA8")
script.traceWrite("Done!");

script.traceWrite("Connecting A8...");
debugSession.target.connect();
script.traceWrite("Done!");

script.traceWrite("Resetting A8...");
debugSession.target.reset();
script.traceWrite("Done!");

script.traceWrite("Loading ProgPBL in A8...");
debugSession.memory.loadProgram("myprogram.out");
script.traceWrite("Done!");
debugSession.target.runAsynch();

 When I try to execute out of CSS (dss.bat flash.js) I have the error:

SEVERE: CortexA8: Error: Error 0xA0002020/-1203 Error during: Execution, Control, The DAP access, address 0x00000088, has returned a SLAVE error.

SEVERE: CortexA8: Unable to determine target status after 20 attempts

SEVERE: CortexA8: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

SEVERE: emulation failure occurred
SEVERE: Error connecting to the target: emulation failure occurred
org.mozilla.javascript.WrappedException: Wrapped com.ti.ccstudio.scripting.environment.ScriptingException: Error connecting to the target: emulation failure occurred (flash.js#52)
at org.mozilla.javascript.Context.throwAsScriptRuntimeEx(Context.java:1693)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:160)
at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:204)
at org.mozilla.javascript.optimizer.OptRuntime.callProp0(OptRuntime.java:119)
at org.mozilla.javascript.gen.c1._c0(flash.js:52)
at org.mozilla.javascript.gen.c1.call(flash.js)
at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:340)
at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2758)
at org.mozilla.javascript.gen.c1.call(flash.js)
at org.mozilla.javascript.gen.c1.exec(flash.js)
at org.mozilla.javascript.tools.shell.Main.evaluateScript(Main.java:503)
at org.mozilla.javascript.tools.shell.Main.processFileSecure(Main.java:425)
at org.mozilla.javascript.tools.shell.Main.processFile(Main.java:391)
at org.mozilla.javascript.tools.shell.Main.processSource(Main.java:382)
at org.mozilla.javascript.tools.shell.Main.processFiles(Main.java:179)
at org.mozilla.javascript.tools.shell.Main$IProxy.run(Main.java:100)
at org.mozilla.javascript.Context.call(Context.java:528)
at org.mozilla.javascript.ContextFactory.call(ContextFactory.java:450)
at org.mozilla.javascript.tools.shell.Main.exec(Main.java:162)
at com.ti.ccstudio.apps.internal.scripting.RunScript$1.run(RunScript.java:88)
Caused by: com.ti.ccstudio.scripting.environment.ScriptingException: Error connecting to the target: emulation failure occurred
at com.ti.debug.engine.scripting.Target.connect(Target.java:921)
at com.ti.debug.engine.scripting.Target.connect(Target.java:863)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:145)
... 18 more

I have got to exec correctly this script outside CCS once, so I know that script is correct, and whitin CCS it always works correctly. I don´t know the difference or that I am doing bad.