topic Re: Unable to Debug after KDS Update in Kinetis Design Studio

Unable to Debug after KDS Update

leifzars — Mon, 03 Aug 2015 16:22:23 GMT

After a fresh install of KDS, everything works. Once I do a software update I can no longer debug.

I have tried starting a new work space and that doesn't help.

When I select Debug Configuration I get the following error:"An error has occurred. See error log for more details. ilg/gnuarmeclipse/debug/gdbjtag/data/CProjectAttributes"

I would attache the log file, but I have no clue where the folder ilg is.

This is my versions after the update:

Component Development Environment	1.8.0.RT7_b1515-1052
Component Development Environment Documentation	1.1.0.RT7_b1515-1052
Documentation for Kinetis Design Studio V3.0.0	4.0.0
Embedded Systems Register View (SFR)	0.2.4.r178
FSL Eclipse Updater Custom Actions Feature for Eclipse 4.4.x	2.0.12.FSL_150303
GNU ARM C/C++ Cross Compiler	1.14.1.201508011813
GNU ARM C/C++ J-Link Debugging	3.2.1.201508011813
GNU ARM C/C++ OpenOCD Debugging	3.2.1.201508011813
GNU ARM PEMicro Interface Debugging Support	2.1.5.201507151627
Kinetis Design Studio	3.0.0
Processor Expert for Kinetis	3.0.0.RT7_b1515-0427
Project of Projects	1.1.8.201504141312

I found this log snip-it in my workspace folder, it looks like it might help

!ENTRY org.eclipse.jface 4 2 2015-08-03 11:14:48.447

!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".

!STACK 0

java.lang.NoClassDefFoundError: ilg/gnuarmeclipse/debug/gdbjtag/data/CProjectAttributes

at ilg.gnuarmeclipse.debug.gdbjtag.jlink.ui.TabDebugger.initializeFrom(TabDebugger.java:1199)

at org.eclipse.debug.ui.AbstractLaunchConfigurationTabGroup.initializeFrom(AbstractLaunchConfigurationTabGroup.java:90)

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupWrapper.initializeFrom(LaunchConfigurationTabGroupWrapper.java:201)

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:764)

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$8.run(LaunchConfigurationTabGroupViewer.java:635)

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

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:652)

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput0(LaunchConfigurationTabGroupViewer.java:613)

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:588)

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:960)

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:573)

at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)

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:178)

at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)

at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1217)

at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1243)

at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)

at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)

at org.eclipse.jface.util.OpenStrategy$1$2.run(OpenStrategy.java:440)

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

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

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

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

at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)

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

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154)

at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:611)

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

at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:619)

at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:552)

at org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(OpenLaunchDialogAction.java:82)

at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)

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:4353)

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

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

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

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)

at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)

at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

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

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

at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)

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(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:648)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)

at org.eclipse.equinox.launcher.Main.run(Main.java:1465)

Re: Unable to Debug after KDS Update

jeffreyerickson — Mon, 03 Aug 2015 20:27:25 GMT

I am having the same problem. To get to the log file, in KDS go to Help->About Kinetis Design Studio->Installation Details->Configuration->View Error Log.

It seems the problem is a NoClassDefFoundError at ilg.gnuarmeclipse.debug.gdbjtag.jlink.ui.TabDebugger.setDefaults(TabDebugger.java:1969)

The package name seems to suggest this may only impact jlink debuggers. That package install date on my machine and on your info above is dated August 1. So, it's a new package released over the weekend that caused us to bump into this difficulty now.

Re: Unable to Debug after KDS Update

ivadorazinova — Tue, 04 Aug 2015 08:36:04 GMT

Hello Leif Zars and Jeffrey Erickson,

Please, what do you use for the system? Do you have Linux distribution 64-bit?

I´m going to try it in Ubuntu 14.04.02, please wait for a moment.

Have a nice day!

Iva

Re: Unable to Debug after KDS Update

peterruesch — Tue, 04 Aug 2015 12:55:55 GMT

my project was also rendered useless after performing an update :smileysad:

very annoying.

trying to reinstall KDS without doing the "check for updates" step from within eclipse...

Re: Unable to Debug after KDS Update

ivadorazinova — Tue, 04 Aug 2015 12:58:25 GMT

Hello Peter,

please wait, I´m trying it on another computer.

Iva

Re: Unable to Debug after KDS Update

peterruesch — Tue, 04 Aug 2015 13:01:41 GMT

i have reinstalled KDS and was able to debug again... luckily!

Re: Unable to Debug after KDS Update

PetrK — Tue, 04 Aug 2015 14:39:59 GMT

Hello,

I'm also facing to same or similar issue. After update I'm not able to create "GDB SEGGER J-link Debugging" configuration. All other (Hardware, OpenOCD, PEMicro) are OK.

Version of j-link software is 5.0.1e.

Regards,

Petr

Re: Unable to Debug after KDS Update

jeffreyerickson — Tue, 04 Aug 2015 14:50:21 GMT

I use a Segger J-Link debugger on Windows 7 64-bit.

I followed your procedure and I still can't debug. My log is nearly identical to the one posted by the OP.

Re: Unable to Debug after KDS Update

ivadorazinova — Tue, 04 Aug 2015 15:28:55 GMT

Hello Petr Kolesnikov , Peter Ruesch and Leif Zars.

I tried it on another computer from the beginning and it works without problems. Actually I use for FRDM-KL03Z OpenSDA.

Please,when the error message comes? /can you show us error message? or it is impossible to debug without any message? Did you try it in other terminal? (putty, tera term, terminate...)

Just few points to check:

Do you have correctly set Debugger?

Did you try to load the newest firmware for the interface?
Have you tried Jennie Zhang´s mentioned steps?

Thank you.

Best Regards,

Iva

Re: Unable to Debug after KDS Update

ivadorazinova — Tue, 04 Aug 2015 15:39:34 GMT

Hello Petr,

can you show the screenshot of the error?

Thank you,

Best Regards,

Iva

Re: Unable to Debug after KDS Update

PetrK — Tue, 04 Aug 2015 15:49:19 GMT

Re: Unable to Debug after KDS Update

davepfaltzgraff — Tue, 04 Aug 2015 20:07:45 GMT

Having the same problem here on two different PCs - both Windows 7 Pro.

Re: Unable to Debug after KDS Update

PetrK — Wed, 05 Aug 2015 08:48:01 GMT

Hello Iva,

When I updated KDS, the debugging was impossible, because almost all setting were missing. So, I deleted debugging configuration and tried to create new one and then the error occurred.

I tried to delete .metadata directory and so effectively delete workspace settings and create new one, unfortunately without success.

I'll try to create new project and check if it works.

Petr

Re: Unable to Debug after KDS Update

ivadorazinova — Wed, 05 Aug 2015 08:52:43 GMT

Hello Petr Kolesnikov and David Pfaltzgraff,

Yes, it is the same on my side - and when you try to manually set it, it does not help because the Apply and Debug are not possible - are gray..

Thank you for pointing out us!

I will reproduce it and let you know.

Iva

Re: Unable to Debug after KDS Update

PetrK — Wed, 05 Aug 2015 08:59:26 GMT

I tried to create new project for frdm-k64f board and same happened when I tried to open the configuration:

Log message:

!ENTRY org.eclipse.jface 4 2 2015-08-05 10:52:37.796