LPCXpresso IDE debugging tools stopped working

[lpcware]

Content originally posted in LPCWare by mridup on Wed Oct 15 03:56:44 MST 2014
Hi,
Some of the debugging options within the IDE has stopped working without any reason.
E.g. The buttons Resume, Suspend, Step Over, Step Into etc are no longer highlighted and cannot be clicked/used.
Only "Run to Line" optionn works or is possible to be used.

Restarting the LPCXpresso IDE did not help.

Has this problem been seen by someone ever?

Regards,
Mridu

[Anonymous]

This problem still exists. I used LPCXpresso 7.8.0, 8.1.0 and now I am using 8.2.2

After installation everything works fine but at some point in time the debug buttons (and menu options) will randomly be grayed out when starting a debugging session.

Placing breakpoints and "run to line" still work but that's not enough. We really need system that works reliably.

Rob

[lpcware]

Content originally posted in LPCWare by DSchwarzfischerMEGALine on Fri Mar 11 05:51:13 MST 2016
Hi,
when debug works wrong, its never the same thing to do,
to make the debugger working right.

Here are two logs, one the debugger is working right, the second, the debugger fault:

[collapse title=<working right>]
!SESSION 2016-03-11 13:21:37.108 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_60
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments:  -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.core.resources 2 10035 2016-03-11 13:21:40.197
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.

!ENTRY org.eclipse.ui 4 4 2016-03-11 13:21:43.116
!MESSAGE Plugin org.eclipse.cdt.ui, extension org.eclipse.ui.decorators, id org.eclipse.cdt.internal.ui.CustomBuildSettingsDecorator: Duplicate id found: org.eclipse.cdt.internal.ui.CustomBuildSettingsDecorator

!ENTRY org.eclipse.ui 4 4 2016-03-11 13:21:43.116
!MESSAGE Plugin org.eclipse.cdt.ui, extension org.eclipse.ui.decorators, id org.eclipse.cdt.internal.ui.CustomBuildSettingsDecorator: Unknown extension tag found: decorator

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2016-03-11 13:22:13.217
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-target-download
Error message from debugger back end:
Error finishing flash operation
at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:109)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:97)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: Error finishing flash operation
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:927)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:756)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2016-03-11 13:22:13.218
!MESSAGE Failed to execute MI command:
-target-download
Error message from debugger back end:
Error finishing flash operation
!STACK 0
java.lang.Exception: Error finishing flash operation
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:927)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:756)

!ENTRY com.crt.dsfdebug 4 0 2016-03-11 13:22:13.624
!MESSAGE 15: Target error from Commit Flash write
!SUBENTRY 1 com.crt.dsfdebug 4 0 2016-03-11 13:22:13.624
!MESSAGE 15: Target error from Commit Flash write
!SUBENTRY 1 com.crt.dsfdebug 4 0 2016-03-11 13:22:13.624
!MESSAGE System rejected access at location 0x00000000 - verify Population of memory and peripherals

[/collapse]

[collapse title=<debugging fault>]
!SESSION 2016-03-11 13:18:11.393 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.8.0_60
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments:  -os win32 -ws win32 -arch x86 -data N:\Ucontrol\LPC4357\Modultestprogramm\0101

!ENTRY org.eclipse.ui 4 4 2016-03-11 13:18:16.044
!MESSAGE Plugin org.eclipse.cdt.ui, extension org.eclipse.ui.decorators, id org.eclipse.cdt.internal.ui.CustomBuildSettingsDecorator: Duplicate id found: org.eclipse.cdt.internal.ui.CustomBuildSettingsDecorator

!ENTRY org.eclipse.ui 4 4 2016-03-11 13:18:16.059
!MESSAGE Plugin org.eclipse.cdt.ui, extension org.eclipse.ui.decorators, id org.eclipse.cdt.internal.ui.CustomBuildSettingsDecorator: Unknown extension tag found: decorator

!ENTRY org.eclipse.cdt.dsf 4 10005 2016-03-11 13:18:48.351
!MESSAGE Request for monitor: 'RequestMonitor (com.crt.etmetb.redlink.RedlinkClient$3@135929e): Status ERROR: com.crt.etmetb code=0 Problem obtaining SWO buffer content. java.net.SocketException: Connection reset by peer: socket write error' resulted in an error.
!SUBENTRY 1 com.crt.etmetb 4 0 2016-03-11 13:18:48.351
!MESSAGE Problem obtaining SWO buffer content.
!STACK 0
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
at java.net.SocketOutputStream.write(SocketOutputStream.java:141)
at com.crt.etmetb.redlink.RedlinkClient$2.run(RedlinkClient.java:122)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

