nRF Connect and nRF Terminal profiles

nRF Connect for VS Code

tags
nRF Connect for VS Code

The extension comes with several extension-specific actions that are available from the Launch Profile... drop-down list (the arrow next to the plus sign icon) located in the Panel Toolbar area.

RTT and serial terminal actions

The following extension-specific actions are available:

Action Description
nRF Connect Opens an nRF Connect terminal profile that is configured to work with west and the last used versions of the nRF Connect Toolchain and the nRF Connect SDK.

The terminal name lists the SDK icon SDK and the Toolchain icon toolchain versions used by the terminal, which depend on where you start the terminal from. For example, on the following image:
nRF Connect terminal profile examples
- The terminal for the dac context is using the SDK icon SDK and Toolchain icon toolchain v3.2.1.
- The terminal for the hello_world context is using the SDK icon SDK v3.1.0 and the Toolchain icon toolchain v3.1.1.

If you opened the terminal from Manage SDKs > Open terminal profile and skipped the selection of the SDK, the terminal only uses the Toolchain icon toolchain, like on the following image:
nRF Connect terminal profile with only a toolchain

See How to use nRF Connect terminal profile for more information.
nRF RTT Terminal Establishes a connection to the board through RTT if it is supported on the selected device. Selecting this option frees a UART port that the serial port would use. However, you always need a SEGGER J-Link debugger connected for RTT to work.
nRF Serial Terminal Establishes a connection to the board through the serial port if it is supported on the selected device.

The RTT and serial connection actions correspond to the actions available from Connected Devices View and described in the How to connect to a device section. You can also start them from the Command Palette using nRF Terminal commands.

Tip

If you lose your serial connection, for example when your device loses power, the connection is automatically restored when the cause of the interruption is resolved, as long as you do not close the connection window.

This functionality is not available for the RTT terminal, which has to be reconnected manually.