Unable to Debug after KDS Update

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Debug after KDS Update

Jump to solution
8,753 Views
leifzars
Contributor IV

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 Environment1.8.0.RT7_b1515-1052
    Component Development Environment Documentation1.1.0.RT7_b1515-1052
    Documentation for Kinetis Design Studio V3.0.04.0.0
    Embedded Systems Register View (SFR)0.2.4.r178
    FSL Eclipse Updater Custom Actions Feature for Eclipse 4.4.x2.0.12.FSL_150303
    GNU ARM C/C++ Cross Compiler1.14.1.201508011813
    GNU ARM C/C++ J-Link Debugging3.2.1.201508011813
    GNU ARM C/C++ OpenOCD Debugging3.2.1.201508011813
    GNU ARM PEMicro Interface Debugging Support2.1.5.201507151627
    Kinetis Design Studio3.0.0
    Processor Expert for Kinetis3.0.0.RT7_b1515-0427
    Project of Projects1.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)

Labels (1)
1 Solution
570 Views
BlackNight
NXP Employee
NXP Employee

Good news: the KDS team has found a patch to re-enable J-Link debugging after that GNU ARM Eclipse update:

  1. Close KDS/Eclipse
  2. Download the attached 'plugins.zip'
  3. Extract the two plugins in that zip file to the 'plugins' subfolder of your installation folder (C:\freescale\kds_v3.0.0\eclipse\plugins)
  4. Confirm to replace the original files
  5. Restart KDS/Eclipse. Segger J-Link debugging is possible again.

We are looking into the root cause of the problem. But until there is a better fix, I recommend the above workaround.

We appologize again for that issue,

Erich

View solution in original post

35 Replies
571 Views
BlackNight
NXP Employee
NXP Employee

Good news: the KDS team has found a patch to re-enable J-Link debugging after that GNU ARM Eclipse update:

  1. Close KDS/Eclipse
  2. Download the attached 'plugins.zip'
  3. Extract the two plugins in that zip file to the 'plugins' subfolder of your installation folder (C:\freescale\kds_v3.0.0\eclipse\plugins)
  4. Confirm to replace the original files
  5. Restart KDS/Eclipse. Segger J-Link debugging is possible again.

We are looking into the root cause of the problem. But until there is a better fix, I recommend the above workaround.

We appologize again for that issue,

Erich

View solution in original post

472 Views
alexandrebyshim
Contributor II

Thanks,

It worked for me!

0 Kudos
472 Views
bothnor
Contributor I

I bought a FRDM-K64F a few weeks ago as my first go at mbed.

I installed KDS v3.0.0 yesterday for the first time on Debian Jessie 64bit on an old PC.

I've been working through the "Getting started with Kinetis SDK".

Encountered the problem listed above.

Installed the plugin patch as described and completed the Hello_world demo.

Thanks.

0 Kudos
472 Views
davezawislak
Contributor II

For Mac OS X:

in the folder "Applications" right click or option click on the KDS_3.0.0.app to bring up the contextual menu.

     Click on "Show Package Contents"

     Dig down into "Contents > eclipse > plugins" and replace the two files here

0 Kudos
472 Views
nhtshot
Contributor II

I encountered this while installed KSDK 1.3. It wanted to update several things in KDS, so I let it. Then, my J-link debugging was broken. I copied the plugins from the zip posted in this thread and then KDS would launch, but sit spinning forever.

In the end, I reinstalled KDS, installed the PE 3.0.1 update and was able to install KSDK 1.3 without installing the update that broke J-link.

0 Kudos
472 Views
frankvanhooft
Contributor III

I had a similar experience. After installing KDS 3.0 and the updates etc, Jlink programming was broken. I tried the plugins posted here by Erich and they appeared to improve things - programming got further along than it did earlier, but still would never complete and would eventually timeout. So I also uninstalled KDS, then reinstalled it without doing any updates, and voila, back in business. Happy days.

Frank.

frankvh.com

0 Kudos
472 Views
leeshaver
Contributor III