!ENTRY com.crt.dsfdebug 4 0 2016-03-11 13:19:15.580
!MESSAGE 15: Target error from Commit Flash write
!SUBENTRY 1 com.crt.dsfdebug 4 0 2016-03-11 13:19:15.580
!MESSAGE 15: Target error from Commit Flash write
!SUBENTRY 1 com.crt.dsfdebug 4 0 2016-03-11 13:19:15.580
!MESSAGE System rejected access at location 0x00000000 - verify Population of memory and peripherals

!ENTRY org.eclipse.cdt.dsf.gdb 4 5012 2016-03-11 13:19:16.922
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-target-download
Error message from debugger back end:
Error finishing flash operation
at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:111)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:235)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:109)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:97)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.Exception: Error finishing flash operation
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:927)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:756)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2016-03-11 13:19:16.922
!MESSAGE Failed to execute MI command:
-target-download
Error message from debugger back end:
Error finishing flash operation
!STACK 0
java.lang.Exception: Error finishing flash operation
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:927)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:756)

!ENTRY org.eclipse.core.resources 2 10035 2016-03-11 13:20:40.056
!MESSAGE The workspace will exit with unsaved changes in this session.
!SESSION 2016-03-11 13:21:37.108 -----------------------------------------------

[/collapse]

[lpcware]

Content originally posted in LPCWare by Bela on Fri Jul 03 09:55:46 MST 2015
I didn't follow the FAQ, because all the SW I downloadad was just the empty project.

Instead, I just unplugged my LPCXpresso board and then plugged it in again. This power cycling was enough to recover.
Now it is ready to debug. Hopefully for a long time.

I still don't know what was the error and how I solved it, but it seems to work. I think the emulator side of LPCXpresso board had some shock, because the LED was lit before and it is now dark.

Thank you for all your efforts, I go back to my own silly code!

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Jul 03 09:45:10 MST 2015
No. Did you follow the FAQ I provided? Please read and follow the instructions

[lpcware]

Content originally posted in LPCWare by Bela on Fri Jul 03 09:29:19 MST 2015
I tried it again, deleted the whole workspace and launched the complete process from groun up.
The result is the same, but I discovered something at the bottom of the screen.
I don't know what is "configuring GDB", but it takes too long time, I think. Actually it stays at 97% since over a minute.
Does it take us closer to the solution?

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Jul 03 09:29:02 MST 2015
"Not connected to emulator" means the debugger cannot 'see' your target. Probably because you have put it into an invalid state. See this FAQ for how to recover:
http://www.lpcware.com/content/faq/lpcxpresso/regaining-debug-access

[lpcware]

Content originally posted in LPCWare by Bela on Fri Jul 03 09:12:36 MST 2015
I did now, what you described. Run / Debug configurations and I deleted the two lines there under C/C++ (NXP Semiconductors). Then I closed this window.

When I clicked on the green bug to debug my empty project, the same Debug Configuration window appeared again.
I had no other choice as to set some configuration, because if I close this window without doing anything, than debugging doesn't start.
So I double clicked on 'C/C++ (NXP Semiconductors)' line.
I can already click on the 'DEBUG' button.
Now, project compiles, want to connect to the target. I click OK, and here comes the two problems: see the attached screenshots please.

You're officially absolutely right, Linux Mint is not a supported platform. I know that. But Mint is de facto a properly made Ubuntu and on this concrete machine with this concrete OS I already used LPCXpresso v7.6.2 until yesterday. I debugged my code, my only problem was that I couldn't clear a Timer0 MR0 IT request and the SW landed in a hard fail status. That made me headaches because I did everything the same as in another previous project and as it stays in the example projects. During debugging and modifying my code, this 'debug grey' error has happened and I cannot overcome.

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Jul 03 08:16:44 MST 2015
I am not convinced you have deleted all of the launch configurations.

To delete them all:
- Run->Debug Configurations...
- Remove everything under C/C++ (NXP Semiconductors)

After clearing this out, press Debug again. If this still doesn't work, then I don't know what else to suggest, except pointing out the Linux Mint is not one of our supported platforms...

[lpcware]

Content originally posted in LPCWare by Bela on Fri Jul 03 07:55:11 MST 2015
I attached the .metadata folder from my _original_ workspace. (_.metadata.zip)

I opened LPCXpresso again.
In the Project Explorer window, right clicked on Trial01 project. In the pop-up menu I selected Launch Configurations / Deleter current.
Than I clicked on the green bug icon on top of the screen. Interestingly, the debug configuration window didn't come. Instead, the project is built, no error message has come.

But: the debug icons are still grey ...

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Jul 03 07:39:19 MST 2015
I actually only need the ".metadata" directory from the workspaces.

