How to debug Core A53 of iMX8MP using JLink debugger

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to debug Core A53 of iMX8MP using JLink debugger

Jump to solution
1,387 Views
AbdulELPRO
Contributor II

Hi, I'm trying to debug imx8mp (Custom board, SOM Solidrun) using J-Link but once I tried to connect Linux rebooted every time even I tried from UBoot as well. see the logs below from J-LINK

SEGGER J-Link Commander V8.54 (Compiled Jul 23 2025 12:21:02)
DLL version V8.54, compiled Jul 23 2025 12:20:05

Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Jan 30 2023 11:28:07
Hardware version: V10.10
J-Link uptime (since boot): N/A (Not supported by this model)
S/N: 600113317
License(s): RDI, FlashBP, FlashDL, JFlash, GDB
VTref=3.425V


Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MIMX8ML8_A53_0
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>J
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "MIMX8ML8_A53_0" selected.


Connecting to target via JTAG
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 30us
InitTarget() start
InitTarget() end - Took 52.3ms
TotalIRLen = 5, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x00000000, IRLen: 05, Unknown device
Connect failed. Resetting via Reset pin and trying again.
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 40us
InitTarget() start
DAP: Could not power-up system power domain.
InitTarget() end - Took 4.70ms
Could not measure total IR len. TDO is constant high.
Failed to identify target. Resetting via Reset pin and trying again.
ConfigTargetSettings() start
ConfigTargetSettings() end - Took 14us
InitTarget() start
DAP: Could not power-up system power domain.
InitTarget() end - Took 3.80ms

****** Error: CPU-TAP not found in JTAG chain
Supply voltage too low (1 Volt is required, Measured: 0.0 Volt).
Please check target power.
Target voltage too low. Please check https://kb.segger.com/J-Link_cannot_connect_to_the_CPU#Target_connection.
Error occurred: Could not connect to the target device.
For troubleshooting steps visit: https://kb.segger.com/J-Link_Troubleshooting
J-Link>

Tags (3)
0 Kudos
Reply
1 Solution
1,359 Views
AbdulELPRO
Contributor II

Got working, its need to be in eMMC mode 

openocd -f interface/jlink.cfg -f board/imx8mp-evk.cfg
Open On-Chip Debugger 0.12.0 (2025-07-10) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 d52e355daa09f17ce64819122cb067b8a2ee0d4b
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : [imx8mp.a53.0] Hardware thread awareness created
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : J-Link V10 compiled Jan 30 2023 11:28:07
Info : Hardware version: 10.10
Info : VTarget = 3.425 V
Info : clock speed 4000 kHz
Info : JTAG tap: imx8mp.cpu tap/device found: 0x5ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x5)
Info : imx8mp.a53.0: hardware has 6 breakpoints, 4 watchpoints
Info : [imx8mp.a53.0] external reset detected
Info : [imx8mp.a53.0] Examination succeed
Info : [imx8mp.ahb] Examination succeed
Info : [imx8mp.a53.0] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections
Info : [imx8mp.m4] starting gdb server on 3334
Info : Listening on port 3334 for gdb connections
Info : [imx8mp.ahb] gdb port disabled

View solution in original post

3 Replies
1,360 Views
AbdulELPRO
Contributor II

Got working, its need to be in eMMC mode 

openocd -f interface/jlink.cfg -f board/imx8mp-evk.cfg
Open On-Chip Debugger 0.12.0 (2025-07-10) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 d52e355daa09f17ce64819122cb067b8a2ee0d4b
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : [imx8mp.a53.0] Hardware thread awareness created
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : J-Link V10 compiled Jan 30 2023 11:28:07
Info : Hardware version: 10.10
Info : VTarget = 3.425 V
Info : clock speed 4000 kHz
Info : JTAG tap: imx8mp.cpu tap/device found: 0x5ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x5)
Info : imx8mp.a53.0: hardware has 6 breakpoints, 4 watchpoints
Info : [imx8mp.a53.0] external reset detected
Info : [imx8mp.a53.0] Examination succeed
Info : [imx8mp.ahb] Examination succeed
Info : [imx8mp.a53.0] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections
Info : [imx8mp.m4] starting gdb server on 3334
Info : Listening on port 3334 for gdb connections
Info : [imx8mp.ahb] gdb port disabled

1,314 Views
Rita_Wang
NXP TechSupport
NXP TechSupport

Good news it can works and thanks for sharing.

0 Kudos
Reply
1,377 Views
AbdulELPRO
Contributor II

When I tried openocd then I got the following: 

