nRF Terminal extension in VS Code fails to connect in RTT mode

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

spring.liu — Wed, 06 Jul 2022 02:13:15 GMT

how to configuration the "device" "serial number" "memory address"

"NFR52840_XXAA" what should i put in "serial number" "memory address"?

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Fri, 25 Mar 2022 12:13:12 GMT

This is what i get when i do not change the DK to another and press the connect to RTT without pressing the refresh view.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Chris — Wed, 23 Mar 2022 16:55:49 GMT

I deleted the build folder then opened VSC and created a new build. The only difference I see is now when I run a debug session I get the word "Disconnected" repeated 5 times in the NRF Terminal.

At least I'm seeing something in the NRF Terminal now, maybe it means we are getting closer to a solution.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Wed, 23 Mar 2022 10:48:55 GMT

exit the VSC, delete the build folder and open VSC again for that project and try so that all references to underlying command tools are done from the latest version. Also uninstall older command line tools.
I have tried to install older version of the command line tools but not able to reproduce that unfortunately. I am not sure what else might be different in our setups.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

AndyM — Tue, 22 Mar 2022 20:25:13 GMT

Confirming that behavior. I'm on Windows 10 as well

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Chris — Tue, 22 Mar 2022 19:11:20 GMT

Some additional information:

When attempting to Debug my project with logs I see a "Debug Console" a "Terminal" and the "NRF Terminal"

Under the Debug Console I see information about symbols being read and launching of GDB and gdb-server. It gives me information about the threads being created and finally ends by telling me the temporary breakpoint at main has been reached.

Under Terminal I see the GDB server and a J-Link connection. It looks to give information about programming the device and then reading some memory locations. It informs me the CPU is starting and reading registers.

The NRF Terminal is always blank

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Chris — Tue, 22 Mar 2022 17:47:15 GMT

I manually installed the latest nRF-Command-Line-Tools (V 10.15.4)

When I click "Connect to RTT" under connected devices VS Code now doesn't ask me for the device. I select "Automatic search" but the end result is the same. I still see "nRF Terminal Trying to Reconnect...." and none of my logs are shown on the "NRF TERMINAL"

Connecting via J-Link still works.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Chris — Tue, 22 Mar 2022 17:22:51 GMT

Thanks for the response Susheel!

1. Yes, I have refreshed the list and the problem remains.

2. Where is VS Code expecting nrjfprog to be installed? The only reference to nrfjprog I could find on my machine was in "C:\NCS\v1.9.1\zephyr\scripts\west_commands\tests" Would the latest nRF-Command-Line-Tools be installed when I used the nRF Tool Chain Manager?

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Tue, 22 Mar 2022 08:45:11 GMT

Please check if you have refreshed the list of the connected device before you try to connect to RTT. Our developers believe that if something has changed in terms of connection, then it is not automatically updated in terms of device info indexing.
the device details is populated with the --deviceversion flag for nrfjprog, which was added in nRF-Command-Line-Tools v10.8.0. Any earlier versions will fail to populate this view

We do not know anything else that might affect this behavior

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Mon, 21 Mar 2022 11:45:11 GMT

Chris,
I need to be able to reproduce it first to be able to get more help from the team. I am using PCA10040V2.1.0 and also tried it with v1.0.1 and not able to reproduce this behavior

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Chris — Thu, 17 Mar 2022 16:00:48 GMT

Thank you. Is there any additional information I can provide to help you solve this?

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Thu, 17 Mar 2022 09:38:25 GMT

OK, since this is reproducible by two, I will create an internal ticket for the team to investigate. I still cannot reproduce it at my end, but hopefully the team will dig into it.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

AndyM — Tue, 15 Mar 2022 23:17:02 GMT

glad I'm not alone 🙂

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Chris — Tue, 15 Mar 2022 22:57:45 GMT

I am having this same issue. I can get logging out using J-Link RTT Viewer V7.62b but no luck with the nRF Terminal in VS Code. The status bar just says "nRF Terminal Trying to Reconnect...."

I am using a Nordic nRF52832 DK. (PCA10040 V1.2.4)

Under the "Connected Devices" I see my dev kit's serial number but when I expand the device I don't see any of the board information or COM ports like shown in the walkthrough.

When I click the "Connect To RTT In nRF Terminal" button next to my serial number it asks for the device. I type in NRF52832_XXAA and select "Automatic search" for the memory address and nothing happens.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

tellg — Tue, 15 Mar 2022 22:41:29 GMT

I have the same problem. Had to use Ozone instead.

ncs 1.9.1

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

AndyM — Tue, 15 Mar 2022 16:18:34 GMT

I tried that and also tried leaving all fields empty - no luck. As for serial number - no idea where to find it - this is a custom board - so I typed 1234 - made no difference.
Confirming, the board communicates just fine with JLink RTT viewer and Segger Embedded Studio. I'm on Windows 10.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Tue, 15 Mar 2022 08:21:49 GMT

What is the device name you are giving? for me for nRf52840 DK, I give NRF52840_XXAA and it works fine after giving the serial number.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Tue, 15 Mar 2022 06:40:57 GMT

I have tried to test this with multiple DKs and am not able to reproduce it. Unable to find any communication within support where this is being discussed. So I am assuming this is something to do with the custom board. The nRF Terminal uses JLink in the background, so I am a bit confused as to why this is works with JLink on command prompt and not with this process. I will try to ask the VCS team to know if they have seen this before and for any directions to proceed from here.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

AndyM — Mon, 14 Mar 2022 14:07:42 GMT

I'm on Windows and have a custom board. Connection to the board via JLink works fine with Segger Embedded Studio and standalone ( Commander, RTT viewer ) but does not work in VScode. You don't need a project - nRF Terminal extension keeps "trying to connect" but never succeeds.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Mon, 14 Mar 2022 07:48:44 GMT

which OS are you using? Windows/Linux?
Can you give me your project zipped so that I can do a quick smoke test on my desk?

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

AndyM — Fri, 11 Mar 2022 14:39:02 GMT

No other emulators are running. Memory address selection is set to auto.

RE: nRF Terminal extension in VS Code fails to connect in RTT mode

Susheel Nuguru — Fri, 11 Mar 2022 11:51:35 GMT

can you set the memory address to auto and see if that works?

I am not able to reproduce that with latest VSC and latest nRF terminal extension. probably there is some other emulator listening to your COM/RTT port?