topic Re: USBDM Hardware Debugging in KDS in OSBDM and TBDML

USBDM Hardware Debugging in KDS

ebee — Fri, 27 Jun 2014 08:54:54 GMT

When I try to set up USBDM Hardware Debugging in KDS I am getting the message 'An error occurred. See error log for more details'. The initial error message is 'net/sourceforge/usbdm/constants/UsbdmSharedConstants$InterfaceType'.

I have attached the error log report,

Re: USBDM Hardware Debugging in KDS

pgo — Sun, 29 Jun 2014 12:50:51 GMT

Hi Ian,

This looks like it can't find one of the plugins - probably because it failed to load or was the wrong version.

Can I find check the following:

What version of USBDM is installed?
When exactly is this error occurring? During the creation of the Debug Launch configuration?

Also please check the following:

Make sure there are not any bits left over from other versions of USBDM. For example if your installed an earlier version that didn't have the KDS installation and and manually copied the plugin files into the ...\Freescale\KDS_1.0.1\eclipse\dropins directory it will be necessary to delete these. Later installers don't have this problem.
Can you check the USBDM plugin versions installed in KDS. This can be done by
- Selecting : Help->About Kinetis Design Studio
- Then Installation Details button
- Select Plug-ins tab
- Click on the Plug-in Id column header to sort the column.
- The list should be similar to that shown below.

bye

Re: USBDM Hardware Debugging in KDS

ebee — Mon, 30 Jun 2014 07:28:09 GMT

I am running version 4.10.6.160 of the USBDM software. The error occurs when I try to create the Debug Launch configuration.

I did start off with an earlier version of USBDM that did not automatically detect the KDS installation so I used the configuration within the installer to install the plug ins into KDS1.0.1 etc. I have checked the contents of the dropins folder and all the files are date stamped 31/05/2014 which is the same as most of the files in my current pgo installation directory so it does not look as though anything has been left behind in here. I had an arm_devices.xml file left over from 4.10.6.140 in its own directory but that is the only file that I had modified. I have now deleted this file and the same error occurs.

For the plugins I have all the same file names as you on your list but the version numbers for everything is 4.10.6.201405311721 with the exception of USBDM Peripheral View which has the version number 1.0.0.201405311721.

I have had it working but recently for developing a multi processor system I have moved the USBDM device to a USB port on a hub rather than having it connected to my default debug port on my computer. The other device is debugging over J-Link. On the computer the USBDM device appears as a USB Composite device. On the hub the same device appears as a USBDM HCS08,HCS12,CFV1,ARM_SWD_BDM (I am debugging an ARM device over SWD). If I plug it into the computer USB port or the hub it still does not work within KDS.

If I connect the device to the PC USB port I can still use the ARM Programmer utility to program the micro controller, this does not work on the hub where it can not find a BDM device.

Re: USBDM Hardware Debugging in KDS

pgo — Tue, 01 Jul 2014 03:16:08 GMT

Hi Ian,

I'm a bit unclear about your description above. Does the plugin work with KDS if the BDM is plugged directly into the machine?

Anyway, I suspect there is a problem with loading one of the plugins (net.sourceforge.usbdm.constants). This handles paths to USBDM amongst other things.

Could I get you do do the following:

Open the Error Log (Window->Show View->Error Log) You may need to search for it under Other.
Clear the log using the Big Red X
Restart KDS
Check for any messages relating to USBDM in the log.
Try your failing process
Re-check the error log to see if there are any errors (other than the one you quoted above).

Thanks

bye

Re: USBDM Hardware Debugging in KDS

ebee — Wed, 02 Jul 2014 06:24:36 GMT

Hi pgo,

Sorry about the confusion. The plug is is not working within KDS where ever I plug the BDM in.

I have followed the instructions that you gave. On restarting KDS there was not any messages relating to USBDM in the log. When I try to connect to the debugger two new errors occur -

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

An error occurred while automatically activating bundle net.sourceforge.usbdm.contstants (464) in plugin org.eclispe.osgi

I have attached the full (or as much as I can get) error reports

Re: USBDM Hardware Debugging in KDS

pgo — Wed, 02 Jul 2014 06:47:52 GMT

Hi Ian,

The second exception looks more hopeful for a clue.

It appears that one of the plugins is throwing an exception when loading. Probably processing the USBDM paths but there isn't enough information to be sure.

I should have asked you to post the .metadata\.log file from the workspace you are using as this contains the entire log.

Would you please repeat clearing the log and triggering the exceptions?

Clearing the log first will reduce the "clutter" in the .log file.

