AnsweredAssumed Answered

Brand new board / install FRDM-K28FA can't debug

Question asked by Mike Mitchell on Oct 14, 2019
Latest reply on Oct 14, 2019 by Mike Mitchell

New install, just trying to run hello_world demo. The debugger drivers look OK, but when it tries to program the board I get an error:

 

Error in final launch sequence:

Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=8108 -g -mi -2 -pMK28FN2M0Axxx15 -vendor=NXP --connectscript=kinetisconnect.scp --reset= -ProbeHandle=1 -CoreIndex=0 -cache=disable --flash-driver= -x C:/Users/Mike/Documents/MCUXpressoIDE_11.0.1_2563/workspace/.mcuxpressoide_packages_support/MK28FN2M0Axxx15_support --flash-dir C:/nxp/MCUXpressoIDE_11.0.1_2563/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.0.1.201908271452/binaries/Flash --flash-dir C:/Users/Mike/Documents/MCUXpressoIDE_11.0.1_2563/workspace/.mcuxpressoide_packages_support/MK28FN2M0Axxx15_support/Flash --telnet 3331
Error message from debugger back end:
Remote communication error. Target disconnected.: Success.
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=8108 -g -mi -2 -pMK28FN2M0Axxx15 -vendor=NXP --connectscript=kinetisconnect.scp --reset= -ProbeHandle=1 -CoreIndex=0 -cache=disable --flash-driver= -x C:/Users/Mike/Documents/MCUXpressoIDE_11.0.1_2563/workspace/.mcuxpressoide_packages_support/MK28FN2M0Axxx15_support --flash-dir C:/nxp/MCUXpressoIDE_11.0.1_2563/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.0.1.201908271452/binaries/Flash --flash-dir C:/Users/Mike/Documents/MCUXpressoIDE_11.0.1_2563/workspace/.mcuxpressoide_packages_support/MK28FN2M0Axxx15_support/Flash --telnet 3331
Error message from debugger back end:
Remote communication error. Target disconnected.: Success.

Console Output:

 

============= SCRIPT: kinetisconnect.scp =============
Kinetis Connect Script
Connecting to Probe Index = 1
This probe = 1
This TAP = 0
This core = 0
DpID = 2BA01477
Assert NRESET
Reset pin state: 00
Power up Debug
MDM-AP APID: 0x001C0000
MDM-AP System Reset/Hold Reset/Debug Request
MDM-AP Control: 0x0000001C
MDM-AP Status (Flash Ready) : 0x00000032
Part is not secured
MDM-AP Control: 0x00000014
Release NRESET
Reset pin state: 01
MDM-AP Control (Debug Request): 0x00000004
MDM-AP Status: 0x0001003A
MDM-AP Core Halted
============= END SCRIPT =============================
Probe Firmware: DAPLink CMSIS-DAP (ARM)
Serial Number: 0224000032044e4500347009997b003c6781000097969900
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#9&87f38fe&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
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-M4 (CPU ID 00000C24) 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: 00000C24. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04003BB002 Gen DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)
ROM 1 E0000000: CID B105E00D PID 04003BB001 Gen ITM (type 0x0)
ROM 1 E0040000: CID B105900D PID 04000BB9A1 CSt TPIU type 0x11 Trace Sink - TPIU
ROM 1 E0041000: CID B105900D PID 04000BB925 CSt ETM type 0x13 Trace Source - Core
NXP: MK28FN2M0Axxx15
DAP stride is 4096 bytes (1024 words)
can't find a flash driver called ''

Jumpers are all set to defaults per: https://www.nxp.com/docs/en/user-guide/FRDMK28FUG.pdf  Table 8. 

Outcomes