• State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 25 subscribers
  • Views 405 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 285102
Options
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

nRF Connect SDK 1.9.0 Segger Embedded Studio

user67640

After installing NCS 1.9.0 Open Segger Embedded Studio does not show as an option any longer. I have tried to remove the SDK and install it again, but the result is the same. Our customer does not want us to migrate to VS Code right now. How can i get Segger Embedded Studio back?

Kind regards

Dirk

  • 0

    Hello Dirk,

    the installation of the nRF Connect SDK probably didn’t finish successfully. Does the customer use an open VPN connection or a firewall that might block the repository downloads from GitHub?

    Anyway, your customer could try this. When opening a bash, the following message should appear:

    NCS repositories are not yet cloned here. To do so run the following command:

ncsmgr init-ncs

user@user MINGW64 ~/ncs/v1.8.0
$

    By running this command, the GitHub repositories should be downloaded and thus finish the installation.

    Regards

    Markus

  • 0 in reply to user100109

    Hello Markus,

    we dont have a VPN active and firewall settings are unchanged. After ncsmgr init-ncs I get the following result:

    Regards

    Dirk

  • 0

    Thanks for the feedback, Dirk!

    dhandzic said:
    we dont have a VPN active and firewall settings are unchanged. After ncsmgr init-ncs I get the following result:

    Lets try this another way, then:

    • Close the Toolchain Manager.
    • In ../ncs/downloads, you should have a file that is named something like: ncs-toolchain-v1.9.0-20220217-728bbd5.zip
    • Please unzip to a folder named "toolchain" (should be root folder).
    • Delete everything in ../ncs/v1.9.0 and move the folder "toolchain" to it.
    • Re-open Toolchain Manager & bash and re-run ncsmgr init-ncs.

    Regards,

    Markus

  • 0 in reply to user100109

    Hi Markus,

    this procedure solved the problem. Thank you very much for the swift help.

    Regards

    Dirk

  • 0
    dhandzic said:

    this procedure solved the problem. Thank you very much for the swift help.

    My pleasure, Dirk!

    Ha det gött :-)

    //Markus

Related
Terms of service