I have installed USBDM 4.10.6.160 from sourceforge on another machine but it also appears to work OK with KDS.

Do you have any regular eclipse installations with USBDM installed. If so, are there any problems with them?

One last thing to check:

Open the USBDM configuration form the menu (USBDM->Configuration) and check that all the pages look OK.

Thanks

Re: USBDM Hardware Debugging in KDS

ebee — Thu, 03 Jul 2014 08:51:41 GMT

Hi,

The USBDM interface works fine within CodeWarrior 10.5 but is not seen from within 10.6 (10.6 was installed after USBDM so the plugins may not have been installed for this version).

Checking the configuration page when I click on USBDM -> Configure option I get the error message "Could Not Accept Changes. The current displayed page contains invalid values." Click on the OK button this window clears and the Preferences page appears. This is OK. Click throught to the ARM GDB Server then I get the familiar error message window.

As it is not appearing to be an easy solution I am tempted to uninstall both packages USBDM and KDS, make sure that their folders are all clear and reinstall them to see if this resolves the issue.

Below is the contents of the .log fileafter I try to connect to the USBDM in KDS.

Thanks

Ian

!ENTRY org.eclipse.jface 4 2 2014-07-03 09:19:44.079

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

!STACK 0

java.lang.NoClassDefFoundError: net/sourceforge/usbdm/constants/UsbdmSharedConstants$InterfaceType

at net.sourceforge.usbdm.gdb.ui.UsbdmDebuggerTab.createUsbdmParametersGroup(UsbdmDebuggerTab.java:674)

at net.sourceforge.usbdm.gdb.ui.UsbdmDebuggerTab.createControl(UsbdmDebuggerTab.java:1211)

at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:808)

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.handlePostSelect(StructuredViewer.java:1226)

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

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

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

at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:433)

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

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

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)

Caused by: org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter$TerminatingClassNotFoundException: An error occurred while automatically activating bundle net.sourceforge.usbdm.constants (464).

at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:124)

at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:469)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)

at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)

at org.eclipse.osgi.internal.loader.SingleSourcePackage.loadClass(SingleSourcePackage.java:35)

at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)

at java.lang.ClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClass(Unknown Source)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.defineClass(DefaultClassLoader.java:188)

at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClassHoldingLock(ClasspathManager.java:638)

at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.defineClass(ClasspathManager.java:613)

at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findClassImpl(ClasspathManager.java:574)

at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClassImpl(ClasspathManager.java:492)

at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:465)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:216)

at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:395)

at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:464)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)

at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)

at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)

at java.lang.ClassLoader.loadClass(Unknown Source)

at net.sourceforge.usbdm.cdt.ui.WorkbenchMainPreferencePage.createPathComposite(WorkbenchMainPreferencePage.java:201)

at net.sourceforge.usbdm.cdt.ui.WorkbenchMainPreferencePage.createContents(WorkbenchMainPreferencePage.java:68)

at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232)

at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1502)

at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1259)

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.preference.PreferenceDialog.showPage(PreferenceDialog.java:1253)

at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:675)

at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:709)

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

at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:705)

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.jface.preference.PreferenceDialog.selectSavedItem(PreferenceDialog.java:1055)

at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.selectSavedItem(FilteredPreferenceDialog.java:730)

at org.eclipse.jface.preference.PreferenceDialog$4.run(PreferenceDialog.java:376)

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

at org.eclipse.jface.preference.PreferenceDialog.createContents(PreferenceDialog.java:372)

at org.eclipse.jface.window.Window.create(Window.java:432)

at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)

at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.createDialogOn(WorkbenchPreferenceDialog.java:102)

at org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:192)

at org.eclipse.ui.dialogs.PreferencesUtil.createPreferenceDialogOn(PreferencesUtil.java:116)

at net.sourceforge.usbdm.cdt.ui.handlers.ConfigureHandler.execute(ConfigureHandler.java:26)

at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)

at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)

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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)

at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)

at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)

at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)

at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)

at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)

at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)

at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)

at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850)

at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743)

at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727)

at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662)

... 25 more

Caused by: org.osgi.framework.BundleException: Exception in net.sourceforge.usbdm.constants.Activator.start() of bundle net.sourceforge.usbdm.constants.

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)

at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)

at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)

at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:478)

at org.eclipse.osgi.internal.loader.BundleLoader.setLazyTrigger(BundleLoader.java:263)

at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:109)

... 98 more

Caused by: java.lang.UnsatisfiedLinkError: C:\Freescale\KDS_1.0.1\eclipse\configuration\org.eclipse.osgi\bundles\467\1\.cp\usbdm.4.dll: The specified procedure could not be found

