Issue with "LPC-Link 2"     Error in final launch sequence  + Error 02 + Error 31

cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with "LPC-Link 2"     Error in final launch sequence  + Error 02 + Error 31

483 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by Powerfreak on Fri Dec 25 03:34:55 MST 2015
Hi,
I have a severs issue with LPC-Link 2

Usually I was programming with "Red Probe +" for years now, and it _still_ runs perfect.
As LPCXpresso will stop the support for "RedProbe+" in the near future, I want to change to LPC-Link2

Some facts:
-Windows 7
-LPCXpresso Version 8.0.0_526
- one PCB is a LPC1313, the other a LPC1111/33-201
-Firewall and realtime scan was both off to ensure that this has no influenc
-"LPC-Link 2" was successfully found by "LPCXpresso" is initializing with CMSIS-DAP with
  LPC432x_CMSIS_DAP_V5_134.bin.hdr" but stoped with "Timeout waiting for SMSIS-DAP to initialize (0)"
-I tried with USB-Hub or without, no difference
-I already updated the "LPC-Link II UCOM Port" Driver to 2.0.0.0 21.Nov 2014
-I have 2 targets and both are own developed and are still running with "Red Probe +"
-I am programming with SWD, only
-I built an own cable connected to J6 (SWDIO, SWCLK, SWD{not used now}, Reset, GND)
  connection/Pinout is the same as I did my self für "Red Probe+" and triple verified.
-Pinout between J6 and J7 was measured and confirmed
-Pinout from J6 to target was measured and confirmed
-I checkt the connection to LPC-Link 2 with LPCScrypt, and I am able to programm the LPC-
  and the Segger- config without any failure. (LEDs are blinking at different speed)
-with LPC-Link 2 Configuration Tool v2.02 I can programm different configurations, too
  and get a visual "Image verified by read back successfully"
-power supply is checked and far from any limits
-I already set the targets to ISP mode several times, but "LPC-Link 2" cannot reach the target and it stays in ISP mode till power on.
-"Vector catch" is on.
-I did everything above with and without connected target, failure message is unchanged
-Some lines below you will find the console output from the Redlink Server and the GDB-Trace

-Debug Message was:
"LPCXpresso RedlinkMulti Driver v8.0 (Nov 17 2015 10:18:17 - crt_emu_cm_redlink build 556)
Failed on connect: Ee(36). Could not connect to core.
No connection to emulator device"

==> Again: my system is still running if I change the programmer to "Red Probe +" !!

Please advice.

Thanks ;-)







##############################
Redlink Server:

[Started server]
[Connected on port 3025]
redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
VID = 1FC9, PID = 0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
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
redlink>ProbeIsOpen 1
FALSE
redlink>ProbeOpenByIndex 1
Probe Handle 1 Open
redlink>WireIspReset 1
redlink>WireIsConnected 1
FALSE
redlink>WireSwdConnect 1
DpID = 00000000
redlink>CoresConfigured 1
FALSE
redlink>CoreConfig 1
Number of CORES/TAPs = 1, Fully recognized: True
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
VID = 1FC9, PID = 0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = SWD
CoresConfigured = TRUE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink>exit
[Closed]
[Started server]
[Connected on port 3025]
redlink>ProbeList
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
VID:PID = 1FC9:0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
VID = 1FC9, PID = 0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
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
redlink>ProbeIsOpen 1
FALSE
redlink>ProbeOpenByIndex 1
Probe Handle 1 Open
redlink>WireIspReset 1
redlink>WireIsConnected 1
FALSE
redlink>WireSwdConnect 1
DpID = 00000000
redlink>CoresConfigured 1
FALSE
redlink>CoreConfig 1
Number of CORES/TAPs = 1, Fully recognized: True
redlink>ProbeStatus
Index = 1
Manufacturer = NXP Semiconductors
Description = LPC-LINK2 CMSIS-DAP V5.134
VID = 1FC9, PID = 0090
Path = \\?\hid#vid_1fc9&pid_0090&mi_00#7&de4dbc8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
IsOpen = TRUE
WireInitialized = TRUE
WireProtocol = SWD
CoresConfigured = TRUE
PacketSize = 1024
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = CMSIS-DAP
Probe Reference Count = 0
redlink>exit
[Closed]

#############################
GDB-Trace:

