TCP / RTT

Open a raw TCP connection in a tab: SEGGER RTT from a J-Link or OpenOCD RTT server, or any device stream on a TCP port. The tab works like a serial console for a device log.

Open a TCP / RTT tab

  1. Choose New Session → TCP / RTT.
  2. Pick a Preset. It fills in the host and port, which you can change.
  3. Click Connect. The tab is named after the endpoint, for example RTT 127.0.0.1:19021.
PresetFills inBefore you connect
J-Link RTT127.0.0.1, port 19021J-Link Commander, GDB Server or RTT Viewer serves RTT on this port while it is connected to the target.
OpenOCD RTT127.0.0.1, port 9090Start the server in OpenOCD first.
Customnothing: no default host or portEnter the host and port of any raw TCP stream.

OpenOCD RTT

In OpenOCD, start the RTT server with rtt server start 9090 0, then connect the tab with the OpenOCD RTT preset on port 9090.

Custom raw TCP

Custom has no default port: enter the host and port yourself. Use it for any device stream on a TCP socket, for example QEMU serial over TCP.

Advanced settings

  • Config string: sent first after every connect. Empty sends nothing. The example in the field is a SEGGER J-Link config string.
  • Connect timeout: 500 to 60000 ms, 5 s by default.
  • Local Echo, for a target that does not echo what you type.

How the tab behaves

Bytes pass through unchanged in both directions; there is no telnet negotiation. Pattern markers, the filter, logging and saved profiles work as in a serial tab.

When the server goes away, the tab tries to reconnect a few times and then stops; Retry starts again. A tab you disconnect stays disconnected, and NeuroTerm does not connect TCP tabs by itself at startup.

With Terminal Use set up, Claude Code or Codex can read a TCP tab and, when you allow it, type into it.