• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 422 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.

Error in Debug UI error comprehension - xds100v2 CCS

K Md Feroz Irfan
Expert 7225 points
Other Parts Discussed in Thread: CCSTUDIO

Hello,

 

I get "Error in Debug UI" Error on trying to launch the EVMDM365 config on CCS4.2.07000  with xds100v2.

Dump from error log below.

 

Thanks!

Best Regards

Feroz

 

xds100 v2

java.lang.reflect.InvocationTargetException

at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:350)

at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:479)

at org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:272)

at org.eclipse.ui.internal.progress.ProgressManager$3.run(ProgressManager.java:894)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)

at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:929)

at org.eclipse.ui.internal.progress.ProgressManager.busyCursorWhile(ProgressManager.java:904)

at org.eclipse.debug.internal.ui.DebugUIPlugin.launchInForeground(DebugUIPlugin.java:844)

at org.eclipse.debug.ui.DebugUITools.launch(DebugUITools.java:518)

at com.ti.ccstudio.debug.core.launch.CCELaunchManager$1$1.run(CCELaunchManager.java:78)

at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)

at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)

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

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)

Caused by: java.lang.NoClassDefFoundError: com/ti/ccstudio/debug/memoryserver/MemoryServerManager

at com.ti.ccstudio.debug.core.memoryserver.MemoryServerProxy.<init>(MemoryServerProxy.java:67)

at com.ti.ccstudio.debug.core.cdi.model.TaskProxy.initialize(TaskProxy.java:524)

at com.ti.ccstudio.debug.core.cdi.model.Thread.<init>(Thread.java:54)

at com.ti.ccstudio.debug.core.cdi.model.DeviceThread.<init>(DeviceThread.java:11)

at com.ti.ccstudio.debug.core.cdi.model.DeviceTarget.<init>(DeviceTarget.java:89)

at com.ti.ccstudio.debug.core.cdi.model.Session.createDeviceTarget(Session.java:730)

at com.ti.ccstudio.debug.core.cdi.model.Session.internalInitializeSession(Session.java:359)

at com.ti.ccstudio.debug.core.cdi.model.Session.initializeSession(Session.java:288)

at com.ti.ccstudio.debug.core.cdi.model.Debugger.createDebuggerSession(Debugger.java:27)

at com.ti.ccstudio.debug.core.launch.BaseCCELaunchDelegate.doLaunch(BaseCCELaunchDelegate.java:321)

at com.ti.ccstudio.debug.core.launch.BaseCCELaunchDelegate.launch(BaseCCELaunchDelegate.java:267)

at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:657)

at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:583)

at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:764)

at org.eclipse.debug.internal.ui.DebugUIPlugin$5.run(DebugUIPlugin.java:837)

at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)

 

 

 

  • 0
    TI__Guru**** 162885 points

    Feroz,

    The log shows a line:

    Caused by: java.lang.NoClassDefFoundError: com/ti/ccstudio/debug/memoryserver/MemoryServerManager

    This implies that CCS was not able to load a component of the debugger.  This could be because it is missing some other element that the memory server is dependent on.  The build number you have listed above 4.2.0.07000 is an extremely old alpha release that was not released beyond a few people for use with some simulators.  It would not have been validated for use with DM365.  Please download a supported version of CCS such is 4.2.2.  You can get it here: http://processors.wiki.ti.com/index.php/Download_CCS

    Regards,

    John