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.

Debug "Terminate All" causes CCS program to crash

I am running Windows 7 64-bit.

I just purchased the controlSTICK for evaluating. I went through the C2000 Microcontrollers booklet to try to run the first example project. I ran the BlinkingLED project. I could debug, run, and halt the program. When it came time to terminate the debugger, I got the following message box:

"

Java(TM) 2 Platform Standard Edition binary has stopped working

A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.

"

 

When I then click on the "Close Program" button, the following dialog appears:

"

Eclipse

---------------------------

JVM terminated. Exit code=255

C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\javaw.exe

-Xms40m

-Xmx256m

-XX:MaxPermSize=96m

-DXPCOM.RUNTIME=C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32

-Dxpcom.bridge.executeOnDedicatedThread=yes

-Dorg.eclipse.swt.browser.XULRunnerPath=C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32

-Dosgi.instance.area.default=file:/C:/Users/Tatge/Documents/workspace/

-jar C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\startup.jar

-os win32

-ws win32

-arch x86

-launcher C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\eclipse.exe

-name Eclipse

-showsplash 600

-exitdata dd0_cc

-vm C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\jre\bin\javaw.exe

-vmargs

-Xms40m

-Xmx256m

-XX:MaxPermSize=96m

-DXPCOM.RUNTIME=C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32

-Dxpcom.bridge.executeOnDedicatedThread=yes

-Dorg.eclipse.swt.browser.XULRunnerPath=C:\Program Files (x86)\Texas Instruments\ccsv4\DebugServer\win32

-Dosgi.instance.area.default=file:/C:/Users/Tatge/Documents/workspace/

-jar C:\Program Files (x86)\Texas Instruments\ccsv4\eclipse\startup.jar 

---------------------------

"

