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

"Couldn't find Zephyr root" both SEGGER and VsCode

Hello all,

Lost my VM that had a working installation and just setting everything back up.

After installing SDK 1.8.0 and all of the extensions for VsCode. Now both SEGGER and VSCode cannoot find the Zephry root and I cannot find it on disk?

This was not a problem in the past, any ideas?

Thanks

Edit: Another problem... like all of the examples are missing?? searched for serial_lte_modem and it comes up with nothing. Even just searching serial, or application comes up with nothing useful?

Edit2: I installed the most recent 3 releases and none have a zephyr folder anymore?!?!?

Parents
  • Hello Kyle,

    There should be a Z:\ncs\v1.8.0\zephyr, which is the mentioned Zephyr root. Probably, the installation of NCS didn’t finish successfully.

    Please remove this installation completely and try it one more time. An active VPN connection or firewall could possibly block the necessary downloads from GitHub (which is why I assume that applications like e.g. the Serial LTE modem are missing). Additionally, my personal recommendation would be to stick with the default installation path.

    Regards,

    Markus

Reply
  • Hello Kyle,

    There should be a Z:\ncs\v1.8.0\zephyr, which is the mentioned Zephyr root. Probably, the installation of NCS didn’t finish successfully.

    Please remove this installation completely and try it one more time. An active VPN connection or firewall could possibly block the necessary downloads from GitHub (which is why I assume that applications like e.g. the Serial LTE modem are missing). Additionally, my personal recommendation would be to stick with the default installation path.

    Regards,

    Markus

Children
  • I will try fully uninstalling everything

    I am not using any VPN, SDK is running in a VM with a shared network drive

    I had all sorts of issues with the default installation path last time because the path length would get too long for windows command line.

    I will try locally as well just in case, but even if its the network share problem; that's a bug that probably should be corrected?

Related