This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

I don't have an "Open IDE" button for nRF Connect SDK v1.4.99-dev1

I have the latest nRF Connect for Desktop.

After I install "nRF Connect SDK v1.4.99-dev1" in Toolchain Manager I don't have an "Open IDE" button.

I've tried uninstalling and reinstalling, but that doesn't fix it.

Any ideas on how to fix this?

Parents Reply Children
  • It turns out our corporate antivirus was blocking west at ncs\v1.4.99-dev1\toolchain\opt\bin\Scripts\west.exe

    Is there any reason you know of why west for v1.4.0 would not be blocked but west for v1.4.99-dev1 would?

    (I'm wondering if this is going to be a problem every time I install a new version of the SDK)

  • Can you please try to install NCS 1.4.2 and/or reinstall NCS 1.4.99-dev1 outside of corporate network? Remember that v1.4.99-dev1 is master branch and may include functionality under testing that may cause issues i.e. not stable. Currently v1.4.2 is latest stable release. 

    However, I agree that it should not cause issues like what you are seeing and I will forward to our Toolchain Manager developers. 

    Can you provide more info on what environment you are on? I.e. Windows, Linux, MacOS?

  • I work from home and have not had VPN enabled during any of these installations (so I'm on my home network not the corporate network)

    My work PC (provided by my employer) has these properties:

    An attempt to install 1.4.2 failed in the same way (no "Open IDE" button)

    An attempt to install 1.4.1 succeeded (I did get an "Open IDE" button)

    So it looks like the problem starts with 1.4.2

    I also tried my personal laptop (different security policies and anti-virus software, but on the same network)

    Processor Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz   2.40 GHz
    Installed RAM 8.00 GB (7.87 GB usable)
    System type 64-bit operating system, x64-based processor
    Pen and touch Touch support with 10 touch points
    Edition Windows 10 Home
    Version 20H2
    Installed on ‎8/‎15/‎2020
    OS build 19042.746
    Experience Windows Feature Experience Pack 120.2212.551.0

    An attempt to install 1.4.2 succeeded

    An attempt to install 1.4.99-dev1 succeeded

  • Hello, 

    I've been working with our R&D team, and it looks like this is an issue with the path. It cannot include "cd" it looks like. Can you please change your build folder to e.g. C:\Temp\SES or similar? 

    -Øyvind

  • By "build folder" do you mean the installation directory as shown when you start the installation process?

    This is the installation directory I'm currently using

Related