nrf connect terminal open failed when option follow nRF Connect SDK Intermediate less1 exer1

[Chaoyue Ying]

When I follow exercise steps A to open nRF connect terminal,vs code will display issue as follow:

Whether some issues happened when I get nrf connect SDK?

How can I repair it?

[Hieu]

Hi Chaoyue Ying,

Could you please get the log from VS Code's Developer Console when this happen?

You can get to the console at Help > Toggle Developer Tools > Console.

Hieu

[Chaoyue Ying]

Hi,

The log from Developer Console is follow:

It just the message after I click nRF Connect.

I find other errors happened before it ,if you need,I will get more details to you

[Hieu]

I found that you can actually select a line, Ctrl+A, Ctrl+C to copy all the logs, and then pasted into a text file. Could you do that please?

[Chaoyue Ying]

Fullscreen 5861.error.txt Download

No terminal profile provider registered for id "nrf-connect.ncs_terminal"
c @ workbench.desktop.main.js:747
(anonymous) @ workbench.desktop.main.js:747
invoke @ workbench.desktop.main.js:86
deliver @ workbench.desktop.main.js:86
fire @ workbench.desktop.main.js:86
addNotification @ workbench.desktop.main.js:747
error @ workbench.desktop.main.js:1671
createContributedTerminalProfile @ workbench.desktop.main.js:2628
await in createContributedTerminalProfile (async)
createTerminal @ workbench.desktop.main.js:2628
await in createTerminal (async)
(anonymous) @ workbench.desktop.main.js:1200
run @ workbench.desktop.main.js:86
runAction @ workbench.desktop.main.js:86
run @ workbench.desktop.main.js:86
onClick @ workbench.desktop.main.js:182
(anonymous) @ workbench.desktop.main.js:182
setTimeout (async)
(anonymous) @ workbench.desktop.main.js:182

[Hieu]

Oh OK, there isn't much other information compared to the screenshot, unfortunately.

Could it be that you tried to open a terminal with nRF Connect terminal profile?

Perhaps you have this profile set as default and when VSCode starts the extension is not ready yet?  It would be great to know when this happens.

Does it happen consistently or just scarcely?

[Chaoyue Ying]

It will happen until open a nrf conneect sdk project folder.

[Hieu]

This is tricky because none of us have encountered this issue before, and we also cannot reproduce it at all.

Does it happen again after you have successfully used the extension once?

As in, after you open the SDK installation, and compile a sample there, would it start working properly from then on?

Also, which terminal profile are you configuring as the default for VS Code?