• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 2369 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.

Integrating Trace32 with Code Composer Studio v6

kushal patel
Intellectual 330 points


Hello Everyone,

I need to integrate (or trying to) lauterbach's trace32 with CCS 6. In Eclipse, as lauterbach claims to be this task straightforward, this is not simple for CCS.

I am particularly interested to know the steps or direction to obtain this.

After downloading plug-ins from "Install new softwares" for lauterbach, I can see trace32 button in "Debug Configurations". But if I click on this to create an instance, I see below errors.

!ENTRY org.eclipse.jface 4 2 2015-02-12 22:08:07.239
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0
java.lang.NoSuchMethodError: org.eclipse.cdt.launch.internal.ui.LaunchMessages.getString(Ljava/lang/String;)Ljava/lang/String;
    at org.eclipse.cdt.launch.internal2.ui.AbstractCDebuggerTab.getName(AbstractCDebuggerTab.java:264)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:797)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:739)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:626)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:643)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:605)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:581)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:943)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:562)
    at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:888)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
    at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
    at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:886)
    at org.eclipse.jface.viewers.StructuredViewer.setSelection(StructuredViewer.java:1726)
    at org.eclipse.jface.viewers.TreeViewer.setSelection(TreeViewer.java:1139)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.handleConfigurationAdded(LaunchConfigurationView.java:283)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.access$1(LaunchConfigurationView.java:272)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView$2.run(LaunchConfigurationView.java:261)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4145)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3762)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
    at org.eclipse.jface.window.Window.open(Window.java:802)
    at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1134)
    at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:604)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
    at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:612)
    at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:546)
    at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:81)
    at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
    at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
    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.equinox.launcher.Main.invokeFramework(Main.java:636)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1450)

I will be more than happy if someone can guide me from here!

Thanks in advance,

Kushal

  • 0
    TI__Guru**** 472721 points
    Hi Kushal,
    This is a configuration not normally supported by CCS. However, CCS does use stock Eclipse so if there is a Lauterbach Eclipse plug-in, it is theoretically possible to get it to work. I checked Lauterbach's documentation it looks like up to Eclipse 4.2 is supported. The latest version of CCSv6 is based off Eclipse 4.3. A little newer but close enough that it may work. I would check with Lauterbach support to see if they can help you.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 330 points

    Hello Ki-Soo,

    Thanks for the prompt response. Seems like Lauterbach has plug-in for Eclipse 4.2 or greater versions but I noticed a strange thing.

    On my Linux host (Ubuntu 10.04 & 12.04),  CCS6.0.1 is able to create lauterbach debug configuration.

    But above mentioned error (Pls see screenshot) only comes in Windows 7 PC (same CCS 6.0.1- based on eclipse v4.3.1).

    Why with same CCS & eclipse versions on different hosts make difference?

    As most of development with the lauterbach is going on Windows, this will be an issue for user. Any help will be appreciated.

    Thanks & regards,

    Kushal

  • 0 in reply to kushal patel
    TI__Guru**** 472721 points

    Kushal,
    The CCS team does not have much experience with Lauterbach since it is not a debug connection that we normally support. Contacting Lauterbach support directly is your best bet. Another thing to try is using stock Eclipse 4.3.1 on Windows and see if this works for you. Sorry.

    ki

  • 0 in reply to Ki
    Intellectual 330 points

    Ok Ki,

    But if linux CCSv6 launches debug configuration whereas windows can't then don't you think it is more or less CCS relating thing that makes difference. I just want to figure out what is difference between two CCS installers and underlying eclipse framework(though of same version).

    Hope you will understand my point and guide.

    Thanks again,

    Kushal

  • 0 in reply to kushal patel
    Intellectual 330 points
    Just to update on this!
    I was installing wrong plug-ins from lauterbach.
    I uninstalled them and then did fresh installation from www.lauterbach.com/eclipse and now I am able to create configuration both on Linux as well as Windows CCS6.
    Kushal