Hello everyone,
we have just updated to a new JLink in order to program/debug an i.MX7D device.
For a test, I wanted to connect to NXP demo board (MX7 Sabre).
I tried connecting to the A7 using JLink.exe, but get the result listed below (see line 17).
As suggested in other threads, the JTAG clock speed has been limited to <400 KHz. The target board is powered (JLINK detects 3,3V).
The scripts for connecting to the cores were mentioned in the other threads as well. Based on the console output below I assume these do not have to be called/setup manually.
Display All
Using the JlinkGDBserver through thw win10 command line gives the folowing (same) output, with no mentioning of the connect scripts, resulting in the same error:
Display All
I had the same problem before with a hand soldered adaptor 20 pin arm JTAG to 10 pin arm JTAG with lots of air-wires and assumed there might be something wrong with the adaptor. Bought an olimex 20->10 pin adaptor that I am using now.
If i try the same using the M4, it says "CPU_TAP not found in JTAG Chain" instead (probably cause it needs to be booted by the A7 first).
So my questions are:
we have just updated to a new JLink in order to program/debug an i.MX7D device.
For a test, I wanted to connect to NXP demo board (MX7 Sabre).
I tried connecting to the A7 using JLink.exe, but get the result listed below (see line 17).
As suggested in other threads, the JTAG clock speed has been limited to <400 KHz. The target board is powered (JLINK detects 3,3V).
The scripts for connecting to the cores were mentioned in the other threads as well. Based on the console output below I assume these do not have to be called/setup manually.
C Source Code
- J-Link>connect
- Device "MCIMX7D7_A7_0" selected.
- Connecting to target via JTAG
- ***************************************************
- J-Link script: iMX7D Cortex-A7_0 core J-Link script
- ***************************************************
- TotalIRLen = 5, IRPrint = 0x01J
- TAG chain detection found 1 devices: #0 Id: 0x088E001D, IRLen: 04, JTAG-DP
- ***************************************************
- J-Link script: iMX7D Cortex-A7_0 core J-Link script
- ***************************************************
- TotalIRLen = 5, IRPrint = 0x01J
- TAG chain detection found 1 devices:
- #0 Id: 0x088E001D, IRLen: 04, JTAG-DP
- ****** Error: JTAG Id mismatch. TAP with Id 0x00000000 is no JTAG-DP
- ***************************************************
- J-Link script: iMX7D Cortex-A7_0 core J-Link script
- ***************************************************
- TotalIRLen = 5, IRPrint = 0x01JTAG chain detection found 1 devices:
- #0 Id: 0x088E001D, IRLen: 04, JTAG-DP
- ***************************************************
- J-Link script: iMX7D Cortex-A7_0 core J-Link script
- ***************************************************
- TotalIRLen = 5, IRPrint = 0x01JTAG chain detection found 1 devices:
- #0 Id: 0x088E001D, IRLen: 04, JTAG-DPCannot connect to target.
- J-Link>
Using the JlinkGDBserver through thw win10 command line gives the folowing (same) output, with no mentioning of the connect scripts, resulting in the same error:
C Source Code
- C:\Program Files (x86)\SEGGER\JLink_V622g>JLinkGDBServerCL.exe -device MCIMX7D7_M4 -speed 300 -select USB
- SEGGER J-Link GDB Server V6.22g Command Line Version
- JLinkARM.dll V6.22g (DLL compiled Jan 17 2018 16:39:42)
- Command line: -device MCIMX7D7_A7_0 -speed 300 -select USB
- -----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: localhost only
- 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: USBJ-Link
- script: none
- J-Link settings file: none
- ------Target related settings------
- Target device: MCIMX7D7_A7_0
- Target interface: JTAG
- Target interface speed: 300kHz
- Target endian: little
- Connecting to J-Link...
- J-Link is connected.
- Firmware: J-Link V10 compiled Jan 11 2018 10:41:05
- Hardware: V10.10
- S/N: 50117772
- Feature(s): GDB
- Checking target voltage...Target voltage: 3.32 V
- Listening on TCP/IP port 2331
- Connecting to target...ERROR: JTAG Id mismatch. TAP with Id 0x00000000 is no JTAG-DP
- 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.
I had the same problem before with a hand soldered adaptor 20 pin arm JTAG to 10 pin arm JTAG with lots of air-wires and assumed there might be something wrong with the adaptor. Bought an olimex 20->10 pin adaptor that I am using now.
If i try the same using the M4, it says "CPU_TAP not found in JTAG Chain" instead (probably cause it needs to be booted by the A7 first).
So my questions are:
- Connect sequence must be A7_0, A7_1, M4 with no deviation allowed?
- Do I need to setup/provide/link the connect scripts somehow?
- What might cause the 0x00000000 TAP ID readout (ARM 10 pin - olimex 10-20 adaptor - JLINK)?
- "JTAG Device not found" is caused by trying to connect to the M4 before the A7 are running?
- Am I missing anything?