• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 796 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS Debugger Stopped Working

matt wilson
Prodigy 130 points

Other Parts Discussed in Thread: CCSTUDIO, MSP430F5529

The debugger just suddenly stopped working. I'm getting a pop up error:

An internal error occurred during 'Creating Debug Server'.

Please see the Error Log for details.

When I click details, it shows a long error message, but the copy command doesn't copy it. I have no idea where the error log is.
Matt

  • 0
    TI__Guru**** 480691 points

    Hi Matt,

    Please provide more details about your environment.

    What is the full version number of your CCS installation?

    What device are you using?

    What emulator are you using?

    matt wilson said:
    I have no idea where the error log is.

    See the below link on how to generate a zip of the diagnostic logs:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 130 points

    I found how to view errors. Pressing the "CCS Support Activities" menu item causes an error:

     

    org.mozilla.xpcom.XPCOMException: Could not createInstance(@ti.com/DSLogger1;1,{88de5d06-9f14-4628-bc1c-9cef687a039e})Java/XPCOM bridge: exception while executing submit() with parameterorg.mozilla.xpcom.internal.XPCOMJavaProxy$3@17a0b4d.

    org.mozilla.xpcom.XPCOMException: The function "createInstanceByContractID" returned an error condition  (0x80040154)  (0x80004005)  (0x80004005)

     

    at com.ti.debug.engine.xpcom.Runtime.createComponent(Runtime.java:229)

     

    at com.ti.logger.impl.DSLogger.<init>(DSLogger.java:29)

     

    at com.ti.logger.impl.DSLogger.instance(DSLogger.java:46)

     

    at com.ti.logger.impl.DSLogger.getLoggerConfiguration(DSLogger.java:67)

     

    at com.ti.ccstudio.ui.support.internal.DebugServerSupportActivity.getLogLocation(DebugServerSupportActivity.java:45)

     

    at com.ti.ccstudio.ui.support.internal.dialog.SupportDialog.updateActivity(SupportDialog.java:253)

     

    at com.ti.ccstudio.ui.support.internal.dialog.SupportDialog.insertActivities(SupportDialog.java:271)

     

    at com.ti.ccstudio.ui.support.internal.dialog.SupportDialog.createDialogArea(SupportDialog.java:186)

     

    at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:165)

     

    at org.eclipse.jface.window.Window.create(Window.java:426)

     

    at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1124)

     

    at org.eclipse.jface.window.Window.open(Window.java:785)

     

    at com.ti.ccstudio.ui.actions.SupportActivityActionDelegate.run(SupportActivityActionDelegate.java:35)

     

    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)

     

    at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:229)

     

    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)

     

    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)

     

    at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)

     

    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

     

    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)

     

    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823)

     

    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)

     

    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)

     

    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)

     

    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)

     

    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

     

    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:97)

     

    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)

     

    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)

     

    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)

     

    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)

     

    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)

     

    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.eclipse.core.launcher.Main.invokeFramework(Main.java:336)

     

    at org.eclipse.core.launcher.Main.basicRun(Main.java:280)

     

    at org.eclipse.core.launcher.Main.run(Main.java:996)

     

    at org.eclipse.core.launcher.Main.main(Main.java:971)

     

  • 0 in reply to Ki
    Prodigy 130 points

    I'm using CCS 4.2.4. With a USB FET and an MSP430F5529

  • 0 in reply to matt wilson
    TI__Guru**** 480691 points

    The contents of the error log look similar to what has been reported in a previous thread:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/130506/467526.aspx

     

  • 0 in reply to Ki
    Prodigy 130 points

    That link does not work.

  • 0 in reply to matt wilson
    TI__Guru**** 480691 points

    There was a syntax error in the link. Try the below:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/130506/467526.aspx

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 130 points

    Uninstalling and then reinstalling seems to have worked. It locked up and failed on the first re-install, but the second try seems to have worked.