LPCLink Error: Target markes as not debuggable.

lpcware — Wed, 15 Jun 2016 22:05:56 GMT

Content originally posted in LPCWare by bobw on Tue Sep 11 08:48:04 MST 2012
Can anyone from CodeRed support help us with this LPC-Link error?

OS is Windows 7 x64 so HID mode. Seems like this is a common problem. Could not resolve with any other threads...

Log from DOS session (i.e. after executing instructions in link below):
[FONT=Calibri]http://support.code-red-tech.com/CodeRedWiki/LPCLinkDiagnostics[/FONT]

 
C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin\Scripts>bootlpcxpresso hid
Booting LPC-Link with LPCXpressoHS.enc
Press any key to continue . . .
C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin\Scripts>set CRT_DEBUG_TRACE=1
C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin\Scripts>cd ..
C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin>crt_emu_cm3_nxp -info-emu -wire=hid
Ni: LPCXpresso Debug Driver v4.0 (May 21 2012 21:42:41)
1 Emulators available:
0. T1S6RGRIA    LPC-Link Probe v1.0 (Code Red - LPCXpresso)

C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin>crt_emu_cm3_nxp -info-target -plpc176
9 -wire=hid -4
Ni: LPCXpresso Debug Driver v4.0 (May 21 2012 21:42:41)
Nc: Looked for chip XML file in C:/nxp/LPCXpresso_4.2.3_292/lpcxpresso/bin/lpc17
69.xml
Nc: Looked for vendor directory XML file in C:/nxp/LPCXpresso_4.2.3_292/lpcxpres
so/bin/nxp_directory.xml
Nc: Found generic directory XML file in C:/nxp/LPCXpresso_4.2.3_292/lpcxpresso/b
in/crt_directory.xml
Nc: 2000 KHz
Nc: 1500 KHz
Nc: 1200 KHz
Nc: 1000 KHz
Nc:  750 KHz
Nc:  600 KHz
Nc:  500 KHz
Nc:  400 KHz
Nc:  300 KHz
Nc:  250 KHz
Nc:  200 KHz
Nc:  150 KHz
Nc:  100 KHz
Nc:   50 KHz
Nc:   50 KHz
Nc: 2000 KHz
Nc: 1500 KHz
Nc: 1200 KHz
Nc: 1000 KHz
Nc:  750 KHz
Nc:  600 KHz
Nc:  500 KHz
Nc:  400 KHz
Nc:  300 KHz
Nc:  250 KHz
Nc:  200 KHz
Nc:  150 KHz
Nc:  100 KHz
Nc:   50 KHz
Nc:   50 KHz
Nc: 2000 KHz
Nc: 1500 KHz
Nc: 1200 KHz
Nc: 1000 KHz
Nc:  750 KHz
Nc:  600 KHz
Nc:  500 KHz
Nc:  400 KHz
Nc:  300 KHz
Nc:  250 KHz
Nc:  200 KHz
Nc:  150 KHz
Nc:  100 KHz
Nc:   50 KHz
Nc:   50 KHz
Ed:02: Failed on connect: Ep(01). Target marked as not debuggable.
Et: Emu(0): Connected. Was: None. DpID:     EDB6. Info: T1S6RGRIA
Error 0: (null)
Last sticky: 0. AIndex: 0
No MemAp selected
No Speed test
SWD Frequency: 50 KHz. RTCK: False. Vector catch: False.
Packet delay: 0  Poll delay: 0.
Nc: 2000 KHz
Nc: 1500 KHz
Nc: 1200 KHz
Nc: 1000 KHz
Nc:  750 KHz
Nc:  600 KHz
Nc:  500 KHz
Nc:  400 KHz
Nc:  300 KHz
Nc:  250 KHz
Nc:  200 KHz
Nc:  150 KHz
Nc:  100 KHz
Nc:   50 KHz
Nc:   50 KHz
C:\nxp\LPCXpresso_4.2.3_292\lpcxpresso\bin>

Re: LPCLink Error: Target markes as not debuggable.

lpcware — Wed, 15 Jun 2016 22:05:57 GMT

Content originally posted in LPCWare by CodeRedSupport on Tue Sep 11 10:26:43 MST 2012
What is your target board? Is it custom or an LPCXpresso board?

"Target marked as not debuggable" normally means one of:
- the SWD cable is not correctly inserted, or is broken
- the target has been put into one of the CRP modes - you may only be able to recover this using FlashMagic over a UART
- the board is not provided with power
- the debug circuit is incorrectly designed

topic Re: LPCLink Error: Target markes as not debuggable. in LPCXpresso IDE

LPCLink Error: Target markes as not debuggable.

Re: LPCLink Error: Target markes as not debuggable.