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.

Unable to run Java project once exported to Runnable JAR

Other Parts Discussed in Thread: CCSTUDIO

So I'm essentially trying to make a wrapper executable for loading four different programs onto a DSP sequentially, so I wrote a java class with a GUI that will handle this.  The project works perfectly from inside of eclipse, but once exported to an external executable jar file it ceases to function.  Running it from the command line produces this error 

SEVERE: Can not connect to DebugServer. Path not found: 'C:\\bin'
SEVERE: Could not start server: DebugServer.1: Can not connect to DebugServer. P
ath not found: 'C:\\bin'

It seems like it's looking for the TI libraries in the wrong place.  How might I be able to point it in the right direction?

  • Hi,

    Can you please add a screenshot for more clarity?

    Regards,

    Gautam

  • Keith - please specify which exact version of CCS you are using (provide the full version number)

    Thanks

    ki

  • I've been using version 5.3.0.00090.  I managed to narrow the problem down to a classpath issue.  I got it working using the following batch script copied from the debug properties command line arguments:

    chdir {Project Directory}

    "C:\Program Files (x86)\Java\jdk1.7.0_25\bin\java.exe" -classpath {Project Directory}\bin;C:\ti\ccsv5\ccs_base\DebugServer\packages\ti\dss\java\com.ti.ccstudio.scripting.environment_3.1.0.jar;C:\ti\ccsv5\ccs_base\DebugServer\packages\ti\dss\java\com.ti.debug.engine_1.0.0.jar;C:\ti\ccsv5\ccs_base\DebugServer\packages\ti\dss\java\js.jar;C:\ti\ccsv5\ccs_base\DebugServer\packages\ti\dss\java\com.ti.ccstudio.scripting.rtdx_1.0.0.jar;C:\ti\ccsv5\ccs_base\DebugServer\packages\ti\dss\java\dss.jar {Package}.{Main Class}

    It seems to me that eclipse doesn't properly link the libraries in any of the export configurations I've tried.  I'm not sure if it's an issue with the libaries, Eclipse, or myself doing something wrong.  While dirty, this fix has been good enough for my purposes so far so I haven't tried manually editing the executable jar files to fix the classpath.