748,400 2-gdb-version
748,416 ~"GNU gdb (GNU Tools for ARM Embedded Processors) 7.8.0.20150604-cvs\n"
748,416 ~"Copyright (C) 2014 Free Software Foundation, Inc.\n"
748,416 ~"License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>\nThis is fre\
e software: you are free to change and redistribute it.\nThere is NO WARRANTY, to the extent permitt\
ed by law.  Type \"show copying\"\nand \"show warranty\" for details.\n"
748,416 ~"This GDB was configured as \"--host=i686-w64-mingw32 --target=arm-none-eabi\".\nType \"sho\
w configuration\" for configuration details."
748,416 ~"\nFor bug reporting instructions, please see:\n"
748,416 ~"<http://www.gnu.org/software/gdb/bugs/>.\n"
748,416 ~"Find the GDB manual and other documentation resources online at:\n<http://www.gnu.org/soft\
ware/gdb/documentation/>.\n"
748,416 ~"For help, type \"help\".\n"
748,416 ~"Type \"apropos word\" to search for commands related to \"word\".\n"
748,416 2^done
748,416 (gdb)
748,416 3-environment-cd D:/E/Projekte/LPCxpresso_Workbench/__LPC13
748,432 3^done
748,432 (gdb)
748,432 4-gdb-set breakpoint pending on
748,447 4^done
748,447 (gdb)
748,447 5-enable-pretty-printing
748,464 5^done
748,464 (gdb)
748,464 6-gdb-set python print-stack none
748,479 6^done
748,479 (gdb)
748,479 7-gdb-set print object on
748,495 7^done
748,495 (gdb)
748,495 8-gdb-set print sevenbit-strings on
748,511 8^done
748,511 (gdb)
748,511 9-gdb-set charset ISO-8859-1
748,526 9^done
748,526 (gdb)
748,526 10-gdb-set auto-solib-add on
748,542 10^done
748,542 (gdb)
748,542 11-file-exec-and-symbols --thread-group i1 D:/E/Projekte/LPCxpresso_Workbench/__LPC13/Debug/\
__LPC13.axf
748,557 11^done
748,557 (gdb)
748,557 12-interpreter-exec console "set remotetimeout 60000"
748,573 =cmd-param-changed,param="remotetimeout",value="60000"
748,573 12^done
748,573 (gdb)
748,651 13-target-select extended-remote | crt_emu_cm_redlink -msg-port=51434 -g -mi -2 -pLPC1313 -v\
endor=NXP -vc -reset= -ProbeHandle=1 -CoreIndex=0 -flash-driver=LPC11_12_13_32K_8K.cfx
748,791 13^error,msg="Remote communication error.  Target disconnected.: No error."
748,791 (gdb)
748,791 14-target-disconnect
748,791 15-gdb-exit
748,807 14^error,msg="You can't do that when your target is `exec'"
748,807 (gdb)
748,807 15^exit


############################
0 Kudos
15 Replies

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by JojoS on Tue Jan 05 09:03:06 MST 2016
For my breakout board I have used now also the J6 because this board has no SWD/JTAG header and for dupont wires J6 is more convenient. I don't want to supply my board thru the probe, so I opened SJ1 1-2 by removing the 0R resistor and closing JP2. So I have VTarget on Pin1 of J6.
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by Powerfreak on Tue Jan 05 05:40:21 MST 2016

Quote: lpcxpresso-support
So the first thing to double check is VTref vs JP2 on your LPC-Link2. From the debug considerations FAQ:

https://www.lpcware.com/content/faq/lpcxpresso/debug-design

Quote:
With JP2 open the target must supply the VTref to power the target side of the dual-supply buffer.



Otherwise check your JP6 connection to the target for shorts / bad connections both on the LPC-Link2 as well as at the other end of your "home made cable" where it attaches to your target. We have certainly seen the occasional customer having issues using JP6 to make their debug connection because of such issues. Generally it is much more reliable to use JP7 and the cable supplied with the LPC-Link2!

Regards,
LPCXpresso Support




Hi,

your tip was helpful, many thanks.

I checked the connections and VTref again and again and found a PCB-Problem of the LPCXpresso-Link-2.
The GND-Pin at J6 has a disconnect somewhere bevor J6-GND.
I soldered the pin fix to GND, and everything was running excellent.

Thanks and have a nice day
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by JojoS on Mon Jan 04 13:57:53 MST 2016
great, that solved my problem!
Thanks for your help.
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by vtw.433e on Mon Jan 04 13:14:21 MST 2016
Jojos, yours is a different problem, covered by this FAQ
https://www.lpcware.com/content/faq/lpcxpresso/lpc-link2-failing-enumerate-cmsis-dap-firmware
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by JojoS on Mon Jan 04 11:33:13 MST 2016
I can confirm this problem. Target is an ezSBC2 board with LPC1347 or another simple breakout board with the same cpu. LPCxrpesso v8.0.0 on Win7 64Bit, LPCLink2 with original cables from EA, connected to J7.
When I start debug, the LPCLink is detected and the firmware CMSIS-DAP 5.134 is downloaded. After about 30s I get also the timeout and Init failed message.
When I use the latest LPCLink configuration tool and load the CMSIS-DAP then the probe cannot be detected by LPCXpresso.
When I use an older version of LPCLink config (04/2013) an load the CMSIS-DAP then debugging works fine.

Edit:
Tested with another target, LPC4088 QuickStartBoard from EA, connected via 20pin cable to J8. The same result, old fixed CMSIS config works, the LPCXpresso downloaded firmware 5.134 works not.

