Difference between revisions of "Remote Debugging with Ozone"
(→Remote Debugging Over The Internet) |
(→Remote Debugging Over The Internet) |
||
Line 22: | Line 22: | ||
expects a tunnel server credential of the form: |
expects a tunnel server credential of the form: |
||
− | <code> |
+ | <code>tunnel:<Probe>[:<Password>[:<Server>]]</code> |
where: |
where: |
||
Line 29: | Line 29: | ||
| Argument |
| Argument |
||
| Description |
| Description |
||
− | |- |
||
− | | IP |
||
− | | IP address of the remote server |
||
|- |
|- |
||
| Probe |
| Probe |
||
Line 43: | Line 40: | ||
|} |
|} |
||
− | The short credential variant <code> |
+ | The short credential variant <code>tunnel:<Probe></code> 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. |
<b>Examples</b> |
<b>Examples</b> |
||
Line 51: | Line 48: | ||
| Description |
| Description |
||
|- |
|- |
||
− | | |
+ | | tunnel:932000000:MyPassword123:jlink2.segger.com |
| J-Link was registered by S/N, with a password, at jlink2.segger.com |
| J-Link was registered by S/N, with a password, at jlink2.segger.com |
||
|- |
|- |
||
− | | |
+ | | tunnel:MyJLink::jlink2.segger.com |
| J-Link was registered by Name, without a password, at jlink2.segger.com |
| J-Link was registered by Name, without a password, at jlink2.segger.com |
||
|- |
|- |
||
− | | |
+ | | tunnel:600100000:MyPassword123 |
| J-Link was registered by S/N, with a password, at the SEGGER default tunnel server |
| J-Link was registered by S/N, with a password, at the SEGGER default tunnel server |
||
|} |
|} |
Revision as of 23:58, 15 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 Ozone menu path 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.
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:
tunnel:<Probe>[:<Password>[:<Server>]]
where:
Argument | Description |
Probe | Either the serial number or nickname of the J-Link / J-Trace to connect to |
Password | Password that was used when the J-Link / J-Trace debug probe was registered with the Remote Server |
Server | Address or hostname of the tunnel server. For use when a tunnel server other than the SEGGER default tunnel server (jlink.segger.com, port 19020) is used. |
The short credential variant tunnel:<Probe>
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.
Examples
Input | Description |
tunnel:932000000:MyPassword123:jlink2.segger.com | J-Link was registered by S/N, with a password, at jlink2.segger.com |
tunnel:MyJLink::jlink2.segger.com | J-Link was registered by Name, without a password, at jlink2.segger.com |
tunnel:600100000:MyPassword123 | J-Link was registered by S/N, with a password, at the SEGGER default tunnel server |
References
- J-Link Remote Server on SEGGER.com
- J-Link Remote Server on SEGGER wiki
- J-Link / J-Trace user guide
- Ozone user guide