Hi,
I tried to debug the example of the frdmkw38_adv_ext_central_freertos on the freedom development board of KW38, but there was something wrong.
Precondition: freedom development board + USB OpenSDA
ps. the frdmkw38_beacon_freertos and frdmkw38_hs_beacon_freertos were OK
the information of the console is below:
MCUXpresso IDE RedlinkMulti Driver v11.6 (Oct 3 2022 08:09:13 - crt_emu_cm_redlink build 9)
Found chip XML file in C:/Users/jian.yu/Documents/MCUXpressoIDE_11.6.1_8255/workspace/frdmkw38_adv_ext_central_freertos/Debug\MKW38A512xxx4.xml
Reconnected to existing LinkServer process.
============= SCRIPT: kinetisconnect.scp =============
Kinetis Connect Script
Connecting to Probe Index = 1
This probe = 1
This TAP = 0
This core = 0
DpID = 0BC11477
Assert NRESET
Reset pin state: 00
Power up Debug
MDM-AP APID: 0x001C0020
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: CMSIS-DAP (ARM)
Serial Number: 0251000053014e450010700ff2d40025e881000097969900
VID:PID: 0D28:0204
USB Path: \\?\hid#vid_0d28&pid_0204&mi_03#7&bc40dc5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
debug interface type = CoreSight DP (DAP DP ID 0BC11477) over SWD TAP 0
processor type = Cortex-M0+ (CPU ID 00000C60) on DAP AP 0
number of h/w breakpoints = 2
number of flash patches = 0
number of h/w watchpoints = 2
Probe(0): Connected&Reset. DpID: 0BC11477. CpuID: 00000C60. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE F0002000: CID B105100D PID 000008E000 ROM (type 0x1)
ROM 1 F0000000: CID B105900D PID 04001BB932 CSt ARM MTB type 0x31 Trace Sink - Basic trace router
ROM 1 F0001000: CID B105900D PID 000008E000 CSt MTBDWT type 0x4 Debug Control - Other
ROM 1 E00FF000: CID B105100D PID 04000BB4C0 ROM (type 0x1)
ROM 4 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)
ROM 4 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)
ROM 4 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)
NXP: MKW38A512xxx4
DAP stride is 1024 bytes (256 words)
Inspected v.2 On chip Kinetis Flash memory module FTFE_2K_PD.cfx
Image 'Kinetis SemiGeneric Sep 19 2022 09:11:31'
Opening flash driver FTFE_2K_PD.cfx
Sending VECTRESET to run flash driver
Flash variant 'KW35 FTFE P&DFlash 2K' detected (512KB = 256*2K at 0x0)
Closing flash driver FTFE_2K_PD.cfx
Inspected v.2 On chip Kinetis Flash memory module FTFE_2K_PD.cfx
Image 'Kinetis SemiGeneric Sep 19 2022 09:11:31'
Opening flash driver FTFE_2K_PD.cfx
Sending VECTRESET to run flash driver
Flash variant 'KW35 FTFE P&DFlash 2K' detected (512KB = 256*2K at 0x0)
Closing flash driver FTFE_2K_PD.cfx
Inspected v.2 On chip Kinetis Flash memory module FTFE_2K_PD.cfx
Image 'Kinetis SemiGeneric Sep 19 2022 09:11:31'
Opening flash driver FTFE_2K_PD.cfx
Sending VECTRESET to run flash driver
Flash variant 'KW35 FTFE P&DFlash 2K' detected (512KB = 256*2K at 0x0)
Closing flash driver FTFE_2K_PD.cfx
Connected: was_reset=true. was_stopped=true
Awaiting telnet connection to port 3330 ...
GDB nonstop mode enabled
FreeRTOS stack backtrace is disabled in Non-stop mode (use All-stop)
GDB stub (C:\nxp\MCUXpressoIDE_11.6.1_8255\ide\plugins\com.nxp.mcuxpresso.tools.bin.win32_11.6.1.202210030617\binaries\crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.
