MCUXpresso: Failed to execute MI command: -target-download. Load failed

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCUXpresso: Failed to execute MI command: -target-download. Load failed

3,150 Views
darcy_cavanagh
Contributor I

Hi, I'm trying to debug as LinkServer to a PNEV5180B with an LPC-Link2 but am getting this issue every time i try debugging. I have tried resetting the Link2 and deleting the launch file. Have also set the optimisation to -Os. Any help would be appreciated thanks.

( 5) Remote configuration complete
Reconnected to existing LinkServer process.
Using memory from core 0 after searching for a good core
debug interface type = Cortex-M3/4 (DAP DP ID 2BA01477) over SWD TAP 0
processor type = Cortex-M3 (CPU ID 00000C23) on DAP AP 0
number of h/w breakpoints = 6
number of flash patches = 2
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 2BA01477. CpuID: 00000C23. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 0000000000 ROM (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04002BB000 Gen SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04002BB002 Gen DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)
ROM 1 E0000000: CID B105E00D PID 04002BB001 Gen ITM (type 0x0)
ROM 1 E0040000: CID B105900D PID 04002BB923 CSt TPIU-Lite type 0x11 Trace Sink - TPIU
ROM 1 E0041000: CID B105900D PID 04002BB924 CSt ETM-M3 type 0x13 Trace Source - Core
NXP: LPC1769
DAP stride is 4096 bytes (1024 words)
Inspected v.2 On-chip Flash Memory LPC11_12_13_32K_8K.cfx
Image 'LPC11_12_13 (32K Flash, min 8K RAM) May 22 2019 12:27:45'
Connected: was_reset=false. was_stopped=true
Awaiting telnet connection to port 3335 ...
GDB nonstop mode enabled
GDB stub (crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.

Project settings are as follows

Capture.PNG

0 Kudos
2 Replies

1,259 Views
MCUXpresso
Contributor I

Hey,

failed to exicute MI commond target

 

 

 

0 Kudos

2,782 Views
FelipeGarcia
NXP Employee
NXP Employee

Hello Darcy,

 

I recommend you to re-program the firmware to the board. You can do this by following the next document:

https://community.nxp.com/docs/DOC-334997 

I hope this helps.

 

Have a great day,
Felipe

-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "Mark Correct" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

0 Kudos