I am planning to develop RTOS-based firmware on the M7 with the i.MX8M plus.
I'll use A53 with Linux.
So I'm using the evaluation kit "8MPLUSLPD4-PEVK" that I have, building a sample project with MCUXpresso for VSCode, and trying to test debugging with Segger's j-Link.
I was able to generate the target elf and bin without any problems up until the build stage, but when I tried to debug, I couldn't connect to the target evaluation kit with j-Link.
The evaluation kit is SD booted, and u-boot is started with the debug UART, but Linux has not yet started.
Since I can't connect from VS Code in this state, I tried to connect with Segger's j-Link commander, but I couldn't connect.
I'd like to know if there are any settings required to debug the M7 via JTAG.
Below is the log from j-Link commander
SEGGER J-Link Commander V8.46 (Compiled Jun 26 2025 07:49:03)
DLL version V8.46, compiled Jun 26 2025 07:48:12
Connecting to J-Link via USB...O.K.
Firmware: J-Link V11 compiled Apr 1 2025 10:02:30
Hardware version: V11.00
J-Link uptime (since boot): 0d 00h 01m 58s
S/N: 51020038
License(s): GDB
USB speed mode: High speed (480 MBit/s)
VTref=1.704V
Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MIMX8ML8_M7
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MIMX8ML8_M7" selected.
Connecting to target via JTAG
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 1.91ms
InitTarget() start
InitTarget() end - Took 54.9ms
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
Failed to identify target. Resetting via Reset pin and trying again.
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 22us
InitTarget() start
InitTarget() end - Took 52.6ms
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
Error occurred: Could not connect to the target device.
For troubleshooting steps visit: https://kb.segger.com/J-Link_Troubleshooting
J-Link>