CCS/RM48L952: Deployed Debug Server Script Application cannot openSession

So for some more info on this, below is a shot of my classpath, from within the IDE my DSS connections and all actions through the scripting engine are successful. I cannot even get a connection when running an executable JAR.

When exporting to executable Jar I have tried all options for packaging referenced libraries i.e. extract, package and copy to sub-folder. Nothing seems to work. 

I am connecting to an RM48L952 target via Blackhawk USB200 JTAG Emulator. As shown by the classpath I use ccs v7, but my java application is developed in Eclipse Oxygen.

The following methods are called to get things started and appear to be successful. eol_server is the constructor for my server object through which all dss commands are handled.

	public eol_server() {
		/* Create Scripting Environment */
		env = ScriptingEnvironment.instance();
		env.setScriptTimeout(60000);
		try {
			env.traceSetConsoleLevel(TraceLevel.OFF);
		} catch (ScriptingException e) {
			// TODO Auto-generated catch block
			serverMessagesProperty().set("TraceLevel Could not be set");
		}
		connectedProperty().set(false);
		serverMessagesProperty().set("waiting");
		targetRunningProperty().set(false);
		programLoadingProperty().set(false);
	}	
	


	public boolean getdssserver() {
		try {
			debugServer = (DebugServer)env.getServer("DebugServer.1");
			if (debugServer != null) {
				serverMessagesProperty().set("DebugServer.1 Created");
				return true;
			}
			else
			{
				serverMessagesProperty().set("Failed to create debug server");
				return false;
			}
		} catch (ScriptingException e) {
			serverMessagesProperty().set("Failed to create debug server");
			return false;
		}
	}

In my main function I set up my JavaFX stage, instantiate an eol_server object then call getdssserver and launch the GUI. In the GUI we choose when to connect via a Java FX menu command, this permits selecting software builds and target configuration files before connecting. The connection method is as follows:

private class ConnectService extends Service<Void> {
		private String g_ccxml;
		private String g_board;
		private String g_cpu;
		private String g_build;
		private boolean g_loadProgram;
		
		public ConnectService(String board, String cpu, String ccxml,String build, boolean loadProgram) {
			g_ccxml = ccxml;
			g_board = board;
			g_cpu = cpu;
			g_build = build;
			g_loadProgram = loadProgram;
		}
		
		@Override
        protected void succeeded() {
			//thread will set appropriate status
			serverMessagesProperty().set("idle");
        }

        @Override
        protected void failed() {
        	serverMessagesProperty().set("error - connect thread");
        	
        }

        @Override
        protected void cancelled() {
        	serverMessagesProperty().set("error - thread exit");
        }

        @Override
        protected Task<Void> createTask() {
            return new Task<Void>() {
                @Override
                protected Void call() throws Exception {
                	
                	if(debugServer != null && g_board != null )
                    {
                    	serverMessagesProperty().set("Configure CCXML file");
                    	debugServer.setConfig(g_ccxml);
                    	serverMessagesProperty().set("Opening Session");
                    	try {
                    		//debugSession = debugServer.openSession(String.format("%s/%s",g_board,g_cpu));
                    		//debugSession = debugServer.openSession(g_board,g_cpu);
                    		//debugSession = debugServer.openSession("Texas Instruments XDS2xx USB Debug Probe_0/CortexR4");
                    		debugSession = debugServer.openSession("*","*");
                    		serverMessagesProperty().set("Session Opened");
                    		Thread.sleep(250);
                    		debugSession.target.connect();
                            serverMessagesProperty().set("Target Connected");
                            Thread.sleep(250);
                            debugSession.symbol.load(g_build);
                            serverMessagesProperty().set("Symbols Loaded");
                            Thread.sleep(250);
                            debugSession.target.runAsynch();
                            serverMessagesProperty().set("Target Running");
                            Thread.sleep(250);
                            //debugSession.options.printOptions(".*");
                            //there is a problem with the auto run to main after a program load, so disable that option
                            debugSession.options.setBoolean("AutoRunToLabelOnRestart",false);
                            connectedProperty().set(true);
                            targetRunningProperty().set(true);
                            
                    	}
                    	catch(Exception e)
                    	{
                    		serverMessagesProperty().set("Session Closed : Error 1");
                    		serverMessagesProperty().set(e.getMessage());
                    	}
                    	
                    }
                    else
                    {
                    	serverMessagesProperty().set("Invalid Request");
                    }
                    Thread.sleep(250); 
                    return null;
                }
            };
        }
	}

