AnsweredAssumed Answered

Failed to execute MI command

Question asked by Leif Zars on Mar 1, 2015
Latest reply on Mar 1, 2015 by Leif Zars

Post port from CodeWarrior to KDS 2.0.0.

I get this when tiring to start a debugging session.

 

Error in final launch sequence

Failed to execute MI command:

tbreak main

Error message from debugger back end:

Cannot access memory at address 0x17bca

Cannot access memory at address 0x17bca

 

The only way I have found around this is to power on the K20 right before the code download begins.

Any thoughts on how to fix this?

 

 

SEGGER J-Link GDB Server V4.92 Command Line Version

JLinkARM.dll V4.92 (DLL compiled Sep 30 2014 09:33:42)

 

-----GDB Server start settings-----

GDBInit file:                  none

GDB Server Listening port:     2331

SWO raw output listening port: 2332

Terminal I/O port:             2333

Accept remote connection:      localhost only

Generate logfile:              off

Verify download:               on

Init regs on start:            on

Silent mode:                   off

Single run mode:               on

Target connection timeout:     5 sec.

------J-Link related settings------

J-Link Host interface:         USB

J-Link script:                 none

J-Link settings file:          none

------Target related settings------

Target device:                 MK20DN512xxx10

Target interface:              JTAG

Target interface speed:        1000kHz

Target endian:                 little

 

 

Connecting to J-Link...

J-Link is connected.

Firmware: J-Link V9 compiled Sep 29 2014 18:56:38

Hardware: V9.00

S/N: 269301025

OEM: SEGGER-EDU

Feature(s): FlashBP, GDB

Checking target voltage...

Target voltage: 3.38 V

Listening on TCP/IP port 2331

Connecting to target...ERROR: Could not connect to target.

Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...

Shutting down...

Outcomes