It looks like you are trying to create you own Launch configurations? Whilst this may work (if you know exactly what you are doing), you should use the "Debug" button in the Quickstart panel - it correctly creates everything you need to start a debugger. I suspect this may be the root of your problems.

So:

1. Remove ALL existing launch configurations
2. Select your project
3. Press Debug button in the Quickstart panel.

[lpcware]

Content originally posted in LPCWare by Bela on Fri Jul 03 07:06:24 MST 2015
Sir,

I created a new workspace (called LPCXpressoTrialWorkspace).

I created a new, empty project in this workspace.

I tried to debug it.
Here a "debug configuration" window popped up. Maybe, I did something wrong there, but I couldn't start the debugging, the corresponding icons remained grey.
A screenshot and a .zip of this newly created workspace are attached.

I also created a .zip file of my previous workspace, but it is 682 Mbyte, I can't upload it here.
Is there another place for such a large file? There's nothing confidential in it, it is so large because I try to get know the LPC microcontroller since more than a year whenever I time and motivation have, and a lot of sample-projects are imported there. (Despite this, I'm still not a skilled programmer.)

[lpcware]

Content originally posted in LPCWare by Bela on Fri Jul 03 06:07:25 MST 2015
OK, I will do that.

I suppose, you're only interested in the newest version, am I right?

Just because I tried V7.3.0 in a few minutes and the debugging doesn't enabled there as well. :-(

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Jul 03 05:45:32 MST 2015
Please try this
- create a new workspace (choose a new empty directory when you start LPCXpresso)
- create a new project with the wizard
- debug it

If this works, please zip up the two workspaces (working and not working) and post them to this thread.

[lpcware]

Content originally posted in LPCWare by Bela on Fri Jul 03 05:23:55 MST 2015
Thanks, 8473, it seems I'm not so lucky.

Today I installed V7.8.0 into a different folder.
Since my old project didn't work, (debug buttons greyed out), I closed it. Than I created a new, empty project by the wizzard.
This empty project compiles without error, I am able to start a debug session in the Quickstart Panel. It seems everything goes the proper way, except that all the debug buttons are greyed out.
See the attached pictures.
So, I think, I have to downgrade to an earlier version, where these problem didin't exist.

In case I can do something to help catching this problem, I will do whatever I can. Please consider, I'm not a professional SW guy.

[lpcware]

Content originally posted in LPCWare by 8473 on Thu Jul 02 16:29:25 MST 2015
Hello Bela,

I personally experienced this just 1 time within half a year IIRC -- but noticed it here because of a fellow suffering this in strange .. rhythm.
Currently, with 7.8.x, problem vanished on his side, too.

"Our" solution was to close all eclipse "perspectives" and restarting eclipse itself..

[lpcware]

Content originally posted in LPCWare by Bela on Thu Jul 02 14:48:39 MST 2015
Hi, I experienced this problem too.
My system is Linux Mint 17, 64 bit (with the necessary 32 bit libraries), LPCXpresso 7.6.2

I removed the org.eclipse.debug.ui folder, but it didn't solve the problem. The file I attached, is the original folder before it got moved away.

Is it already corrected in V7.8.0?
Or would it be better do downgrade to some 6.xxx version, where this problem didn't exist? I hope it would work for my LPC1769 / LPCXpresso board / LPC Base board project.

[lpcware]

Content originally posted in LPCWare by emh203 on Wed Jun 03 06:54:34 MST 2015
I have been using 7.7.2 and just ran into this problem last night.   Reseting all perspectives and rebooting seemed to fix it. 

[lpcware]

Content originally posted in LPCWare by brownm on Wed May 27 03:51:09 MST 2015
Further to this. I think that I was doing the following, when it broke.

If I open 2 instances of LPCxpresso,

The first with LPCOpen as the workspace,
The second with my project as the workspace,

Then connect to the same debugger consecutively to test my code vs the LPCOpen code. it appears to reliably bust.....

ie. Debug the RTC in LPC Open examples, then terminate the debug on this. then switch to the other LPCXpresso instance and debug the RTC on the same hardware with the same debugger.

I was a bit scared to retry the procedure since I couldn't get it working again. but now that I know we can just delete a directory to get it going again, I'll check it further in the morning.

Regards
Marshall

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Wed May 27 02:56:00 MST 2015
We continue to try to track the cause of this problem down - but it remains frustratingly elusive.

Anyway thanks for posting your files. We'll see if these provide any further clues.

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by brownm on Tue May 26 18:17:55 MST 2015
this happened to me, as well

Moving the .metadata\.plugins\org.eclipse.debug.ui directory worked

As requested I have attached this directory to this post.

Regards
Marshall