Home/Support/Support Forum/JTAG LINK cannot connect with Digi Connect ME
New and improved user forum site coming soon
Welcome to Digi Forum, where you can ask questions and receive answers from other members of the community.

JTAG LINK cannot connect with Digi Connect ME

0 votes
I used the Digi ESP for Net+OS Version 2.0.0 to implement a custom application based on the Net+OS 7.3 for the Digi Connect ME module. I haven't used for a while. Recently I am facing an issue, which the ESP IDE cannot connect with the Digi Connect ME module with JTAG interface on a development board. The SEGGER J-LINK GDB Server log window always show "WARNING: RESET (pin 15) high, but should be low. Please check target hardware", "ERROR: JTAG Timeout during adaptive clocking: RTCK did not respond. Could not find supported CPU core on JTAG chain". I don't know where the issue come from. ESP IDE, JTAG LINK, development board, or module itself? I used the set to develop firmware before. Please let me know if you have any recommendation. Thanks!

The following is the screen capture:
J-Link connected
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware: V8.00
S/N: 38001159
OEM: DIGI-LINK
Feature(s): GDB

Resetting target using BP@0 and trying again to connect...
WARNING: No matching core found. Selecting default core (ARM7).
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
WARNING: Received 0 as core Id.
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
WARNING: RESET (pin 15) high, but should be low. Please check target hardware.
WARNING: Received 0 as core Id.
ERROR: JTAG Timeout during adaptive clocking: RTCK did not respond.
Could not find supported CPU core on JTAG chain

ERROR: Could not connect to target.

J-Link connected
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware: V8.00
S/N: 38001159
OEM: DIGI-LINK
Feature(s): GDB
asked Apr 4 in NET+OS by pshih New to the Community (1 point)

Please log in or register to answer this question.

1 Answer

0 votes
are you using a development board? Are you sure your module has JTAG? production ME modules do not have JTAG populated.
answered Apr 11 by LeonidM Veteran of the Digi Community (4,490 points)
...