EnergyTrace error

Giannis Roussos

Other Parts Discussed in Thread: ENERGYTRACE, MSP430F5528

Hello,

I am trying to use an EXP432P401R Launchpad to measure the current consumption of a custom MSP430F5528 board. I do not necessarily need to be debugging the MSP430 while measuring current, so I believe using the EXP432 launchpad in standalone EnergyTrace mode should be OK.

However, when I press the EnergyTrace button in the CCS Edit view the button remains pressed for ~10 seconds but nothing happens. Looking at the CCS log file I see the following exception:

!ENTRY org.eclipse.ui 4 0 2016-06-29 20:07:18.604
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.IllegalArgumentException: No enum constant com.ti.dvt.energytrace.core.RuntimeParameter.EnumTargetDevice.RF432
	at java.lang.Enum.valueOf(Enum.java:236)
	at com.ti.dvt.energytrace.core.RuntimeParameter$EnumTargetDevice.valueOf(RuntimeParameter.java:1)
	at com.ti.dvt.energytrace.af.PowerActivity$DebuggerTargetInfo.fromCCXML(PowerActivity.java:1198)
	at com.ti.dvt.energytrace.af.PowerActivity$DebuggerTargetInfo.<init>(PowerActivity.java:1166)
	at com.ti.dvt.energytrace.af.PowerActivity.launchHiddenDS(PowerActivity.java:1317)
	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:228)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
	at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
	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:380)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)

Also when I go to the EnergyTrace settings in CCS Preferences and press Apply/OK I get the following:

!ENTRY org.eclipse.jface 4 0 2016-06-29 19:59:07.603
!MESSAGE java.lang.NumberFormatException: empty String
!STACK 0
java.lang.NumberFormatException: empty String
	at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1020)
	at java.lang.Double.valueOf(Double.java:504)
	at java.lang.Double.<init>(Double.java:597)
	at com.ti.dvt.energytrace.PreferencePage$DoubleFieldEditor.doStore(PreferencePage.java:223)
	at org.eclipse.jface.preference.FieldEditor.store(FieldEditor.java:683)
	at org.eclipse.jface.preference.FieldEditorPreferencePage.performOk(FieldEditorPreferencePage.java:344)
	at org.eclipse.jface.preference.PreferenceDialog$12.run(PreferenceDialog.java:925)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
	at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:909)
	at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:409)
	at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:168)
	at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
	at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
	at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
	at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
	at org.eclipse.jface.window.Window.open(Window.java:803)
	at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
	at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63)
	at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
	at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
	at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
	at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
	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:380)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1515)

The only way to get the EnergyTrace window to even appear is to press the EnergyTrace button in while debugging a project, but even then pressing the start button has no effect, i.e. the button flashes to red for a sec then returns to green, time remains at 0sec and no data are plotted in the Energy or Power graphs.

I am using CCS 6.1.3 and have tested with the EXP432 both connected and not connected to USB and the target connection in EnergyTrace settings set to XDS110 and USB.

Shouldn't I be able to use the EXP432 in standalone EnergyTrace mode? Is there some other setting that I am missing?

over 9 years ago

0 William Goh over 9 years ago

TI__Genius 16195 points

Hi,

CCS should support standalone EnergyTrace with MSP432 LaunchPads.

But, you would first need to point EnergyTrace to launch using XDS110 by going to Windows --> Preferences --> Code Composer Studio --> Advanced Tools --> EnergyTrace Technology. And change the Target Connection from USB1 to XDS110.

Regards,

William

0 Giannis Roussos over 9 years ago in reply to William Goh

Expert 2290 points

As I wrote in the first post I have already tried with both XDS110 and USB connection but get the errors described above.

0 Robert Cowsill over 9 years ago

Guru 16361 points

Giannis Roussos said:
The only way to get the EnergyTrace window to even appear is to press the EnergyTrace button in while debugging a project, but even then pressing the start button has no effect, i.e. the button flashes to red for a sec then returns to green, time remains at 0sec and no data are plotted in the Energy or Power graphs.

I've not seen the first problem you were facing with running EnergyTrace outside of a debug session, but I have had this problem while debugging. I think I get around it by pausing and running the target, which triggers EnergyTrace capture if the window is already open. After that the record button starts to work.

0 William Goh over 9 years ago in reply to Giannis Roussos

TI__Genius 16195 points

What revision of EXP432P401R LaunchPad are you using?

0 Katie Pier over 9 years ago in reply to William Goh

TI__Guru 73236 points

Hi Giannis and Robert,

Can you comment on the revision of the Launchpad that you had when you saw the issue, as William asked above? It may help to determine your issue. You can find the revision number silkscreened on the board near where the board name is silkscreened. Could you also comment on the revision marked on the MSP432 device on the board?

Regards,
Katie

0 Giannis Roussos over 9 years ago in reply to Katie Pier

Expert 2290 points

Hi, the Launchpad is Rev 1.0, the MSP432 is REV B

Best,

Giannis

0 Katie Pier over 9 years ago in reply to Giannis Roussos

TI__Guru 73236 points

Hi Giannis,

We talked to our tools team and they recommended trying this potential workaround:
Find the file <ccsv6 install location, default is C:\ti\ccsv6>\ccs_base\dvt_4.1.0.xxxxxxxxxxxx\AnalysisLibrary\DataProviders\EnergyTrace\EnergyTrace_RF432_XDS110.ccxml
Take this file and remove it (my suggestion would be to move it to your desktop or somewhere for safe-keeping just in case, but get it out of CCS path for this test). They said after this if a valid target is connected EnergyTrace should start.

Can you try this and report back if it helps resolve the issue?

Regards,
Katie

0 Katie Pier over 9 years ago in reply to Katie Pier

TI__Guru 73236 points

Hi Giannis,

Did this resolve your issue?

Regards,
Katie

0 Giannis Roussos over 9 years ago in reply to Katie Pier

Expert 2290 points

Hi Katie,

I tried (re)moving the EnergyTrace_RF432_XDS110.ccxml file but then EnergyTrace fails to start saying that no XDS110 is found.

0 Bruce Lee (SDO) over 9 years ago in reply to Giannis Roussos

TI__Prodigy 690 points

Hi,

There are 2 similar files in the mentioned folder: "EnergyTrace_MSP432_XDS110.ccxml" and "EnergyTrace_RF432_XDS110.ccxml".

Please check that only the "RF432" one is removed and keep the "MSP432". Also make sure you have MSP432 Launchpad connected to your PC.

0 Katie Pier over 9 years ago in reply to Bruce Lee (SDO)

TI__Guru 73236 points

Hi Giannis,

Did Bruce Lee (SDO) 's suggestion help resolve your issue?

Regards,
Katie

**Attention** This is a public forum

MSP low-power microcontrollers

MSP low-power microcontroller forum

EnergyTrace error