Hello everyone,

I'm facing issue related to set up JTAG for my raspberry pi. I already researched and refer to many setups, but the result is not as expected. Below is error:

J-Link>connect
Please specify device / core. <Default>: CORTEX-A72
Type '?' for selection dialog
Device>cortex-a72
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>4000
Device "CORTEX-A72" selected.


Connecting to target via JTAG
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
Failed to identify target. Resetting via Reset pin and trying again.
TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
Error occurred: Could not connect to the target device.
For troubleshooting steps visit: wiki.segger.com/J-Link_Troubleshooting

Here are my setup's details:

• Wiring connection (some errors when I upload my wiring connection image):
  

TMS => JTAG PIN#7 => GPIO27 => Pin #13
TRST => JTAG PIN#3 => GPIO22 => Pin #15
RTCK => JTAG PIN#11 => GPIO23 => Pin #16
TCK => JTAG PIN#9 => GPIO25 => Pin #22
TDI => JTAG PIN#5 => GPIO26 => Pin #37
TDO => JTAG PIN#13 => GPIO24 => Pin #18
GND => JTAG PIN#4 => N/A => Pin #34

• Raspberry pi config:
  

[all]
arm_64bit=1

kernel=vmlinuz
cmdline=cmdline.txt
initramfs initrd.img followkernel


gpio=22-27=np
enable_jtag_gpio=1
gpio=23-27=a4
gpio=22=a4,pu
# Enable the audio output, I2C and SPI interfaces on the GPIO header. As these
# parameters related to the base device-tree they must appear *before* any
# other dtoverlay= specification
dtparam=audio=on
#dtparam=i2c_arm=on
dtparam=spi=on


# Comment out the following line if the edges of the desktop appear outside
# the edges of your display
disable_overscan=1


# If you have issues with audio, you may try uncommenting the following line
# which forces the HDMI output into HDMI mode instead of DVI (which doesn't
# support audio output)
#hdmi_drive=2


# Enable the KMS ("full" KMS) graphics overlay, leaving GPU memory as the
# default (the kernel is in control of graphics memory with full KMS)
dtoverlay=vc4-kms-v3d
disable_fw_kms_setup=1


# Autoload overlays for any recognized cameras or displays that are attached
# to the CSI/DSI ports. Please note this is for libcamera support, *not* for
# the legacy camera stack
camera_auto_detect=1
display_auto_detect=1


# Config settings specific to arm64
dtoverlay=dwc2


[pi4]
max_framebuffers=2
arm_boost=1


[pi3+]
# Use a smaller contiguous memory area, specifically on the 3A+ to avoid an
# OOM oops on boot. The 3B+ is also affected by this section, but it shouldn't
# cause any issues on that board
dtoverlay=vc4-kms-v3d,cma-128


[pi02]
# The Zero 2W is another 512MB board which is occasionally affected by the same
# OOM oops on boot.
dtoverlay=vc4-kms-v3d,cma-128


[cm4]
# Enable the USB2 outputs on the IO board (assuming your CM4 is plugged into
# such a board)
dtoverlay=dwc2,dr_mode=host


[all]

• Information of raspberry pi:
  

Revision : c03115
Serial : 10000000dc6f9b54
Model : Raspberry Pi 4 Model B Rev 1.5 => Broadcom 2711, arm cortex-a72
OS: Ubuntu 24.10

Anyone got this problem before? Please help me I stuck with this issue for a week. Thanks.