Hi,
I've seen that this problem was solved for Windows users in 6.22e, but under Linux x86 is still exists:
aystarik@mint /opt/SEGGER/JLink_V630 $ ./JLinkGDBServerCLExe -device MCIMX6G2 -scriptfile /home/aystarik/SDK_2.2_MCIM6UL/boards/evkmcimx6ul/demo_apps/hello_world/ddr_init.jlinkscript
I've seen that this problem was solved for Windows users in 6.22e, but under Linux x86 is still exists:
aystarik@mint /opt/SEGGER/JLink_V630 $ ./JLinkGDBServerCLExe -device MCIMX6G2 -scriptfile /home/aystarik/SDK_2.2_MCIM6UL/boards/evkmcimx6ul/demo_apps/hello_world/ddr_init.jlinkscript
rolled back to v6.20i and it works fine:
SEGGER J-Link GDB Server V6.30 Command Line Version
JLinkARM.dll V6.30 (DLL compiled Jan 30 2018 18:46:34)
Command line: -device MCIMX6G2 -scriptfile /home/aystarik/SDK_2.2_MCIM6UL/boards/evkmcimx6ul/demo_apps/hello_world/ddr_init.jlinkscript
-----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: /home/aystarik/SDK_2.2_MCIM6UL/boards/evkmcimx6ul/demo_apps/hello_world/ddr_init.jlinkscript
J-Link settings file: none
------Target related settings------
Target device: MCIMX6G2
Target interface: JTAG
Target interface speed: 4000kHz
Target endian: little
Connecting to J-Link...
J-Link is connected.
Firmware: J-Link V10 compiled Jan 29 2018 15:41:33
Hardware: V10.10
S/N: 600105924
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
Checking target voltage...
Target voltage: 3.35 V
Listening on TCP/IP port 2331
Connecting to target...WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
ERROR: Cortex-A/R-JTAG (connect): Could not determine address of core debug registers. Incorrect CoreSight ROM table in device?
ERROR: Could not connect to target.
Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...
Shutting down...
Could not connect to target.
Please check power, connection and settings.aystarik@mint /opt/SEGGER/JLink_V630 $
aystarik@mint /opt/SEGGER/JLink_V620i $ ./JLinkGDBServer -device MCIMX6G2 -scriptfile /home/aystarik/SDK_2.2_MCIM6UL/boards/evkmcimx6ul/demo_apps/hello_world/ddr_init.jlinkscript
SEGGER J-Link GDB Server V6.20i Command Line Version
JLinkARM.dll V6.20i (DLL compiled Nov 17 2017 17:33:15)
Command line: -device MCIMX6G2 -scriptfile /home/aystarik/SDK_2.2_MCIM6UL/boards/evkmcimx6ul/demo_apps/hello_world/ddr_init.jlinkscript
-----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: /home/aystarik/SDK_2.2_MCIM6UL/boards/evkmcimx6ul/demo_apps/hello_world/ddr_init.jlinkscript
J-Link settings file: none
------Target related settings------
Target device: MCIMX6G2
Target interface: JTAG
Target interface speed: 1000kHz
Target endian: little
Connecting to J-Link...
J-Link is connected.
Firmware: J-Link V10 compiled Jan 29 2018 15:41:33
Hardware: V10.10
S/N: 600105924
Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB
Checking target voltage...
Target voltage: 3.35 V
Listening on TCP/IP port 2331
Connecting to target...WARNING: At least one of the connected devices is not JTAG compliant (IEEE Std 1149.1, 7.1.1.d, IR-cells). (NumDevices = 3, NumBitsSet = 2)
J-Link found 3 JTAG devices, Total IRLen = 13
JTAG ID: 0x5BA00477 (Cortex-A7)
Connected to target
Waiting for GDB connection...