Debugger disconnect behaviour

[lpcware]

Content originally posted in LPCWare by lpcentric on Tue Aug 14 21:41:00 MST 2012
Recently when stopping the debugger from within the LPCXpresso eclipse the target is always stopped. In the  launch configuration the disconnect behaviour is set to "cont" in both places. LPC-Link board from an LPC1768 board purchased about a year ago, but with my own LPC1768 instead of the original LPCXpresso board.

How can I get the original behaviour (to leave the target running) back? It used to work, and Code Red's FAQ says to change the launch configuration debugger setting that's already set to "cont".

Thanks.

[lpcware]

Content originally posted in LPCWare by lpcentric on Tue Aug 21 15:41:23 MST 2012
Thanks very much for your help, and confirming that it was supposed to work the way I had it set up. The debug log showed that there were flash programming problems sometimes. There are also huge delays while LPC-link is trying to sort out its jtag targets.
All this gave me a different idea - I had installed the latest lpcxpresso eclipse to a different location, and both new and old worked happily, but maybe not for the debugger part. So I uninstalled both, re-installed the latest one, and all is working again as before.

My guess is that the newer eclipse IDE didn't use its own debugger programs but the older ones from a different location, and the version mismatch doesn't work properly.

Thansk again.

[lpcware]

Content originally posted in LPCWare by CodeRedSupport on Mon Aug 20 03:57:33 MST 2012
Never seen any problems with this in the past. Can you post your debug log, saved at the point just before you terminate your debug connection.

http://support.code-red-tech.com/CodeRedWiki/DebugLog

I'm also wondering if this might be something in your code which is not being handled once there is no debug connection available (for example a semihosted printf). Can you try creating a new "C Project" using the project wizard, and just putting some code into this to toggle a led or similar. Then try debugging and terminating the connection and seeing if you see the same effect.

Regards,
CodeRedSupport

[lpcware]

Content originally posted in LPCWare by lpcentric on Sun Aug 19 15:33:36 MST 2012
It no longer works with the LPCXpresso boards either. Stopping the debugger in eclipse halts the target, recovery is only possible by powering down the target, reset is not enough.
In the debugger settings cont and nochange both have the same effect of halting the target. Settings are as the Code Red FAQ describes, but it's not working.

This used to work. How can I get the documented and previous behaviour back again?

Thanks for any tips.