• State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 74 subscribers
  • Views 1167 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 276389
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

"Paths" Issue with nRF Connect for Visual Studio Code Preview

ayavilevich

Hi,

I am trying the new nRF connect extension for VSC. Great direction. Hope it takes off.

For those interested, the announcement and details are at: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/nrf-connect-for-visual-studio-code-preview

I have encountered an issue. After installing the extension, my "path" environment in VSC got few additional folders at the top. Specifically:

[...]\v1.6.1\toolchain\mingw64\bin
[...]\v1.6.1\toolchain\mingw64\libexec\git-core
[...]\v1.6.1\toolchain\opt\bin
[...]\v1.6.1\toolchain\opt\bin\Scripts

Now since opt\bin contains Python 3.8 and since I am using Python 3.9 in my environment otherwise, there is a conflict. Other extensions got broken (i.e. PlatformIO) and I am now forced to use python 3.8 by default in the terminal.

This seems to be an non optimal way to implement this. Perhaps this change can be restricted only to nRF connect projects and not be a VCS wide change. Perhaps you can use full paths for the toolchain. Alternatively, I have seen some other toolchain requiring to run VSC from special terminal, presumably with custom environment variables set first. FYI.

For now I have to disable the extension and restart VSC if I want to work on another platform.

  • +1

    Hi ayavilevich,

    Please try to uncheck the following settings located on Settings->User->Extensions->nRF Connect-> Terminal Evn

    We also recommend disables the extension in the workspace where you don't use it. I don't see the reason to have both nRF Connect and PlatformIO be active in the same environment.

    Really thanks for your feedback, our development team is also working on the terminal settings to further improve the user experience in the near future.

    Best regards,

    Charlie

Related
Terms of service