The connection request is made in a thread to ensure we don't get any crashes from the JavaFX GUI while all of this completes. I have connection properties to ensure the rest of the GUI does not permit any further actions until dss is connected to the target successfully, see connectedProperty() above. Again, this works well in the IDE. But the line at which it is failing when ran in the executable is openSession:

...
//debugSession = debugServer.openSession(String.format("%s/%s",g_board,g_cpu));
//debugSession = debugServer.openSession(g_board,g_cpu);
//debugSession = debugServer.openSession("Texas Instruments XDS2xx USB Debug Probe_0/CortexR4");
debugSession = debugServer.openSession("*","*");
...

you can see in the code snapshot above I have tried all possible permutations of openSession, with strings passed from the GUI, hardcoded strings and also just a generic connect to anything available string "*". All these options  are successful from the IDE but never work from the executable Jar. 

Typical output in my console is 

[ DSS : Creating Server ]
[ DSS : Configure CCXML file ]
[ DSS : Opening Session ]
[ DSS : Session Closed : Error 1 ]
[ DSS : Could not start server: DebugServer.1: Can not connect to DebugServer. URI is not hierarchical ]

As you can see above the try catch block of my connection thread is what outputs "[ DSS : Session Closed : Error 1 ]" so it is definitely openSession that is failing. 

What can I do to debug this further? How do I ensure my openSession arguments are correctly resolved to avoid these "URI is not hierarchical" errors?

If I ramp up my scripting environment tracelevel to FINE my console output is as follows, so the exception for URI not Hierarchical must come from the openSession method

OK...so I pass my target xml file as a string that is the result of a file select dialog. I now suspect that it is the target xml file and passing of paths by string that is not correct. Here is some text output from a successful connection from within the IDE:

getServer: ENTRY sServerName: DebugServer.1
getServer: Getting definition for: DebugServer.1
getServer: Constructing server
getServer: RETURN com.ti.debug.engine.scripting.DebugServer@14292e8
setConfig: ENTRY sConfigurationFile: C:\Users\jwardlaw\workspace_v7b\CTLI-163_C2_Released\targetConfigs\usb_200_rm48l952.ccxml
setConfig: RETURN
debuggerOpen: ENTRY sBoardName: * sCPUName: *
start: ENTRY
start: Firing: onServerStarting()
start: Connecting to XPCOM DebugServer
start: Initializing DebugServer using specified configuration: "C:\Users\jwardlaw\workspace_v7b\CTLI-163_C2_Released\targetConfigs\usb_200_rm48l952.ccxml"
waitUntil: ENTRY com.ti.ccstudio.scripting.environment.ScriptingEnvironment@75d5d8 timeout: 60000 (ms)
<init>: CPU Name: CortexR4
<init>: PartNum: RM48L952
<init>: Family: 470
<init>: SubFamily/MajorISA: d
<init>: Revision/MinorISA: 0
<init>: Platform: EMULATOR
<init>: Processor ID: 1971336192
<init>: DBName: ArmAdvancedFeatures
<init>: CPU Name: IcePick
<init>: PartNum: RM48L952
<init>: Family: 240
<init>: SubFamily/MajorISA: 2
<init>: Revision/MinorISA: 0
<init>: Platform: NONE
<init>: Processor ID: 1006635013
<init>: CPU Name: Dap
<init>: PartNum: RM48L952
<init>: Family: 224
<init>: SubFamily/MajorISA: 1
<init>: Revision/MinorISA: 0
<init>: Platform: NONE
<init>: Processor ID: 939525125
waitUntil: RETURN com.ti.ccstudio.scripting.environment.ScriptingEnvironment@75d5d8
start: Firing: onServerStarted()
start: Searching for devices
listDevices: ENTRY
listDevices: Found debuggable device: Texas Instruments XDS2xx USB Debug Probe_0/CortexR4
listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Debug Probe_0/IcePick
listDevices: Found non-debuggable device: Texas Instruments XDS2xx USB Debug Probe_0/Dap
listDevices: RETURN
start: RETURN
debuggerOpen: RETURN Texas Instruments XDS2xx USB Debug Probe_0/CortexR4
connect: ENTRY
isConnected: ENTRY
isConnected: Target is not connected
isConnected: RETURN false
connect: Requesting target connect
waitUntil: ENTRY timeout: 60000 (ms)
CortexR4: GEL Output:  Memory Map Setup for Flash @ Address 0x0
log: Target is now connected
waitUntil: RETURN
isConnected: ENTRY
isConnected: Target is connected
isConnected: RETURN true

