• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1443 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: CCS 8.1.0: Using EnergyTrace Without Debugging Still Possible?

Rei Vilo
Guru 23935 points
Other Parts Discussed in Thread: ENERGYTRACE, MSP-EXP430FR5969, LAUNCHXL-CC1350

Tool/software: Code Composer Studio

With CCS 8.0.0, it was possible to use EnergyTrace without launching a debugging session.

It was very handy as I could use the EnergyTrace from a LaunchPad with that feature (e.g. MSP-EXP430FR5969) and target a LaunchPad without it (e.g. LAUCNHXL-CC1350).

I've updated to CCS 8.1.0: I can't manage to get it work. Pressing the EnergyTrace on the toolbar does nothing.

I need first to start a debugging session and then launch EnergyTrace, for example against the MSP-EXP430FR5969. I can no longer use EnergyTrace against the LAUNCHXL-CC1350.

 

  • 0
    Guru 92251 points

    Rei VILO said:
    I've updated to CCS 8.1.0: I can't manage to get it work. Pressing the EnergyTrace on the toolbar does nothing.

    I can repeat that, with CCS 8.1.0.00011 running under Ubuntu 16.04 LTS.

    After pressing the EnergyTrace button on the toolbar the following error appears in the Eclipse log file, with com.ti.dvt.energytrace classes appearing in the Eclipse java backtrace:

    !ENTRY org.eclipse.ui 4 0 2018-06-16 21:51:56.229
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.NullPointerException
	at com.ti.dvt.energytrace.views.DSManager$DSApp.launch(DSManager.java:274)
	at com.ti.dvt.energytrace.af.PowerActivity.launchHiddenDS(PowerActivity.java:1549)
	at com.ti.dvt.energytrace.IDEHandler.detectCfg(IDEHandler.java:290)
	at com.ti.dvt.energytrace.IDEHandler.launchHiddenDS(IDEHandler.java:376)
	at com.ti.dvt.energytrace.IDEHandler.preNonDebugStartup(IDEHandler.java:220)
	at com.ti.dvt.energytrace.IDEHandler.startupDashboard(IDEHandler.java:438)
	at com.ti.dvt.energytrace.actions.DashboardAction.runET(DashboardAction.java:102)
	at com.ti.dvt.energytrace.actions.DashboardAction.run(DashboardAction.java:55)
	at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:247)
	at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:219)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
	at org.eclipse.jface.action.ActionContributionItem.lambda$5(ActionContributionItem.java:436)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4602)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4183)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1499)

  • 0 in reply to Chester Gillon
    Guru 23935 points

    @Chester Gillon Glad to know I am not alone!

    I've reinstalled CCS 7.4.0 to use EnergyTrace, and it works fine.

  • 0
    TI__Guru**** 173310 points

    Rei VILO said:
    I've updated to CCS 8.1.0: I can't manage to get it work. Pressing the EnergyTrace on the toolbar does nothing.

    This is a known issue in CCS 8.1.0. Unfortunately the fix for this did not make it into the release on time. The fix will be in the next CCS release. 

    Sorry about the inconvenience.