openocd -f interface/jlink.cfg -f board/imx8mp-evk.cfg
Open On-Chip Debugger 0.12.0 (2025-07-10) [https://github.com/sysprogs/openocd]
Licensed under GNU GPL v2
libusb1 d52e355daa09f17ce64819122cb067b8a2ee0d4b
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
Info : [imx8mp.a53.0] Hardware thread awareness created
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : J-Link V10 compiled Jan 30 2023 11:28:07
Info : Hardware version: 10.10
Info : VTarget = 3.425 V
Info : clock speed 400 kHz
Info : JTAG tap: imx8mp.cpu tap/device found: 0x088e601d (mfg: 0x00e (Freescale (Motorola)), part: 0x88e6, ver: 0x0)
Warn : JTAG tap: imx8mp.cpu UNEXPECTED: 0x088e601d (mfg: 0x00e (Freescale (Motorola)), part: 0x88e6, ver: 0x0)
Error: JTAG tap: imx8mp.cpu expected 1 of 1: 0x5ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x5)
Error: Trying to use configured scan chain anyway...
Error: IR capture error at bit 4, saw 0x21 not 0x...3
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (0) in DAP response

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2148029%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EHow%20to%20debug%20Core%20A53%20of%20iMX8MP%20using%20JLink%20debugger%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148029%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%20I'm%20trying%20to%20debug%20imx8mp%20(Custom%20board%2C%20SOM%20Solidrun)%20using%20J-Link%20but%20once%20I%20tried%20to%20connect%20Linux%20rebooted%20every%20time%20even%20I%20tried%20from%20UBoot%20as%20well.%20see%20the%20logs%20below%20from%20J-LINK%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3ESEGGER%20J-Link%20Commander%20V8.54%20(Compiled%20Jul%2023%202025%2012%3A21%3A02)%3CBR%20%2F%3EDLL%20version%20V8.54%2C%20compiled%20Jul%2023%202025%2012%3A20%3A05%3C%2FP%3E%3CP%3EConnecting%20to%20J-Link%20via%20USB...O.K.%3CBR%20%2F%3E%3CSTRONG%3EFirmware%3A%20J-Link%20V10%20compiled%20Jan%2030%202023%2011%3A28%3A07%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSTRONG%3EHardware%20version%3A%20V10.10%3C%2FSTRONG%3E%3CBR%20%2F%3EJ-Link%20uptime%20(since%20boot)%3A%20N%2FA%20(Not%20supported%20by%20this%20model)%3CBR%20%2F%3ES%2FN%3A%20600113317%3CBR%20%2F%3ELicense(s)%3A%20RDI%2C%20FlashBP%2C%20FlashDL%2C%20JFlash%2C%20GDB%3CBR%20%2F%3EVTref%3D3.425V%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EType%20%22connect%22%20to%20establish%20a%20target%20connection%2C%20'%3F'%20for%20help%3CBR%20%2F%3EJ-Link%26gt%3Bconnect%3CBR%20%2F%3EPlease%20specify%20device%20%2F%20core.%20%3CDEFAULT%3E%3A%20MIMX8ML8_A53_0%3CBR%20%2F%3EType%20'%3F'%20for%20selection%20dialog%3CBR%20%2F%3EDevice%26gt%3B%3CBR%20%2F%3EPlease%20specify%20target%20interface%3A%3CBR%20%2F%3EJ)%20JTAG%20(Default)%3CBR%20%2F%3ES)%20SWD%3CBR%20%2F%3ET)%20cJTAG%3CBR%20%2F%3ETIF%26gt%3BJ%3CBR%20%2F%3EDevice%20position%20in%20JTAG%20chain%20(IRPre%2CDRPre)%20%3CDEFAULT%3E%3A%20-1%2C-1%20%3D%26gt%3B%20Auto-detect%3CBR%20%2F%3EJTAGConf%26gt%3B%3CBR%20%2F%3ESpecify%20target%20interface%20speed%20%5BkHz%5D.%20%3CDEFAULT%3E%3A%204000%20kHz%3CBR%20%2F%3ESpeed%26gt%3B%3CBR%20%2F%3EDevice%20%22MIMX8ML8_A53_0%22%20selected.%3C%2FDEFAULT%3E%3C%2FDEFAULT%3E%3C%2FDEFAULT%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EConnecting%20to%20target%20via%20JTAG%3CBR%20%2F%3EConfigTargetSettings()%20start%3CBR%20%2F%3EConfigTargetSettings()%20end%20-%20Took%2030us%3CBR%20%2F%3EInitTarget()%20start%3CBR%20%2F%3EInitTarget()%20end%20-%20Took%2052.3ms%3CBR%20%2F%3ETotalIRLen%20%3D%205%2C%20IRPrint%20%3D%200x01%3CBR%20%2F%3EJTAG%20chain%20detection%20found%201%20devices%3A%3CBR%20%2F%3E%230%20Id%3A%200x00000000%2C%20IRLen%3A%2005%2C%20Unknown%20device%3CBR%20%2F%3EConnect%20failed.%20Resetting%20via%20Reset%20pin%20and%20trying%20again.%3CBR%20%2F%3EConfigTargetSettings()%20start%3CBR%20%2F%3EConfigTargetSettings()%20end%20-%20Took%2040us%3CBR%20%2F%3EInitTarget()%20start%3CBR%20%2F%3EDAP%3A%20Could%20not%20power-up%20system%20power%20domain.%3CBR%20%2F%3EInitTarget()%20end%20-%20Took%204.70ms%3CBR%20%2F%3ECould%20not%20measure%20total%20IR%20len.%20TDO%20is%20constant%20high.%3CBR%20%2F%3EFailed%20to%20identify%20target.%20Resetting%20via%20Reset%20pin%20and%20trying%20again.%3CBR%20%2F%3EConfigTargetSettings()%20start%3CBR%20%2F%3EConfigTargetSettings()%20end%20-%20Took%2014us%3CBR%20%2F%3EInitTarget()%20start%3CBR%20%2F%3EDAP%3A%20Could%20not%20power-up%20system%20power%20domain.%3CBR%20%2F%3EInitTarget()%20end%20-%20Took%203.80ms%3C%2FP%3E%3CP%3E******%20Error%3A%20CPU-TAP%20not%20found%20in%20JTAG%20chain%3CBR%20%2F%3ESupply%20voltage%20too%20low%20(1%20Volt%20is%20required%2C%20Measured%3A%200.0%20Volt).%3CBR%20%2F%3EPlease%20check%20target%20power.%3CBR%20%2F%3ETarget%20voltage%20too%20low.%20Please%20check%20%3CA%20href%3D%22https%3A%2F%2Fkb.segger.com%2FJ-Link_cannot_connect_to_the_CPU%23Target_connection%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fkb.segger.com%2FJ-Link_cannot_connect_to_the_CPU%23Target_connection%3C%2FA%3E.%3CBR%20%2F%3EError%20occurred%3A%20Could%20not%20connect%20to%20the%20target%20device.%3CBR%20%2F%3EFor%20troubleshooting%20steps%20visit%3A%20%3CA%20href%3D%22https%3A%2F%2Fkb.segger.com%2FJ-Link_Troubleshooting%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fkb.segger.com%2FJ-Link_Troubleshooting%3C%2FA%3E%3CBR%20%2F%3EJ-Link%26gt%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2149938%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20How%20to%20debug%20Core%20A53%20of%20iMX8MP%20using%20JLink%20debugger%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2149938%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EGood%20news%20it%20can%20works%20and%20thanks%20for%20sharing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2148106%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20How%20to%20debug%20Core%20A53%20of%20iMX8MP%20using%20JLink%20debugger%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148106%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EGot%20working%2C%20its%20need%20to%20be%20in%20eMMC%20mode%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3Eopenocd%20-f%20interface%2Fjlink.cfg%20-f%20board%2Fimx8mp-evk.cfg%3CBR%20%2F%3EOpen%20On-Chip%20Debugger%200.12.0%20(2025-07-10)%20%5B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fsysprogs%2Fopenocd%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fsysprogs%2Fopenocd%3C%2FA%3E%5D%3CBR%20%2F%3ELicensed%20under%20GNU%20GPL%20v2%3CBR%20%2F%3Elibusb1%20d52e355daa09f17ce64819122cb067b8a2ee0d4b%3CBR%20%2F%3EFor%20bug%20reports%2C%20read%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Fopenocd.org%2Fdoc%2Fdoxygen%2Fbugs.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fopenocd.org%2Fdoc%2Fdoxygen%2Fbugs.html%3C%2FA%3E%3CBR%20%2F%3EInfo%20%3A%20%5Bimx8mp.a53.0%5D%20Hardware%20thread%20awareness%20created%3CBR%20%2F%3EInfo%20%3A%20Listening%20on%20port%206666%20for%20tcl%20connections%3CBR%20%2F%3EInfo%20%3A%20Listening%20on%20port%204444%20for%20telnet%20connections%3CBR%20%2F%3EInfo%20%3A%20J-Link%20V10%20compiled%20Jan%2030%202023%2011%3A28%3A07%3CBR%20%2F%3EInfo%20%3A%20Hardware%20version%3A%2010.10%3CBR%20%2F%3EInfo%20%3A%20VTarget%20%3D%203.425%20V%3CBR%20%2F%3EInfo%20%3A%20clock%20speed%204000%20kHz%3CBR%20%2F%3EInfo%20%3A%20JTAG%20tap%3A%20imx8mp.cpu%20tap%2Fdevice%20found%3A%200x5ba00477%20(mfg%3A%200x23b%20(ARM%20Ltd)%2C%20part%3A%200xba00%2C%20ver%3A%200x5)%3CBR%20%2F%3EInfo%20%3A%20imx8mp.a53.0%3A%20hardware%20has%206%20breakpoints%2C%204%20watchpoints%3CBR%20%2F%3EInfo%20%3A%20%5Bimx8mp.a53.0%5D%20external%20reset%20detected%3CBR%20%2F%3EInfo%20%3A%20%5Bimx8mp.a53.0%5D%20Examination%20succeed%3CBR%20%2F%3EInfo%20%3A%20%5Bimx8mp.ahb%5D%20Examination%20succeed%3CBR%20%2F%3EInfo%20%3A%20%5Bimx8mp.a53.0%5D%20starting%20gdb%20server%20on%203333%3CBR%20%2F%3EInfo%20%3A%20Listening%20on%20port%203333%20for%20gdb%20connections%3CBR%20%2F%3EInfo%20%3A%20%5Bimx8mp.m4%5D%20starting%20gdb%20server%20on%203334%3CBR%20%2F%3EInfo%20%3A%20Listening%20on%20port%203334%20for%20gdb%20connections%3CBR%20%2F%3EInfo%20%3A%20%5Bimx8mp.ahb%5D%20gdb%20port%20disabled%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2148038%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20How%20to%20debug%20Core%20A53%20of%20iMX8MP%20using%20JLink%20debugger%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2148038%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EWhen%20I%20tried%20openocd%20then%20I%20got%20the%20following%3A%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3Eopenocd%20-f%20interface%2Fjlink.cfg%20-f%20board%2Fimx8mp-evk.cfg%3CBR%20%2F%3EOpen%20On-Chip%20Debugger%200.12.0%20(2025-07-10)%20%5B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fsysprogs%2Fopenocd%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fsysprogs%2Fopenocd%3C%2FA%3E%5D%3CBR%20%2F%3ELicensed%20under%20GNU%20GPL%20v2%3CBR%20%2F%3Elibusb1%20d52e355daa09f17ce64819122cb067b8a2ee0d4b%3CBR%20%2F%3EFor%20bug%20reports%2C%20read%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Fopenocd.org%2Fdoc%2Fdoxygen%2Fbugs.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fopenocd.org%2Fdoc%2Fdoxygen%2Fbugs.html%3C%2FA%3E%3CBR%20%2F%3EInfo%20%3A%20%5Bimx8mp.a53.0%5D%20Hardware%20thread%20awareness%20created%3CBR%20%2F%3EInfo%20%3A%20Listening%20on%20port%206666%20for%20tcl%20connections%3CBR%20%2F%3EInfo%20%3A%20Listening%20on%20port%204444%20for%20telnet%20connections%3CBR%20%2F%3EInfo%20%3A%20J-Link%20V10%20compiled%20Jan%2030%202023%2011%3A28%3A07%3CBR%20%2F%3EInfo%20%3A%20Hardware%20version%3A%2010.10%3CBR%20%2F%3EInfo%20%3A%20VTarget%20%3D%203.425%20V%3CBR%20%2F%3EInfo%20%3A%20clock%20speed%20400%20kHz%3CBR%20%2F%3EInfo%20%3A%20JTAG%20tap%3A%20imx8mp.cpu%20tap%2Fdevice%20found%3A%200x088e601d%20(mfg%3A%200x00e%20(Freescale%20(Motorola))%2C%20part%3A%200x88e6%2C%20ver%3A%200x0)%3CBR%20%2F%3EWarn%20%3A%20JTAG%20tap%3A%20imx8mp.cpu%20UNEXPECTED%3A%200x088e601d%20(mfg%3A%200x00e%20(Freescale%20(Motorola))%2C%20part%3A%200x88e6%2C%20ver%3A%200x0)%3CBR%20%2F%3EError%3A%20JTAG%20tap%3A%20imx8mp.cpu%20expected%201%20of%201%3A%200x5ba00477%20(mfg%3A%200x23b%20(ARM%20Ltd)%2C%20part%3A%200xba00%2C%20ver%3A%200x5)%3CBR%20%2F%3EError%3A%20Trying%20to%20use%20configured%20scan%20chain%20anyway...%3CBR%20%2F%3EError%3A%20IR%20capture%20error%20at%20bit%204%2C%20saw%200x21%20not%200x...3%3CBR%20%2F%3EWarn%20%3A%20Bypassing%20JTAG%20setup%20events%20due%20to%20errors%3CBR%20%2F%3EError%3A%20Invalid%20ACK%20(0)%20in%20DAP%20response%3C%2FP%3E%3C%2FLINGO-BODY%3E