at java.lang.ClassLoader$NativeLibrary.load(Native Method)

at java.lang.ClassLoader.loadLibrary1(Unknown Source)

at java.lang.ClassLoader.loadLibrary0(Unknown Source)

at java.lang.ClassLoader.loadLibrary(Unknown Source)

at java.lang.Runtime.loadLibrary0(Unknown Source)

at java.lang.System.loadLibrary(Unknown Source)

at net.sourceforge.usbdm.jni.Usbdm$LibraryLoader.<init>(Usbdm.java:1458)

at net.sourceforge.usbdm.jni.Usbdm.<clinit>(Usbdm.java:1518)

at net.sourceforge.usbdm.constants.Activator.loadUsbdmPaths(Activator.java:44)

at net.sourceforge.usbdm.constants.Activator.start(Activator.java:35)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)

at java.security.AccessController.doPrivileged(Native Method)

at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)

... 104 more

Re: USBDM Hardware Debugging in KDS

ebee — Thu, 10 Jul 2014 10:22:25 GMT

Hi pgo,

I tried going diown the uninstall route and that has not resolved the problems.

I uninstalled the KDS installation. Checked for any files / folders left behind and removed these.

I uninstalled the USBDM installation. Checked for any files / folders left behind and removed these.

Reinstalled KDS using the full installation. Opened KDS and checked for any updates - nothing to get.

Reinstalled USBDM from USBDM_4_10_6_160_Win.msi.

I still get the same errors when I try to connect via the KDS. I do not know what else I can try now.

regards

Ian

Re: USBDM Hardware Debugging in KDS

pgo — Sat, 12 Jul 2014 01:42:45 GMT

Hi Ian,

I'm sorry I've been unavailable for a little while.

The trace you posted indicates that the plugin is failing to load the the JNI (Java Native Interface) code and the associated DLL usbdm.4.dll.

I can't reproduce this on the machines I tried but it may be due to OS related problem.

Could you post details about the Operating System you are using and I will try to do some more specific testing.

Thanks

Re: USBDM Hardware Debugging in KDS

ebee — Mon, 14 Jul 2014 10:25:36 GMT

Hi pgo,

I am having identical problems on two machines. Both my laptop and desktop machine are running Windows 7. The laptop is running Home Premium version 6.1, Build 7601, Service pack 1. The desktop is running Windows 7 Professional service pack 1.

I uninstalled and re installed the software on the desktop but still get the same error. The laptop is still using original configuration.

Regards

Ian

Re: USBDM Hardware Debugging in KDS

ebee — Tue, 15 Jul 2014 14:56:19 GMT

Not sure if this is relevant yet but I my desktop computer has just completed a virus scan and it is reporting the following -

"";"The file is signed with a broken digital signature, issued by: Microsoft Windows., C:\Program Files (x86)\pgo\USBDM Drivers 1.2.0\Drivers\BDM_driver\x86\WdfCoInstaller01011.dll";"Infected"

"";"The file is signed with a broken digital signature, issued by: Microsoft Windows., C:\Program Files (x86)\pgo\USBDM Drivers 1.2.0\Drivers\JS16_driver\x86\WdfCoInstaller01011.dll";"Infected"

"";"The file is signed with a broken digital signature, issued by: Microsoft Windows., C:\Program Files (x86)\pgo\USBDM Drivers 1.2.0\Drivers\OLD_driver\x86\WdfCoInstaller01011.dll";"Infected"

Re: USBDM Hardware Debugging in KDS

pgo — Sat, 26 Jul 2014 07:03:03 GMT

Hi Ian,

The warning you are getting is because the drivers are unsigned. This shouldn't be causing any problem.

I've tried a couple more machines with KDS but I've been unable to reproduce the problem.

I will be uploading a new version shortly - Can you try that please.

bye

Re: USBDM Hardware Debugging in KDS

ebee — Fri, 01 Aug 2014 07:46:55 GMT

Hi pgo,

Thanks for looking into this I have not been able to make any further progress at my end so resorting to using CodeWarrior at the moment.

I will keep an eye out for the next update to USBDM.

Thanks

Ian

Re: USBDM Hardware Debugging in KDS

ebee — Tue, 19 Aug 2014 15:03:19 GMT

Hi pgo,

I have downloaded and installed the new version 4.10.6.170 and I am still getting the same error messages.

I have also downloaded the release version of KDS and the same error message occurs when I try to use the USBDM debugger in this one too.

Regards

Ian

Re: USBDM Hardware Debugging in KDS

ebee — Mon, 01 Sep 2014 11:02:48 GMT

