Hi @rudhi.tx,
When I use Ubuntu 22.04, nothing happens and it is not connected to the Jlink debugger.
The debugger’s led remains red.
On the Verdin development board, I connected the debugger to pin header X67.
my debugger is Segger basic j-link and it supports imx8 mini, I have imx8 mini with TorizonCore 6
MCUXpresso SDK:
SDK_2.13.0_MIMX8MM6xxxKZ
The GCC Toolchain:
x86_64 Linux hosted cross toolchains
AArch32 bare-metal target (arm-none-eabi)arm-gnu-toolchain-12.2.MPACBTI-Rel1-x86_64-arm-none-eabi.tar.xz
The output of Ubuntu:
mehrdad@LAPTOP-DHGJM4R6:~$ JLinkGDBServer -if JTAG -device MIMX8MM6_M4
SEGGER J-Link GDB Server V7.70c Command Line Version
JLinkARM.dll V7.70c (DLL compiled Aug 18 2022 17:29:50)
Command line: -if JTAG -device MIMX8MM6_M4
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2331
SWO raw output listening port: 2332
Terminal I/O port: 2333
Accept remote connection: yes
Generate logfile: off
Verify download: off
Init regs on start: off
Silent mode: off
Single run mode: off
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: MIMX8MM6_M4
Target device parameters: none
Target interface: JTAG
Target interface speed: 4000kHz
Target endian: little
Connecting to J-Link...
JLinkGUIServerExe: cannot connect to X server
Connecting to J-Link failed. Connected correctly?
GDBServer will be closed...
Shutting down...
Could not connect to J-Link.
Please check power, connection and settings.
I also shared these details with Segger experts, who told me:
According to the J-Link Commander output, not even the connect works as expected.
The iMX8 is a quite complex device where usually a Linux is booted. From similar cases
in the past, I can tell you that in >90 % of such cases, the Linux was identified by the
user as root cause. Usually the it disables debug pins / debug clocks / debug unit / etc…
If this is the case, the output looks similar to the one shared with us.
Please understand that we cannot see any problems on J-Link side here.
I am pretty sure that the root cause of the failed connect is no misbehavior
of the J-Link but the current state of the MCU (debug connection not possible).
Best regards,
Mehrdad