Similar output from the server when running exactly the same from the executable Jar:

getServer: ENTRY sServerName: DebugServer.1
getServer: Getting definition for: DebugServer.1
getServer: Constructing server
getServer: RETURN com.ti.debug.engine.scripting.DebugServer@1cfd9ed
setConfig: ENTRY sConfigurationFile: C:\Users\jwardlaw\workspace_v7b\CTLI-163_C2_Released\targetConfigs\usb_200_rm48l952.ccxml
setConfig: RETURN
debuggerOpen: ENTRY sBoardName: * sCPUName: *
start: ENTRY
start: Firing: onServerStarting()
start: Connecting to XPCOM DebugServer
SEVERE: Can not connect to DebugServer. URI is not hierarchical
stop: ENTRY
stop: RETURN
SEVERE: Could not start server: DebugServer.1: Can not connect to DebugServer. URI is not hierarchical

The above would indicate that it has nothing to do with the target debugger or CPU but rather the pre-configured target ccxml file that was set up for the server. I assume that the executable Jar is not able to resolve the file. How have other people passed the string in an executable DSS Application?

aboveHello Ki, please see above for more info on all this. I suspect that the file path for the target xml file is wrong when executing outside of the IDE. I also show below how my paths are set up for the referenced Jars.

I have tried to just export the jar of the application on it's own without extracting all the referenced packages etc. This is not an executable Jar but rather just a packaged jar to run from the command line.

When I do this, the application does load but then shutsdown immediately with an exception trace that indicates I cannot create my server instance as I cannot find the ScriptingEnvironment class. Here is a screenshot of my command line execution and the classpath showing all the dss jars. I don't know why this does not work, any ideas?

Hello Ki,

So I seem to have also got the application running from the command line after the usual hassles fighting with classpaths, resource files etc. But it is definitely functional. This may be an option for my first deployment but it clearly it is a clunky approach. Understanding why I can't deploy in an executable Jar would be worth knowing.

For reference my compile command was as follows, pushing the class files to a cmdbin directory to keep things separate from the eclipse directory

javac -d .\cmdbin -cp ".";"c:\ti7\ccsv7\ccs_base\DebugServer\packages\ti\dss\java\*";"c:\users\jwardlaw\eclipse-workspace\eol\libraries\xstream-1.4.10\lib\*" <list all .java files>

Then to execute, I copied resource files (images etc) to my .\cmdbin directory then moved to that directory and executed 

java -cp ".";"c:\ti7\ccsv7\ccs_base\DebugServer\packages\ti\dss\java\*";"c:\users\jwardlaw\eclipse-workspace\eol\libraries\xstream-1.4.10\lib\*";"c:\Users\jwardlaw\eclipse-workspace\leo\resources\*" eol.eol_gui

It still seems strange to me that the connection could not be made through the target configuration file when running in an executable Jar, all other actions to instantiate the server environment etc seem to be OK. You can see in the screenshot below the successful connection trace output

Jamie