I can restart the CCS program and do other work, its just really annoying to have to restart the program every time I want to terminate the debugger. Thanks in advance for your help.
  • I'm going to move this to the CCS forum so you'll get an answer.

     

  • Hi Zach,

    Could you provide some additional information? I'm looking for #3 and #6 (crash dump files) listed in:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3131.aspx

    Thanks

    ki

  • Version: 4.1.2.00027

     

    !SESSION 2010-06-10 09:15:09.148 -----------------------------------------------

    eclipse.buildId=4.1.0.02005

    java.version=1.5.0_14

    java.vendor=Sun Microsystems Inc.

    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

    Command-line arguments:  -os win32 -ws win32 -arch x86

     

    !ENTRY org.eclipse.osgi 2 0 2010-06-10 09:23:52.444

    !MESSAGE C:\Users\Tatge\.keystore (The system cannot find the file specified)

    !STACK 0

    java.io.FileNotFoundException: C:\Users\Tatge\.keystore (The system cannot find the file specified)

    at java.io.FileInputStream.open(Native Method)

    at java.io.FileInputStream.<init>(Unknown Source)

    at java.io.FileInputStream.<init>(Unknown Source)

    at sun.net.www.protocol.file.FileURLConnection.connect(Unknown Source)

    at sun.net.www.protocol.file.FileURLConnection.getInputStream(Unknown Source)

    at java.net.URL.openStream(Unknown Source)

    at org.eclipse.osgi.internal.verifier.KeyStores.processKeyStore(KeyStores.java:60)

    at org.eclipse.osgi.internal.verifier.KeyStores.initializeDefaultKeyStores(KeyStores.java:80)

    at org.eclipse.osgi.internal.verifier.KeyStores.<init>(KeyStores.java:46)

    at org.eclipse.osgi.internal.verifier.PKCS7Processor.<clinit>(PKCS7Processor.java:35)

    at org.eclipse.osgi.internal.verifier.SignedBundleFile.setBundleFile(SignedBundleFile.java:410)

    at org.eclipse.osgi.internal.verifier.SignedBundleHook.getVerifier(SignedBundleHook.java:125)

    at org.eclipse.update.internal.verifier.CertVerifier.verify(CertVerifier.java:147)

    at org.eclipse.update.internal.verifier.CertVerifier.verify(CertVerifier.java:133)

    at org.eclipse.update.core.Feature.verifyReferences(Feature.java:967)

    at org.eclipse.update.core.Feature.install(Feature.java:365)

    at org.eclipse.update.internal.core.SiteFile.install(SiteFile.java:96)

    at org.eclipse.update.internal.core.ConfiguredSite.install(ConfiguredSite.java:155)

    at org.eclipse.update.internal.core.ConfiguredSite.install(ConfiguredSite.java:119)

    at org.eclipse.update.internal.operations.InstallOperation.execute(InstallOperation.java:92)

    at org.eclipse.update.internal.operations.BatchInstallOperation.execute(BatchInstallOperation.java:84)

    at org.eclipse.update.internal.ui.wizards.InstallWizard2.install(InstallWizard2.java:374)

    at org.eclipse.update.internal.ui.wizards.InstallWizard2.access$1(InstallWizard2.java:371)

    at org.eclipse.update.internal.ui.wizards.InstallWizard2$1.run(InstallWizard2.java:473)

    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)

    !SESSION 2010-06-10 09:38:18.700 -----------------------------------------------

    eclipse.buildId=4.1.2.00027

    java.version=1.5.0_14

    java.vendor=Sun Microsystems Inc.

    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

    Command-line arguments:  -os win32 -ws win32 -arch x86

     

    !ENTRY org.eclipse.update.configurator 2010-06-10 09:38:19.234

    !MESSAGE Duplicate feature found on site platform:/base/ : com.ti.cgt.c2000.5.2

     

    !ENTRY org.eclipse.update.configurator 2010-06-10 09:38:19.237

    !MESSAGE Duplicate feature found on site platform:/base/ : com.ti.cgt.c5500.4.3

     

    !ENTRY org.eclipse.update.configurator 2010-06-10 09:38:19.240

    !MESSAGE Duplicate feature found on site platform:/base/ : com.ti.cgt.c6000.6.1

    !SESSION 2010-06-10 11:21:00.487 -----------------------------------------------

    eclipse.buildId=4.1.2.00027

    java.version=1.5.0_14

    java.vendor=Sun Microsystems Inc.

    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

    Command-line arguments:  -os win32 -ws win32 -arch x86

     

    !ENTRY org.eclipse.core.resources 2 10035 2010-06-10 11:21:05.363

    !MESSAGE A workspace crash was detected. The previous session did not exit normally.

    !SESSION 2010-06-10 11:36:43.611 -----------------------------------------------

    eclipse.buildId=4.1.2.00027

    java.version=1.5.0_14

    java.vendor=Sun Microsystems Inc.

    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

    Command-line arguments:  -os win32 -ws win32 -arch x86

     

    !ENTRY org.eclipse.core.resources 2 10035 2010-06-10 11:36:51.105

    !MESSAGE A workspace crash was detected. The previous session did not exit normally.

    !SESSION 2010-06-10 12:35:45.883 -----------------------------------------------

    eclipse.buildId=4.1.2.00027

    java.version=1.5.0_14

    java.vendor=Sun Microsystems Inc.

    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US

    Command-line arguments:  -os win32 -ws win32 -arch x86

     

    !ENTRY org.eclipse.core.resources 2 10035 2010-06-10 12:35:50.540

    !MESSAGE A workspace crash was detected. The previous session did not exit normally.

    Hopefully this is what you were looking for. Thanks.

  • Thanks, this helps. Was there any dump files (*.dmp) in:  '<INSTALL DIR>\ccsv4\DebugServer\win32\components\Log'?

  • There were no (*.dmp) files in '<INSTALL DIR>\ccsv4\' or in the workspace directory that I was using.

  • Hi Zach,

    From the stacktrace, it looks like eclipse is trying to run through some kind of update process and couldn't find the .keystore file in your user directory.  Were you trying to update CCS before this issue happen? If you can, can you try to run eclipse (<install dir>\ccsv4\eclipse) with the "-clean" option and use a different workspace?

    Regards,
    Patrick

  • I installed the program from the CD and went right into doing the first example program. I didn't try to update anything.

    Also, I found the eclipse folder and I clicked on "eclipse.exe" but it appears to open the CCS program. Am I running the right thing? If I am, how do I run the "-clean" option?

    Lastly, I started following the steps of the first example from the beginning. I created a new workspace, but this problem happened again.

  • You need to run eclipse.exe with an additional option (-clean). You can open a command window , browse to the eclipse.exe folder and type in:

    >eclipse -clean

    or you can modify your desktop shortcut and append -clean at the end.

  • I uninstalled and re-installed everything. Things work as described, but it asks me to update when I start CCS. I think this is what caused the problems last time. I remember now that I updated the first time I started the program, before I went through the examples. I will try now to update again and start a new workspace after that update. I'll post what happens after that.

  • I updated the software as it requested on startup. I then restarted CCS and created a new workspace. It crashed with the same dialog boxes popping up as before. I then went to the cmd window, located the eclipse directory, and typed in "eclipse -clean" (with a space after "eclipse"). The CCS program appeared to run. I then opened a new workspace and the same crash happened.

    Am I correctly doing what you're asking me to?

  • Zach,

    What is the version that you are trying to upgrade from (what version comes on the CD)?  Also note that there is a full 4.1.2 image if you want to install that directly without having to deal with an update:

    http://processors.wiki.ti.com/index.php/Download_CCS

    Thanks

    ki

     

  • The version that comes on the CD is 4.1.0.02005

    That runs fine. When I upgrade, I upgrade to version 4.1.2.00027

    Also, I tried downloading the disk image from the link you just posted. I uninstalled everything, then installed from the disk image to a completely new directory. It too has the same issues as I've been having this entire time.

  • Hi Zach,

    I notice that you install CCS in C:\Program Files (x86)\Texas Instruments\

    Looking at this CCSv4 FAQ, it looks like that is not recommended on Windows 7 (or Vista) since that can interfere with the Update Manager. This may be the issue you are running into.

    ki

     

  • I read this somewhere too. So when I last reinstalled, I changed the directory to C:\TI and ended up with the same results. When I install 4.1.0.02005 from the CD that I received with the controlSTICK, the program works fine....it just asks me to update every time I start the program. When I update to 4.1.2.00027, I see this problem I've described all along. Also, I downloaded and installed the program from the link you suggested earlier. That program too is 4.1.2.00027, and it too does not work from a fresh install. It's error happens at the termination of the debugger with the same pop-up dialog. Thanks for continuing to look into this.

  • Zach,

    A couple things to try.  Look in Windows\SysWow64 (Win7 equivalent of System32) for xerces and xalan.  If they are present try renaming them with "_" in front.  I have hit a problem in 4.1.2 that is not present in 4.1.0 where CCS will load these libraries from the system directory instead of the local directory.  For me this causes a crash on connect but could also be impacting you.

    The other thing to do is to try renaming cTools.dll.  It is located in \ccsv4\emulation\analysis\bin  I have had that thing cause crashes on terminate and exit before.  If either of those help let us know as it could help track down the root cause.

     

    John

     

     

  • Hi John, I have this problem as well.  I do not have any of the files you listed.

    It is a really frustrating issue.

    Ian

  • same is here. I have this problem. it's very annoying.

     

    Li