lpcware

Unable to debug using LPC-Link2

Discussion created by lpcware Employee on Jun 15, 2016
Latest reply on Jun 18, 2016 by lpcware
Content originally posted in LPCWare by lshl on Sun May 29 22:22:11 MST 2016
Hi,
So, a bit of background:
We have been using LPC1549/19 for quite some time now, we have a few products that are already stable and in production.
All of these boards I have been able to debug until recently, and my colleagues are still able to debug right now and I can't.

I have been using LPCXpresso 7.9.2.
And I started getting:

Quote:

  02: Failed on connect
  Could not connect to core.
  31: No connection to emulator device


And then:

Quote:
Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=54188 -g -mi -2 -pLPC1549 -vendor=NXP -vc -ConnectScript=LPC15RunBootRomConnect.scp -ResetScript=LPC15RunBootRomReset.scp -reset= -ProbeHandle=1 -CoreIndex=0 -flash-driver=LPC15xx_256K.cfx -x C:/Dev/LPC1549_2CAN/Debug
Error message from debugger back end:
Remote communication error.  Target disconnected.: No error.
Remote communication error.  Target disconnected.: No error.



I tried disconnecting everything (maybe ground loops), restarting LPCXpresso, and eventually also restarting the computer.
Same outcome.
So I upgraded to 8.1.4.
Same error:

Quote:
02: Failed on connect
  02: Failed on connect
  Could not connect to core.
  Emu(0): Connected&Reset. Was: NotConnected. DpID: 00000000. CpuID: 00000000. Info: <None>


And then:

Quote:
Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=54202 -g -mi -2 -pLPC1549 -vendor=NXP -vc -ConnectScript=LPC15RunBootRomConnect.scp -ResetScript=LPC15RunBootRomReset.scp -reset= -ProbeHandle=1 -CoreIndex=0 -flash-driver=LPC15xx_256K.cfx -x C:/Dev/LPC1549_2CAN/Debug
Error message from debugger back end:
Remote communication error.  Target disconnected.: No error.
Remote communication error.  Target disconnected.: No error.



Again, no kind of reset helped, and the board is "debugable" on any of my colleagues computers.

Thanks for any help.

Outcomes