Troubleshooting KDS Workflow Problems and Debug Configuration
Learn how to open a new SDK 2.x project, name it, inspect the main C within the project, set the debug configuration, and troubleshoot debugging issues when the program doesn't stop at breakpoints or encounters "Source not found" errors in KDS workflow. Explore target related settings for the MK22FN512xxx12 device using J-Link V5.10n, focusing on SWD interface and debugging setup.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
KDS Workflow Problems stephen.g.dame@boeing.com 5/24/2016
Inspect the main.c within the project. (NO CODE CHANGES)
------Target related settings------ Target device: MK22FN512xxx12 *** J-Link V5.10n Warning *** Console Log Target interface: SWD The connected emulator does not support serial wire output (SWO). Target interface speed: 30kHz *** J-Link V5.10n Warning *** Target endian: little Failed to disable SWO. Connecting to J-Link... Failed to enable SWO. Could not determine a suitable SWO speed! J-Link is connected. SEGGER J-Link GDB Server V5.10n Command Line Version Downloading 16 bytes @ address 0x00000400 - Verified OK Firmware: J-Link OpenSDA 2 compiled Oct 13 2015 12:10:56 Downloading 1024 bytes @ address 0x1FFF0000 - Verified OK JLinkARM.dll V5.10n (DLL compiled Feb 19 2016 18:41:43) Hardware: V1.00 Downloading 16080 bytes @ address 0x1FFF0400 - Verified OK -----GDB Server start settings----- S/N: 621000000 Downloading 7112 bytes @ address 0x1FFF42D0 - Verified OK Checking target voltage... Downloading 8 bytes @ address 0x1FFF5E98 - Verified OK GDBInit file: none Target voltage: 3.30 V Downloading 4 bytes @ address 0x1FFF5EA0 - Verified OK GDB Server Listeningport: 2331 Listening on TCP/IP port 2331 Downloading 4 bytes @ address 0x1FFF5EA4 - Verified OK SWO raw output listeningport: 2332 Connecting to target...Connected to target Downloading 120 bytes @ address 0x1FFF5EA8 - Verified OK Waiting for GDB connection...Connected to 127.0.0.1 Writing register (PC = 0x1fff04c8) Terminal I/O port: 2332 Reading all registers Read 4 bytes @ address 0x1FFF04C8 (Data = 0x4809B672) Accept remote connection: localhostonly Read 4 bytes @ address 0x00000000 (Data = 0x20010000) Resetting target Target interface speed set to 30 kHz Halting target CPU... Generate logfile: off Resetting target ...Target halted (PC = 0x000004D8) Verify download: on Halting target CPU... Read 2 bytes @ address 0x1FFF25B8 (Data = 0xF001) Init regs on start: on ...Target halted (PC = 0x000004D8) Read 2 bytes @ address 0x1FFF25B8 (Data = 0xF001) R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000 Read 2 bytes @ address 0x1FFF25B8 (Data = 0xF001) Silent mode: off R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000 R0 = 00000000, R1 = 00000000, R2 = 00000000, R3 = 00000000 Single run mode: on R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000 R4 = 00000000, R5 = 00000000, R6 = 00000000, R7 = 00000000 Target connection timeout: 0 ms R12= 00000000, R13= 20010000, MSP= 20010000, PSP= 00000000 R8 = 00000000, R9 = 00000000, R10= 00000000, R11= 00000000 R14(LR) = FFFFFFFF, R15(PC) = 000004D8 R12= 00000000, R13= 20010000, MSP= 20010000, PSP= 00000000 ------J-Link related settings------ XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000 R14(LR) = FFFFFFFF, R15(PC) = 000004D8 J-Link Host interface: USB CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00 XPSR 01000000, APSR 00000000, EPSR 01000000, IPSR 00000000 Reading all registers CFBP 00000000, CONTROL 00, FAULTMASK 00, BASEPRI 00, PRIMASK 00 J-Link script: none Select auto target interface speed (1429 kHz) Reading all registers J-Link settings file: none Flash breakpoints enabled Read 4 bytes @ address 0x000004D8 (Data = 0x480DB672) Semi-hosting enabled (Handle on BKPT) Setting breakpoint @ address 0x1FFF25B8, Size = 2, BPHandle = 0x0001 Wrong client mask. Semihosting I/O not changed. Starting target CPU...
Attempt to debug Test2 again No JOY (Also tried adding just a print statement)
Description I loaded any one of the imported projects (e.g. bubble level) These imported projects tend to have a way of staying in memory and the new Test2 project will not load. It resets the processor and looks like something it loading, but then the debugger comes up running and has the old previous imported project in it. All of the debug configuration settings are the same between the imported project and the new SDK 2.x project. Bottom line is why doesn t the new project load?
