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

[AndyM]

I installed the nRF Connect extension pack which also contains the nRF Terminal extension but I cannot make it work in VS Code

In the command pallette I select  nRF Terminal:Start Terminal, specify RTT as a connect method and hit Enter when prompted for device name, serial number and memory address.

There is a message "nRF terminal trying to connect" at the bottom of the VS Code window but it  never succeeds. I verified that the board is connected with JLink , the code is running and I can see output is printed in the JLink RTT Viewer 

Tried to send nRF:clear  but that did not help

Any ideas how to fix?

Thank you

Andy

[Chris]

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.

[AndyM]

glad I'm not alone

[Susheel Nuguru]

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.

[Chris]

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

[Susheel Nuguru]

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

[Susheel Nuguru]

1. 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.
   
   
   
2. 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

[Chris]

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?

[Chris]

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.

[Chris]

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

[AndyM]

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

[Susheel Nuguru]

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.