Issue with J-Link Debugging on RT1060 Custom Board Not Jumping to Main Function

pooisonner — Tue, 02 Sep 2025 09:17:41 GMT

Hello, I am developing with the RT1060 and encountering an issue. I would appreciate your help.

I was developing on the RT1060 EVBC board using the Matter SDK. The boot mode was set to Internal Boot, and it was operating in XIP mode. Debugging was possible via SWD using the LinkServer connected to the development board. Now, a custom board has been developed with the same QSPI flash connected as on the EVB board, and I am trying to debug using J-Link. However, while the connection is established, it does not jump to the main function. The boot mode and boot configuration are identical to those of the EVB board, but it is not working.

Below is the J-Link message from the custom board:

```
[2025-09-02T09:08:04.771Z] SERVER CONSOLE DEBUG: GDB server connection established. Switch to "DEBUG CONSOLE" to see GDB traces.
"C:\\Program Files\\SEGGER\\JLink_V864\\JLinkGDBServerCL.exe" -SettingsFile "C:\\nxp_LG_Apple\\nxp_matter_release_v1_4_0\\examples\\thermostat\\nxp\\debug\\JLink_app.jlink" -nosilent -singlerun -endian little -noir -speed 4000 -port 2362 -vd -device MIMXRT1062xxx6A -if SWD -reportuseraction -nogui -select usb=59102252 -halt -swoport 2364 -telnetport 2363
SEGGER J-Link GDB Server V8.64 Command Line Version

JLinkARM.dll V8.64 (DLL compiled Aug 28 2025 10:04:20)

Command line: -SettingsFile C:\nxp_LG_Apple\nxp_matter_release_v1_4_0\examples\thermostat\nxp\debug\JLink_app.jlink -nosilent -singlerun -endian little -noir -speed 4000 -port 2362 -vd -device MIMXRT1062xxx6A -if SWD -reportuseraction -nogui -select usb=59102252 -halt -swoport 2364 -telnetport 2363
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2362
SWO raw output listening port: 2364
Terminal I/O port: 2363
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: off
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: C:\nxp_LG_Apple\nxp_matter_release_v1_4_0\examples\thermostat\nxp\debug\JLink_app.jlink
------Target related settings------
Target device: MIMXRT1062xxx6A
Target device parameters: none
Target interface: SWD
Target interface speed: 4000kHz
Target endian: little

Connecting to J-Link...
J-Link is connected.
Device "MIMXRT1062XXX6A" selected.
Firmware: J-Link V9 compiled May 7 2021 16:26:12
Hardware: V9.10
S/N: 59102252
Feature(s): GDB
Checking target voltage...
Target voltage: 3.32 V
Listening on TCP/IP port 2362
Connecting to target...
InitTarget() start
InitTarget() end - Took 3.71ms
Found SW-DP with ID 0x0BD11477
DPIDR: 0x0BD11477
CoreSight SoC-400 or earlier
Scanning AP map to find all available APs
AP[1]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x04770041, ADDR: 0x00000000)
Iterating through AP map to find AHB-AP to use
AP[0]: Core found
AP[0]: AHB-AP ROM base: 0xE00FD000
CPUID register: 0x411FC271. Implementer code: 0x41 (ARM)
Cache: L1 I/D-cache present
Found Cortex-M7 r1p1, Little endian.
FPUnit: 8 code (BP) slots and 0 literal slots
CoreSight components:
ROMTbl[0] @ E00FD000
[0][0]: E00FE000 CID B105100D PID 000BB4C8 ROM Table
ROMTbl[1] @ E00FE000
[1][0]: E00FF000 CID B105100D PID 000BB4C7 ROM Table
ROMTbl[2] @ E00FF000
[2][0]: E000E000 CID B105E00D PID 000BB00C SCS-M7
[2][1]: E0001000 CID B105E00D PID 000BB002 DWT
[2][2]: E0002000 CID B105E00D PID 000BB00E FPB-M7
[2][3]: E0000000 CID B105E00D PID 000BB001 ITM
[1][1]: E0041000 CID B105900D PID 001BB975 ETM-M7
[1][2]: E0042000 CID B105900D PID 004BB906 CTI
[0][1]: E0040000 CID B105900D PID 000BB9A9 TPIU-M7
[0][2]: E0043000 CID B105F00D PID 001BB101 TSG
I-Cache L1: 32 KB, 512 Sets, 32 Bytes/Line, 2-Way
D-Cache L1: 32 KB, 256 Sets, 32 Bytes/Line, 4-Way
Halting core...
Connected to target
Waiting for GDB connection...Connected to 127.0.0.1
GDB client (conn. 880) requested target.xml from GDB Server
Reading common registers:
Read register 'r0' (4 bytes) from hardware: 0x00000000
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x00000001
Read register 'r3' (4 bytes) from hardware: 0x00000000
Read register 'r4' (4 bytes) from hardware: 0x20207A3C
Read register 'r5' (4 bytes) from hardware: 0x401F4460
Read register 'r6' (4 bytes) from hardware: 0x401F4470
Read register 'r7' (4 bytes) from hardware: 0x401F4400
Read register 'r8' (4 bytes) from hardware: 0x00000001
Read register 'r9' (4 bytes) from hardware: 0x4D0A26F7
Read register 'r10' (4 bytes) from hardware: 0x00000000
Read register 'r11' (4 bytes) from hardware: 0x400F8000
Read register 'r12' (4 bytes) from hardware: 0x00000004
Read register 'sp' (4 bytes) from hardware: 0x20200F90
Read register 'lr' (4 bytes) from hardware: 0x0020ED49
Read register 'pc' (4 bytes) from hardware: 0x0020ED48
Read register 'xpsr' (4 bytes) from hardware: 0x41000000
Read 4 bytes @ address 0x0020ED48 (Data = 0x28007F20)
Read 2 bytes @ address 0x0020ED48 (Data = 0x7F20)
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x0020ED48)
Received monitor command: reset
ResetTarget() start
Core did not halt after reset.
Halting target manually.
ResetTarget() end - Took 344ms
Device specific reset executed.
AfterResetTarget() start
AfterResetTarget() end - Took 3.80ms
Resetting target
Downloading 512 bytes @ address 0x60000000 - Verified OK
Downloading 1088 bytes @ address 0x60001000 - Verified OK
Downloading 1024 bytes @ address 0x60002000 - Verified OK
Downloading 64928 bytes @ address 0x60002400 - Verified OK
Downloading 64720 bytes @ address 0x600121A0 - Verified OK
Downloading 64416 bytes @ address 0x60021E70 - Verified OK
Downloading 64400 bytes @ address 0x60031A10 - Verified OK
Downloading 64368 bytes @ address 0x600415A0 - Verified OK
Downloading 64256 bytes @ address 0x60051110 - Verified OK
Downloading 64288 bytes @ address 0x60060C10 - Verified OK
Downloading 64288 bytes @ address 0x60070730 - Verified OK
Downloading 64176 bytes @ address 0x60080250 - Verified OK
Downloading 64464 bytes @ address 0x6008FD00 - Verified OK
Downloading 64064 bytes @ address 0x6009F8D0 - Verified OK
Downloading 64272 bytes @ address 0x600AF310 - Verified OK
Downloading 64016 bytes @ address 0x600BEE20 - Verified OK
Downloading 63888 bytes @ address 0x600CE830 - Verified OK
Downloading 63936 bytes @ address 0x600DE1C0 - Verified OK
Downloading 64016 bytes @ address 0x600EDB80 - Verified OK
Downloading 64336 bytes @ address 0x600FD590 - Verified OK
Downloading 64272 bytes @ address 0x6010D0E0 - Verified OK
Downloading 65472 bytes @ address 0x6011CBF0 - Verified OK
Downloading 64608 bytes @ address 0x6012CBB0 - Verified OK
Downloading 64496 bytes @ address 0x6013C810 - Verified OK
Downloading 64448 bytes @ address 0x6014C400 - Verified OK
Downloading 64512 bytes @ address 0x6015BFC0 - Verified OK
Downloading 64480 bytes @ address 0x6016BBC0 - Verified OK
Downloading 64480 bytes @ address 0x6017B7A0 - Verified OK
Downloading 64528 bytes @ address 0x6018B380 - Verified OK
Downloading 64496 bytes @ address 0x6019AF90 - Verified OK
Downloading 64464 bytes @ address 0x601AAB80 - Verified OK
Downloading 64448 bytes @ address 0x601BA750 - Verified OK
Downloading 64464 bytes @ address 0x601CA310 - Verified OK
Downloading 64512 bytes @ address 0x601D9EE0 - Verified OK
Downloading 64512 bytes @ address 0x601E9AE0 - Verified OK
Downloading 64528 bytes @ address 0x601F96E0 - Verified OK
Downloading 64528 bytes @ address 0x602092F0 - Verified OK
Downloading 64512 bytes @ address 0x60218F00 - Verified OK
Downloading 64608 bytes @ address 0x60228B00 - Verified OK
Downloading 65136 bytes @ address 0x60238760 - Verified OK
Downloading 9200 bytes @ address 0x602485D0 - Verified OK
Downloading 16 bytes @ address 0x6024A9C0 - Verified OK
Downloading 36 bytes @ address 0x6024A9D4 - Verified OK
Downloading 8 bytes @ address 0x6024A9F4 - Verified OK
Downloading 180 bytes @ address 0x6024A9FC - Verified OK
Downloading 4 bytes @ address 0x6024AAB0 - Verified OK
Downloading 7136 bytes @ address 0x6024AAB4 - Verified OK
Downloading 64188 bytes @ address 0x6024C694 - Verified OK
Downloading 12356 bytes @ address 0x6025C150 - Verified OK
Downloading 208 bytes @ address 0x6025F194 - Verified OK
Downloading 128 bytes @ address 0x60FDFC00 - Verified OK
Downloading 65504 bytes @ address 0x60FE0000 - Verified OK
Downloading 65504 bytes @ address 0x60FEFFE0 - Verified OK
Downloading 64 bytes @ address 0x60FFFFC0 - Verified OK
Writing register 'pc' = 0x6005EA4C
Comparing flash [....................] Done.
J-Link: Flash download: Bank 0 @ 0x60000000: Skipped. Contents already match
Received monitor command: exec SetRestartOnClose=1
Executed SetRestartOnClose=1
Received monitor command: reset
ResetTarget() start
Core did not halt after reset.
Halting target manually.
ResetTarget() end - Took 340ms
Device specific reset executed.
AfterResetTarget() start
AfterResetTarget() end - Took 3.84ms
Resetting target
Read 4 bytes @ address 0x6005EA4C (Data = 0x481BB672)
Read 2 bytes @ address 0x6005EA4C (Data = 0xB672)
Reading 64 bytes @ address 0x60008980
Read 2 bytes @ address 0x600089BA (Data = 0xF7FF)
Setting breakpoint @ address 0x600089BA, Kind = 2, Type = THUMB, BPHandle = 0x0001
Starting target CPU...
Memory map 'after startup completion point' is active
Debugger requested to halt target...
...Target halted (PC = 0x0020D112)
Reading common registers:
Read register 'r0' (4 bytes) from hardware: 0x00000000
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x00000001
Read register 'r3' (4 bytes) from hardware: 0x00000000
Read register 'r4' (4 bytes) from hardware: 0x20203A70
Read register 'r5' (4 bytes) from hardware: 0x401F4460
Read register 'r6' (4 bytes) from hardware: 0x401F4470
Read register 'r7' (4 bytes) from hardware: 0x401F4400
Read register 'r8' (4 bytes) from hardware: 0x00000001
Read register 'r9' (4 bytes) from hardware: 0xD333F1EC
Read register 'r10' (4 bytes) from hardware: 0x00000000
Read register 'r11' (4 bytes) from hardware: 0x400F8000
Read register 'r12' (4 bytes) from hardware: 0x00000004
Read register 'sp' (4 bytes) from hardware: 0x20200F98
Read register 'lr' (4 bytes) from hardware: 0x0020ED49
Read register 'pc' (4 bytes) from hardware: 0x0020D112
Read register 'xpsr' (4 bytes) from hardware: 0x61000000
Removing breakpoint @ address 0x600089BA, Size = 2
Read 4 bytes @ address 0x0020D112 (Data = 0xB570BD10)
Read 2 bytes @ address 0x0020D112 (Data = 0xBD10)
Reading register 'msp' = 0x20200F98
Reading register 'psp' = 0x00000000
Read 4 bytes @ address 0x0020ED48 (Data = 0x28007F20)
Read 2 bytes @ address 0x0020ED48 (Data = 0x7F20)
Read 4 bytes @ address 0x0020ED48 (Data = 0x28007F20)
Read 2 bytes @ address 0x0020ED48 (Data = 0x7F20)
Setting breakpoint @ address 0x600089BA, Kind = 2, Type = THUMB, BPHandle = 0x0002
Starting target CPU...
Debugger requested to halt target...
...Target halted (PC = 0x0020ED4A)
Reading common registers:
Read register 'r0' (4 bytes) from hardware: 0x00000000
Read register 'r1' (4 bytes) from hardware: 0x00000000
Read register 'r2' (4 bytes) from hardware: 0x00000001
Read register 'r3' (4 bytes) from hardware: 0x00000000
Read register 'r4' (4 bytes) from hardware: 0x20207A3C
Read register 'r5' (4 bytes) from hardware: 0x401F4460
Read register 'r6' (4 bytes) from hardware: 0x401F4470
Read register 'r7' (4 bytes) from hardware: 0x401F4400
Read register 'r8' (4 bytes) from hardware: 0x00000001
Read register 'r9' (4 bytes) from hardware: 0xD333F1EC
Read register 'r10' (4 bytes) from hardware: 0x00000000
Read register 'r11' (4 bytes) from hardware: 0x400F8000
Read register 'r12' (4 bytes) from hardware: 0x00000004
Read register 'sp' (4 bytes) from hardware: 0x20200F90
Read register 'lr' (4 bytes) from hardware: 0x0020ED49
Read register 'pc' (4 bytes) from hardware: 0x0020ED4A
Read register 'xpsr' (4 bytes) from hardware: 0x41000000
Removing breakpoint @ address 0x600089BA, Size = 2
Read 4 bytes @ address 0x0020ED4A (Data = 0xD0072800)
Read 2 bytes @ address 0x0020ED4A (Data = 0x2800)
Received monitor command: halt
Halting target CPU...
...Target halted (PC = 0x0020ED4A)
Received monitor command: reset
Memory map 'before startup completion point' is active
```

Re: Issue with J-Link Debugging on RT1060 Custom Board Not Jumping to Main Function

Omar_Anguiano — Thu, 04 Sep 2025 22:21:59 GMT

Is this issue only happening with matter SDK? Does any other example on the SDK works well? You could try the led blinky example to check if this persists, but before the tes,t it is convenient to perform the recovery of the board:
RT board recovery for debugger connect issues - NXP Community

BR,
Omar

topic Issue with J-Link Debugging on RT1060 Custom Board Not Jumping to Main Function in i.MX RT Crossover MCUs

Issue with J-Link Debugging on RT1060 Custom Board Not Jumping to Main Function

Re: Issue with J-Link Debugging on RT1060 Custom Board Not Jumping to Main Function