µVISION DEBUGGER: J-Link remote debugging support in MDK

Information in this knowledgebase article applies to:

• MDK v5.x
• Segger J-Link debug adapters

QUESTION

Segger J-Link debug adapters support remote debugging. In MDK µVision I can remotely connect my J-Link debugger in the LAN mode, which works fine. However, in MDK µVision I cannot remotely connect my J-Link debugger in the tunnel mode via the Segger Tunnel Server. An error "Cannot connect to J-Link via TCP/IP" is shown up in MDK µVision.

ANSWER

Segger J-Link debuggers support three debug mode:

• Direct Mode
• LAN Mode
• Tunnel Mode

More details about these three debug modes can be found on the Segger website.

So far in MDK µVision only the direct mode and the LAN mode of J-Link debuggers are supported. In order to remotely connect a J-Link debugger via the Tunnel mode, the following J-Link command line needs to be called:

ip tunnel: Name/SN

However, so far in MDK µVision debugger settings for J-Link, only IP address and port number of the remote node with a J-Link debugger can be specify, as shown in the following figure:

Since the J-Link debugger driver and DLLs used for debugger settings in MDK µVision are provided by Segger directly, we will keep this article updated, when the support for Tunnel Mode debugging is implemented into future release of MDK.

MORE INFORMATION

• Refer to Interface and TCP/IP in the J-Link/J-Trace User's Guide.

Last Reviewed: Wednesday, August 14, 2019