Skip to content

Troubleshooting

Failed to resolve the nRF Connect SDK path

This issue appears when the extension cannot find the correct version of the nRF Connect SDK on the disk assigned in the current extension settings. This can happen if the SDK was removed from the disk or a different version or tag was checked out by Git in that repository. Either update the settings or ensure that the SDK is correctly installed.

To check which version is installed:

  1. Run the nRF Connect: Generate Support Information command.
  2. In the OUTPUT panel you will find the list of SDKs under the sdks key. To check out the correct version, follow the instructions in Updating the repositories.
  3. After correcting the issue, restart VS Code.

Failed to resolve the nRF Connect Toolchain path

This issue appears when the extension cannot find the correct version of the nRF Connect Toolchain on the disk assigned in the current extension settings. Either update the settings or ensure that the SDK is correctly installed.

To check which version is installed:

  1. Run the nRF Connect: Generate Support Information command.
  2. In the OUTPUT panel you will find the list of toolchains under the toolchains key.
  3. After correcting the issue, restart VS Code.

Shell initialization conflicts nRF Connect terminal profile

This issue may occur when opening the internal terminal with the nRF Connect profile, which sets the shell environment for the configured SDK and toolchain, but the shell initialization script (e.g. .bashrc) overrides the environment. This can happen if the ZEPHYR_BASE environment variable is set in .bashrc. If there is no need for external terminals to use this variable, we suggest removing this from .bashrc, otherwise it can be moved to .bash_profile or an equivalent script that is only loaded by login shells.

Back to top