• State Not Answered
  • Replies 6 replies
  • Subscribers 65 subscribers
  • Views 133 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 328438
Options

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?

  • 0

    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

  • 0 in reply to Hieu

    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

  • 0 in reply to Chaoyue Ying

    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?

  • 0 in reply to Hieu

    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

  • 0 in reply to Chaoyue Ying

    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?

Related