LPCXpresso IDE中的主题 Unable to debug using LPC-Link2

Unable to debug using LPC-Link2

lpcware — Thu, 16 Jun 2016 00:20:12 GMT

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.

Re: Unable to debug using LPC-Link2

lpcware — Thu, 16 Jun 2016 00:20:13 GMT

Content originally posted in LPCWare by vtw.433e on Sun May 29 22:34:18 MST 2016
Try deleting your launch configuration and then debug again.

Re: Unable to debug using LPC-Link2

lpcware — Thu, 16 Jun 2016 00:20:13 GMT

Content originally posted in LPCWare by lshl on Sun May 29 22:54:40 MST 2016
Unfortunantly it didn't help.

But some more capture:

Quote:
LPCXpresso RedlinkMulti Driver v8.1 (Mar 11 2016 13:34:34 - crt_emu_cm_redlink build 672)
Found chip XML file in C:/Dev/LPC1549_2CAN/Debug/LPC1549.xml
( 5) Remote configuration complete
============= SCRIPT: LPC15RunBootRomConnect.scp =============
No probes found
DpID = 00000000
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Halt on reset vector catch
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
Halt on watchpoint write of ROMWSCTRL register
Wire Ack Fault - target connected?
Wire Ack Fault - target connected?
============= END SCRIPT =====================================
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.112 (NXP Semiconductors)
Serial Number: A000000002
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#9&2283716e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
connection failed - Ee(36). Could not connect to core. - retrying
Failed on connect: Ee(36). Could not connect to core.
Connected&Reset. Was: NotConnected. DpID: 00000000. CpuID: 00000000. Info: <None>
Error 0: OK
Last sticky error: 0x0 AIndex: 0
No debug bus (MemAp) selected
DAP Speed test unexecuted or failed
Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.
(100) Target Connection Failed

Re: Unable to debug using LPC-Link2

lpcware — Thu, 16 Jun 2016 00:20:14 GMT

Content originally posted in LPCWare by vtw.433e on Mon May 30 01:10:19 MST 2016
That looks like your jtag cable is misconnected

Re: Unable to debug using LPC-Link2

lpcware — Sun, 19 Jun 2016 01:12:05 GMT

bump