LPCXpresso 8.1.0 vs Evaluation Board LPCXpresso LPC1769

[lpcware]

Content originally posted in LPCWare by sc_cstjean on Mon Feb 29 20:23:01 MST 2016
I have tried the new version of LPCXpresso IDE v8.1.0 but the IDE seems not be able to communicate with de the debugger part of the board.

I got this exception:
Cannot write to server: not open
  at com.crt.debugcommon.emulator.client.RedlinkServerClient.getWriter(RedlinkServerClient.java:621)
  at com.crt.debugcommon.emulator.client.RedlinkServerClient.writeln(RedlinkServerClient.java:1247)
  at com.crt.debugcommon.emulator.client.RedlinkServerClient.send(RedlinkServerClient.java:996)
  at com.crt.debugcommon.emulator.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1060)
  at com.crt.debugcommon.emulator.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1041)
  at com.crt.debugcommon.emulator.client.RedlinkServerClient.sendReceive(RedlinkServerClient.java:1028)
  at com.crt.debugcommon.emulator.client.RedlinkServerClient.probeList(RedlinkServerClient.java:923)
  at com.crt.debugcommon.emulator.common.redlinkserver.RedlinkServerEmuHandler.discoverEmulators(RedlinkServerEmuHandler.java:213)
  at com.crt.debugcommon.emulator.win.AbstractWinServerProbe.discoverEmulators(AbstractWinServerProbe.java:78)
  at com.crt.debugcommon.emulator.EmulatorsDB.getEmus(EmulatorsDB.java:396)
  at com.crt.debugcommon.emulator.EmulatorsDB.getEmulatorInfo(EmulatorsDB.java:303)
  at com.crt.debugcommon.emulator.EmulatorsDB.getAvailableEmulators(EmulatorsDB.java:219)
  at com.crt.debugcommon.emulator.TargetDiscovery.probeDiscovery(TargetDiscovery.java:576)
  at com.crt.debugcommon.emulator.TargetDiscovery.probeDiscovery(TargetDiscovery.java:539)
  at com.crt.debugcommon.utils.LaunchScriptUtils.getEmulatorInfo(LaunchScriptUtils.java:351)
  at com.crt.debugcommon.utils.LaunchScriptUtils.init(LaunchScriptUtils.java:626)
  at com.crt.debugcommon.utils.LaunchScriptUtils.<init>(LaunchScriptUtils.java:242)
  at com.crt.debugcommon.utils.LaunchScriptUtils.<init>(LaunchScriptUtils.java:226)
  at com.crt.dsfdebug.dsf.services.TargetDiscoveryService.getTargetDiscovery(TargetDiscoveryService.java:147)
  at com.crt.dsfdebug.dsf.override.CRTFinalLaunchSequence$TargetDiscoveryJob.runInUIThread(CRTFinalLaunchSequence.java:102)
  at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:97)
  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:4155)
  at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
  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:62)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:497)
  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)

I see the "LPC-Link Debug Probe v1.1" in the devices list

I rolled back to LPCXpresso 8.0.0 and the debug is now working. I will continue to use this version.

It seems that the same problem is present with the new board with the CMSIS-DAP interface.

Thank you for your attention for this issue

Sylvain Cote

[lpcware]

bump

[lpcware]

Content originally posted in LPCWare by sc_cstjean on Tue Mar 01 09:49:50 MST 2016
Yes, I am using non-english (french) windows 64 pro 10 version. And, I have read and executed the workaround solution and it work. I will use this until a patch will be available.

Thank you

[lpcware]

Content originally posted in LPCWare by R2D2 on Tue Mar 01 01:01:04 MST 2016

---

Quote: sc_cstjean
I have tried the new version of LPCXpresso IDE v8.1.0 but the IDE seems not be able to communicate with de the debugger part of the board.

---

Are you using a non-English (french ?) Windows version?

The actual 8.1.0 problem and a workaround is described here:

https://www.lpcware.com/content/forum/lpcxpresso-810597-lpc-link2-not-working-anymore