This are messages that are shown:
!ENTRY com.crt.debugcommon 4 0 2016-01-04 18:57:01.576
!MESSAGE dfu-util 0.7Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.Copyright 2010-2012 Tormod Volden and Stefan SchmidtThis program is Free Software and has ABSOLUTELY NO WARRANTYPlease report bugs to dfu-util@lists.gnumonks.orgFilter on vendor = 0x1fc9 product = 0x000cOpening DFU capable USB device... ID 1fc9:000cRun-time device DFU version 0100Claiming USB DFU Runtime Interface...Determining device status: state = dfuIDLE, status = 0Found Runtime: [1fc9:000c] devnum=0, cfg=1, intf=0, alt=0, name="DFU"Claiming USB DFU Interface...Setting Alternate Setting #0 ...Determining device status: state = dfuIDLE, status = 0dfuIDLE, continuingDFU mode device DFU version 0100bytes_per_hash=491Copying data from PC to DFU deviceStarting download: [##################################################] finished!Resetting USB to switch back to runtime mode

!ENTRY com.crt.log 1 0 2016-01-04 18:59:25.756
!MESSAGE Drivers loaded in 182561 milliseconds

!ENTRY com.crt.debugcommon 4 -1 2016-01-04 18:59:25.786
!MESSAGE Error received while booting CMSIS-DAP:
Timeout waiting for CMSIS-DAP to initialize (0).

0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Mon Jan 04 07:23:43 MST 2016
So the first thing to double check is VTref vs JP2 on your LPC-Link2. From the debug considerations FAQ:

https://www.lpcware.com/content/faq/lpcxpresso/debug-design

Quote:
With JP2 open the target must supply the VTref to power the target side of the dual-supply buffer.



Otherwise check your JP6 connection to the target for shorts / bad connections both on the LPC-Link2 as well as at the other end of your "home made cable" where it attaches to your target. We have certainly seen the occasional customer having issues using JP6 to make their debug connection because of such issues. Generally it is much more reliable to use JP7 and the cable supplied with the LPC-Link2!

Regards,
LPCXpresso Support
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by vtw.433e on Sun Jan 03 14:28:56 MST 2016
Given that my system works when using J7 and yours does not, using J6, why not try what is known to work? Go on, humour me...
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by Powerfreak on Sun Jan 03 13:31:25 MST 2016

Quote: whitecoe
As you have already been told by vtw.433e, to debug you need to connect from J7 to your own target board. J6 is for debugging the LPC4370 on the LPC-Link2 board itself. This is in the docs...

https://www.lpcware.com/lpclink2

You might also want to check your own boards debug/reset circuitry against to the FAQ too. There are some subtle requirements for LPC-Link2 which might be slightly different from Red Probe+..

https://www.lpcware.com/content/faq/lpcxpresso/debug-design

HTH!



Dear whitecoe,
Please do take a closer look at the picture attached.
You will find THE essential part of the connector-description including J6, J7 and J8.
The required pinout is absolutely clear, and pins with the same name have the identical signal... so where should be the problem you want to point out?
Please be so kind and and describe in detail.

In addition: If I look at the picture @ ".../debug-design" below the headline "Using LPC-Link2 as a debug probe"... look at the orange connectors... the debugging target can be conneted there.. can you see it?   J2 is for debugging the LPC4370 on the LPC-Link2 board itself.


For debugging the target in SWD you do need GND, SWDIO, SWCLK, and maybe /Reset. Thats all.
Of course the ISP-Pin is available and only be used for entering the boot-loader on reset. I tried, without any change.

Ok, I do not use VTref, but the target side is properly supplied.

ok?








0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by whitecoe on Sun Jan 03 05:53:45 MST 2016
As you have already been told by vtw.433e, to debug you need to connect from J7 to your own target board. J6 is for debugging the LPC4370 on the LPC-Link2 board itself. This is in the docs...

https://www.lpcware.com/lpclink2

You might also want to check your own boards debug/reset circuitry against to the FAQ too. There are some subtle requirements for LPC-Link2 which might be slightly different from Red Probe+..

https://www.lpcware.com/content/faq/lpcxpresso/debug-design

HTH!
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by Powerfreak on Sun Jan 03 01:26:57 MST 2016
Happy new year to everybody ...



The required pins are availabel on J6 and J7.

Someon available from  lpcxpresso-support?? May be cristmas vacation ;-)
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by vtw.433e on Wed Dec 30 12:46:06 MST 2015
Try j7. That is what I use.
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by Powerfreak on Wed Dec 30 12:22:07 MST 2015
Thanks for your hint.
-As mentioned above, my cable is plugged in J6, named "LPCXpreso Target".
-Pinout/adaptation ist completely identical to my RedProbe+
-Power is more than sufficient.

double checked!

0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by vtw.433e on Wed Dec 30 12:06:02 MST 2015
And make sure you plug the JTAG cable into J7 on your LPC-Link2 and not J2!
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by vtw.433e on Wed Dec 30 11:52:55 MST 2015
Check you have you tag cable connected the right way.
Also check your power.
0 Kudos

88 Views
NXP Employee
NXP Employee
Content originally posted in LPCWare by Powerfreak on Wed Dec 30 09:03:06 MST 2015
Has no one an idea?
Is any information missing?
0 Kudos