LPCxpresso 8.1.4 can no longer debug LPC824

lpcware · ‎06-15-2016

Content originally posted in LPCWare by bob_walker on Sun Mar 27 11:51:16 MST 2016
I was able to use LPCxpresso just fine - with the upgrade to 8.1.4 there is no connection.
Here are the various console outputs:

Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=44211 -g -mi -2 -pLPC824 -vendor=NXP -vc -reset= -ProbeHandle=1 -CoreIndex=0 -flash-driver=LPC800_32.cfx
Error message from debugger back end:
Remote communication error. Target disconnected.: Connection reset by peer.

Redlink Server ****************************
[Started server]
[Connected on port 3025]
[0.000646781s] redlink>
[0.000757709s] redlink>
[0.000844617s] redlink>
[0.000929468s] redlink>
[0.001012473s] redlink>
[0.001087761s] redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
Serial Number = A000000002
VID:PID = 1FC9:0090
Path = /dev/hidraw0
[0.053804368s] redlink>
[0.053914436s] redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
Serial Number = A000000002
VID:PID = 1FC9:0090
Path = /dev/hidraw0
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
[0.094066824s] redlink>
[0.094157544s] redlink>
[0.111028104s] redlink>
[0.111216224s] redlink>
[0.111288240s] redlink>ProbeIsOpen 1
FALSE
[0.150653712s] redlink>ProbeOpenByIndex 1
Probe Handle 1 Open
[0.241789712s] redlink>WireIspReset 1
Hardware interface transfer error
[2.283796992s] redlink>WireIsConnected 1
FALSE
[2.323734528s] redlink>WireSwdConnect 1
Hardware interface transfer error
[4.365786624s] redlink>CoresConfigured 1
FALSE
[4.405742592s] redlink>CoreConfig 1
Wire not connected
[4.445809664s] redlink>
[4.445940224s] redlink>
[6.460968448s] redlink>
[6.461158912s] redlink>
[6.461267456s] redlink>
[6.461394944s] redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
Serial Number = A000000002
VID:PID = 1FC9:0090
Path = /dev/hidraw0
IsOpen = TRUE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
[6.500746752s] redlink>quit
[Closed]

Driver ***********************
LPCXpresso RedlinkMulti Driver v8.1 (Mar 11 2016 13:35:29 - crt_emu_cm_redlink build 672)
Failed on connect: Ee(36). Could not connect to core.
No connection to emulator device

GDB *************************

GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20151217-cvs-LPCXpresso001
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-linux-gnu --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

GDB Traces *****************************

...and here is where it fails

592,035 (gdb)
592,037 13-interpreter-exec console "set remotetimeout 60000"
592,037 =cmd-param-changed,param="remotetimeout",value="60000"
592,037 13^done
592,037 (gdb)
596,374 14-target-select extended-remote | crt_emu_cm_redlink -msg-port=37434 -g -mi -2 -pLPC824 -ve\
ndor=NXP -vc -reset= -ProbeHandle=1 -CoreIndex=0 -flash-driver=LPC800_32.cfx
598,380 14^error,msg="Remote communication error. Target disconnected.: Connection reset by peer."
598,380 (gdb)
598,383 15-target-disconnect
598,383 16-gdb-exit
598,383 15^error,msg="You can't do that when your target is `exec'"
598,383 (gdb)
598,383 16^exit

For linux 64-bit:
I have all the prerequisite groups, udev rules, permissions, etc all set up. I have had no issues until this update to 8.1.4.

Does anyone have any ideas? I'm stuck.

lpcware · ‎06-18-2016

bump

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Mon Mar 28 11:41:56 MST 2016

Quote: bob_walker
I downloaded lpcscrypt and ran the bootload and CMSIS scripts for both my LPC LINK2's. The debugger works now.

Unless there's another reason I'm not aware of, it's a better idea to allow the probe to DFU boot. As probe firmware updates become available in follow-on LPCXpresso releases, the updated probe can be used immediately. Otherwise, you have to remember to keep your LPCScrypt installation current, then reflash.

Thanks and regards,
LPCXpresso Support

lpcware · ‎06-15-2016

Content originally posted in LPCWare by bob_walker on Sun Mar 27 23:20:48 MST 2016
I downloaded lpcscrypt and ran the bootload and CMSIS scripts for both my LPC LINK2's. The debugger works now.

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Sun Mar 27 22:40:45 MST 2016
Booting LPC-Link2

The latest probe firmware for DFU Boot is provided with LPCXpress_8.2.4_606.

Thanks and regards,
LPCXpresso Support

lpcware · ‎06-15-2016

Content originally posted in LPCWare by bob_walker on Sun Mar 27 21:11:28 MST 2016
Where might I find the latest fimware for LPC-Link2? How do I "allow" the LPC-LINK2 to DFU boot?

lpcware · ‎06-15-2016

Content originally posted in LPCWare by lpcxpresso-support on Sun Mar 27 20:56:55 MST 2016

Presuming no damage has occurred to your debug circuit, I'd recommend you first update the probe firmware to the latest release or allow the LPC-Link2 to DFU boot. If the LPC-Link2 is set up to DFU boot, the latest firmware would have downloaded. Second, remove the ISPResetConnect.scp script from the command line. Then, restart your debug session and let us know how you get on.

Thanks and regards,
LPCXpresso Support