Hello,
I am unable to use the Segger RTT terminal built into the nRF Connect SDK for VSCode Extension pack with the nRF54L15DK.
I have configured my project with the following configuration to log via RTT:
CONFIG_LOG=y CONFIG_UART_CONSOLE=n CONFIG_USE_SEGGER_RTT=y CONFIG_RTT_CONSOLE=y CONFIG_LOG_BACKEND_RTT=y
When I connect an RTT terminal in VSCode through the "Connected Devices" list, only the following text appears, and no output is produced:
SEGGER J-Link V8.22 - Real time terminal output SEGGER J-Link (unknown) V1.0, SN=1057777546 Process: JLinkExe
Looking at the running processes while the terminal is open, I can see that the Extension runs the JLink Program as
/opt/SEGGER/JLink/JLinkExe -device NRF54L15_xxAA -SelectEmuBySN <serial number> -if swd -speed auto -AutoConnect 1 -RTTTelnetPort 35315
If I run this manually in a terminal, I get the following output:
SEGGER J-Link Commander V8.22 (Compiled Mar 19 2025 15:52:30) DLL version V8.22, compiled Mar 19 2025 15:51:26 Connecting to J-Link via USB...O.K. Firmware: J-Link OB-nRF5340-NordicSemi compiled Feb 11 2025 17:15:35 Hardware version: V1.00 J-Link uptime (since boot): 0d 00h 53m 22s S/N: <serial number> License(s): RDI, FlashBP, FlashDL, JFlash, GDB USB speed mode: Full speed (12 MBit/s) VTref=3.300V The selected device "NRF54L15_xxAA" is unknown to this software version.
And a window opens prompting me to select a known device. If I manually open a telnet connection, I get the same output as in VSCode.
If I then select the nRF54L15_M33 device, or set the correct device (`-device NRF54L15_M33`) when launching the program, I can successfully receive the logs printed via RTT via the telnet connection.
Is this simply a bug in the VSCode extension, and is there a workaround I can apply so I can use the integrated VSCode terminal?
I am using the nRF Connect SDK v2.9.0, JLink V8.22, nrfutil 7.12.0 and the latest nRF Connect SDK VSCode extension pack inside an Ubuntu 22.04 container using the "Dev Containers"
VSCode addon.
Thanks!