Hi Pgo,

I have now wiped all copies of the Kinetis Design Studio and USBDM from my laptop. I have then done a clean install of the release version of KDS and the latest version of USBDM (4.10.6.180). I am pleased to report that I am able to program and debug my custom board using a MK60DN512VLQ10 device. I have configured the software to think that it is programming a MK60DN512ZM10 (the version 1 part) as you do not have the version 2 part listed in the 'Target Device' list. Do you have any plans to add this new part to the list of available targets. If not how easy is it for me to add this part on?

Thanks for your help to date

Ian

Re: USBDM Hardware Debugging in KDS

ebee — Tue, 02 Sep 2014 14:49:00 GMT

Hi pgo,

It appears that my optimism yesterday was ill founded. I returned to my program this morning and I find that I can not connect to the debugger within KDS once more. It was working fine when I shut down yesterday and this morning I am getting the same sets of error messages. How can this work one day and then not the next - I have not done anything differently or made any changes to the settings.

Regards

Ian

Re: USBDM Hardware Debugging in KDS

FredericoLuiz — Tue, 23 Dec 2014 10:49:54 GMT

Hi Ian,

can you debug now using USBDM hardware in KDS? I'd like to do so but until now I'm able.

If you get your problem solved, please let me know how did you make it.

Thanks.

Frederico

Re: USBDM Hardware Debugging in KDS

RichC — Tue, 27 Jan 2015 16:50:46 GMT

Hi pgo

Sorry for adding a "me too" post, but I've hit this same plugin JNI issue on Windows 7 x64. It's been working reliably for weeks, but today it refuses to cooperate! I guess it's probably something changed on my machine in the time I haven't been using KDS, but even clean reinstalls of KDS/USBDM don't fix it for me.

If I launch the USBDM ARM programmer from the start menu, it will happily detect the device, so it really just seems to be the JNI part of the eclipse plug in which is failing.

Any pointers on how I can start tracking things down or tools which may help please - I'm running out of places to look :-)

Further background, in case it sparks any ideas:

It may be a coincidence, but I recently did an upgrade JetBrains WebStorm (v8 to v9). I'd hope WebStorm and KDS wouldn't fight each other, but perhaps there is one global eclipse setting somewhere that I can't find - I tried checking the registry and env variables, but nothing obvious leapt out waving a big red flag.

In desperation I've now uninstalled WebStorm 9 entirely then reinstalled only KDS (1.1.1), USBDM (4.10.6.230) and drivers (1.3.0 Win x64). But alas the error is still there when I go to the USBDM menu > Configure

Thanks,

Rich.

Re: USBDM Hardware Debugging in KDS

RichC — Wed, 28 Jan 2015 00:48:51 GMT

So, I've managed to get this working again, but without really understanding what has gone wrong with the plugin system. Documenting as best I can here in case it helps future visitors.

The underlying error, reported by Windows, is actually no entry point found in usbdm.4.dll on the path: C:\Freescale\KDS_1.1.1\eclipse\configuration\org.eclipse.osgi\bundles\451\1\.cp\usbdm4.dll

At this point, there are only 3 dlls in the directory libgcc_s_dw2-1.dll, libstdc++-6.dll and usbdm.4.dll. I assume they are getting unpacked from net.sourceforge.usbdm.jni_4.10.6.201412010002.jar

However the dll sizes are smaller than the equivalent dlls in C:\Program Files (x86)\pgo\USBDM 4.10.6.230\ which is what I installed.

So, my work around was to copy the larger usbdm.4.dll over the top. This fixes the JNI issue when trying to open the USBDM > Configure menu. I can't guarantee it's the 'correct' workaround, but it's got me able to debug again :-)

Re: USBDM Hardware Debugging in KDS

pgo — Wed, 28 Jan 2015 05:39:33 GMT

Hi Richard,

I'm glad you found a work-around.

I will check the two DLLs and see if I can reconcile the differences.

In general I have found the JNI stuff a bit fragile so I don't usually change anything unless there is a reason. Because of this it is not surprising that the DLLs may be different builds i.e. updated in the main files but not in the plugin.

It is strange that the same plugin works with Codewarrior.

Can I check a few things:

Is your installation within the Program Files (x86) directory? The permissions applied by windows differ if installed there. I usually install Eclipse-based tools to a "Apps" directory to avoid issues.
It may be worthwhile to run Eclipse with the "-initialize" option e.g. "C:\Apps\Freescale\KDS_2.0.0\eclipse\kinetis-design-studio.exe -initialize" to cause KDS to rescan the plugins. Don't do this if it's working!

bye