I ran into this issue while trying to fix another problem. As I had not yet seen this post, I eventually ran the repair tool in the KDS installer. I'm not sure if it functionally did the same thing as above, but it did fix the J-link debugger profile issue.

It may be wrong, but KDS says I still have the most recent version when I check for updates.

0 Kudos
472 Views
neilhancock
Contributor IV

The plugins worked for me as well. I only updated a couple of days ago. Many thanks for publishing the fix.

0 Kudos
472 Views
leifzars
Contributor IV

This works !

0 Kudos
472 Views
BlackNight
NXP Employee
NXP Employee

A much cleaner way than replacing the plugins with new files is to revert the Eclipse plugin installation.

See

Revert an Eclipse Update Installation | MCU on Eclipse

It requires that the previous versions of the plugins are available to Eclipse. So you might need to download the previous packs from SourceForge. This is explained in the above post too.

I hope this helps,Erich

0 Kudos
472 Views
kev1504
Contributor I

Hi there,

I had the same problem yesterday. I solved it with the following steps:

1. reinstall KDS

2. remove all Segger drivers and install the newest driver from: http://www.segger.com/download_jlink.html

3. link KDS with KSDK if you use it (install new software->archieve->eclipse udate in install_dir/KSDK/tools)

4. Then change the command line in the debug configurations from "set mem....inaccessible..etc." to "help set mem". Maybe this last step is optional but it works.

Thats it. I hope I could help you.

Regards,

Kevin

0 Kudos
472 Views
davepfaltzgraff
Senior Contributor I

On my Windows 7 Pro system, just doing steps 1 and 3 were sufficient. Just make sure you don't apply the updates or you'll be back where you were!

0 Kudos
472 Views
leifzars
Contributor IV

Segger is installed at C:\Freescale\KDS_3.0.0\segger for me, and i think it was installed with KDS. Do you think your solution will work for me?

0 Kudos
472 Views
BlackNight
NXP Employee
NXP Employee

The KDS debug configurations point to c:\freescale\kds_3.0.0\segger. But you can put there a newer Segger drop without problems (I'm doing this all the time).

Erich

0 Kudos
472 Views
BlackNight
NXP Employee
NXP Employee

as a piece of information: it seems that one plugin during the update did not got updated. So the workspace and the launch configs are fine, but not the version of the plugin.

The plugin in question is

ilg.gnuarmeclipse.debug.gdbjtag which has version 2.1.3.20153181632. it should be from 20150801.

Erich

472 Views
kev1504
Contributor I

I did not delete it there but in Window's system control in programs. I would say you try it but store it on another place before. I guess it is important to install the Segger software separately. Give it a try :smileywink:

0 Kudos
474 Views
ivadorazinova
NXP Employee
NXP Employee

Hello,

a bug ticket was filled on SourceForge and contacted the maintainer directly by Erich Styger.

https://sourceforge.net/p/gnuarmeclipse/bugs/192/

Best Regards,

Iva

0 Kudos
474 Views
ilg
Contributor I

initial investigations identified an update problem with the ilg.gnuarmeclipse.debug.gdbjtag plug-in, which is an internal dependency of the J-Link Debugging plug-in.

this problem is specific to KDS, the same plug-in is updated correctly on plain GNU ARM Eclipse setups.

for unknown reasons, it seems that KDS makes a wrong reference to the old version of ilg.gnuarmeclipse.debug.gdbjtag, preventing it to be updated at the new version required by the new J-Link plug-in.

I currently do not have a workaround, and I'm afraid the KDS team might need to fix the wrong dependency; until KDS is fixed just reinstall KDS without performing the update and it should work.

anyway, there is nothing wrong with your files; please refrain from hacking your workspace, your projects or your launch configurations, since there are great chances to ruin them.

regards,

Liviu Ionescu

0 Kudos
474 Views
radomirkozub-re
NXP Employee
NXP Employee

thanks, reinstalling without update has hepled

R.

0 Kudos
474 Views
davepfaltzgraff
Senior Contributor I

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

0 Kudos