Difference between revisions of "Remote Debugging with Ozone"

From SEGGER Wiki
Jump to: navigation, search
Line 8: Line 8:
 
When the remote PC is on the same LAN as the PC hosting Ozone (host PC), it suffices to
 
When the remote PC is on the same LAN as the PC hosting Ozone (host PC), it suffices to
 
start a [[#https://www.segger.com/products/debug-probes/j-link/tools/j-link-remote-server/|J-Link Remote Server]] on the remote PC and supply the IP address of the remote server
 
start a [[#https://www.segger.com/products/debug-probes/j-link/tools/j-link-remote-server/|J-Link Remote Server]] on the remote PC and supply the IP address of the remote server
within Ozone's J-Link Settings Dialog. J-Link Remote Server V6.53b and later also supports encrypted
+
within Ozone's Host Interface Dialog. The Host Interface Dialog is accessible via <code>Tools->J-Link Settings->Host Interface</code>. J-Link Remote Server V6.53b and later also supports encrypted
 
connections.
 
connections.
   
Line 19: Line 19:
 
[[File:JLinkTunnelServer.png|none|J-Link Remote Server in tunnel mode.]]
 
[[File:JLinkTunnelServer.png|none|J-Link Remote Server in tunnel mode.]]
   
For remote debugging via the J-Link Tunnel Server, the IP address field of Ozone's host interface dialog
+
For remote debugging via the J-Link Tunnel Server, the IP address field of Ozone's Host Interface Dialog
 
expects a tunnel server credential of the form:
 
expects a tunnel server credential of the form:
   

Revision as of 11:38, 3 March 2020

Overview

Ozone can connect to a remote J-Link/J-Trace debug probe in order to debug on a remote target. When debugging remotely, the J-Link/J-Trace debug probe is connected to a remote PC via the Ethernet host interface.

Remote Debugging Over LAN

When the remote PC is on the same LAN as the PC hosting Ozone (host PC), it suffices to start a J-Link Remote Server on the remote PC and supply the IP address of the remote server within Ozone's Host Interface Dialog. The Host Interface Dialog is accessible via Tools->J-Link Settings->Host Interface. J-Link Remote Server V6.53b and later also supports encrypted connections.

Remote Debugging Over The Internet

When the remote PC is not on the same LAN as the host PC, an intermediary tunnel server at SEGGER can be used to be mediate a connection for remote debugging. Both Ozone and the J-Link Remote Server then connect to this tunnel server instead of connecting to each other directly.

J-Link Remote Server in tunnel mode.

For remote debugging via the J-Link Tunnel Server, the IP address field of Ozone's Host Interface Dialog expects a tunnel server credential of the form:

IP tunnel:<SN/Name>[:<Password>[:<TunnelServer>]]

where:

Argument Description
IP IP address of the remote server
SN/Name Either the serial number or nickname of the J-Link / J-Trace to connect to
Password Password that was used when setting up the Remote Server
TunnelServer Address or hostname of the tunnel server. This is only needed if a tunnel server other than the SEGGER default tunnel server (jlink.segger.com, port 19020) is used.

The short credential variant IP tunnel:<SN/Name> can be used when the connection is to be established to the default J-Link Tunnel Server and is not passwort-protected. When debugging via the tunnel server, make sure that port 19020 is not blocked by a firewall.

References