Debug tools are disabled

[lpcware]

Content originally posted in LPCWare by jurrien on Fri Jan 09 02:50:03 MST 2015
Hello,

Yesterday I downloaded the newest version of LPCXpresso (LPCXpresso v7.5.0 [Build 254] [2014-10-31] ) and was capable of running and debugging examples just fine. Today (I guess after a pc reboot) for some reason the debug tools are not working correctly anymore. If I press the 'Launch Debug' button it does upload my code and it pauses on the first line of the main function which all sound great. The problem though, is that all buttons on the debug toolbar (continue, step over, step into ect.) are all disabled. Also if I open the 'Run' menu, all the debug options are disabled there is as well. However I haven't lost complete control over the board; the 'run to line' option is still enabled (not found on the debug toolbar but right click my code->run to cursor) and works fine.

After some googleling I found this note (http://www.lpcware.com/content/faq/lpcxpresso/regaining-debug-access) that looked a little like that what I am facing (not sure if it is the same thing). Anyhow I cannot access the ISP since I am using custom hardware and turning on the "vector catch" did not change anything. What solved the problem (i guess only temporarily, but that's something I'll find out after the weekend) is creating a new workspace., but that is not a real sulotion.

Does anyone has an idea on what I might do wrong, and most of all what I should change in my setting to make sure everything does what it is supposed to do?
Many thanks,

Jurrien

[lpcware]

Content originally posted in LPCWare by Bela on Thu Jul 02 14:50:06 MST 2015
For me, the posted solution doesn't work.
I posted my problem in the other topic as well.

[lpcware]

Content originally posted in LPCWare by whitecoe on Thu Jul 02 13:59:56 MST 2015
This worked for me ....

http://www.lpcware.com/content/forum/lpcxpresso-ide-debugging-tools-stopped-working#comment-1145565

And I would certainly suggest trying out 7.8.0 - you do realise that you can keep 7.6.2 installed whilst you try the latest version out ?

HTH!

[lpcware]

Content originally posted in LPCWare by Bela on Thu Jul 02 13:46:23 MST 2015
Hello,

Is this problem already solved in the newest version V7.8.0?
I'm afraid, I also experieced the same in my Linux Mint 17, LPCXpresso V7.6.2 environment.
Does it worth to change to the newest version?

Hi, Bela

[lpcware]

Content originally posted in LPCWare by AndyMcC on Tue Mar 03 09:16:16 MST 2015
HI,

I also had this problem (with LPXpresso 7.6.2 on Win 7, 64-bit) and unsuccessfully tried various things: restarting, power-cycling, re-installing both LPCXpresso and the debug probe (LPC-Link 2) drivers.

What did work was to edit the debug configuration, fiddle with a few things, save it, then set it back to how I originally wanted and save it again.

HTH,

Andy McC

Edit: The above fix doesn't seem to work any more :(

[lpcware]

Content originally posted in LPCWare by jurrien on Tue Feb 17 07:47:16 MST 2015
Is there any update on this problem? I really would appreciate some support on this point.

[lpcware]

Content originally posted in LPCWare by jurrien on Fri Jan 09 08:00:17 MST 2015
Thanks for your response, the log file is in the attachment. I have tried to restart Eclipse (both while debugging in and while not debugging), this did not change anything. Importing an project into a new workspace does solve the problem.
Not sure if it matters but I am using ubuntu 14.04 on a 64bit machine (I think I forgot to mention this in my first post).
Thanks, and please let me if I have to try anything else.
Cheers, Jurrien

[lpcware]

Content originally posted in LPCWare by jurrien on Fri Jan 09 07:32:02 MST 2015
Thanks for your fast response Mike. Instead of looking at the address I looked into the project settings, here I found that code read protection is unchecked (I guess that that is the only way for enabling the code read protection or is there another?). Anyhow, the crp sound like you should not be capable of debugging at all, however it did upload the file and paused in the main function. Also, I could still make it run for a couple of lines (using the run to line), which did break at the right point. So I guess the debugger did understand what to do and when to break (again). I guess that CRP could not be the issue then, right? Or did I miss something? (I did look at address 0x2fc using two different tool who both told me a different value, so wasn't really sure if I should trust any of them).

Thanks, Jurrien

[lpcware]

Content originally posted in LPCWare by lpcxpresso-support on Fri Jan 09 07:29:45 MST 2015
I doubt this is anything to do with the code in your target flash. It sounds more like an known issue in the standard Eclipse Luna/CDT that sits under LPCXpresso - in that very occasionally the debug controls become unaccessible. This is currently under investigation.

We would certainly be interested in seeing your <workspace>/.metadata/.log to see if this gives any clues as to the cause of this problem. Please can you ZIP this file up and attach?

Then, please try restarting LPCXpresso - both whilst a debug session is acitve (ie you are connected to the target) and also when not debugging. Does restarting  in either case make the debug controls active again when you next start a debug session?

If not, try creating a new workspace and then import the projects across from your old workspace - does this fix things?

Regards,
LPCXpresso Support

[lpcware]

Content originally posted in LPCWare by MikeSimmonds on Fri Jan 09 04:56:59 MST 2015
Just a thought (for completeness); you did not enable any of the CRP (code read protection) modes did you?
If you have (or can generate) a binary image that corresponds to the code in your board, then you can check the
4-byte word at absolute offset 0x02FC with a hex viewer. Un protected should be 0xFFFFFFFF.
You can check the other significant values in the user manual.

Cheers, Mike