Attachments (1) Download All
Nordic Case Info
  • Case ID: 272453
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Zephyr Base not set and "Open IDE" not present in Toolchain Manager

Frikkie Badenhorst

Hi there,

We are trying to download and install the nRF Connect SDK v1.5.1, which seems to be the latest version on Toolchain Manager.

However, after installation, the "Open IDE" button is not present. I thus manually open SEGGER embedded studio from within the SDK install directory. However, I then get the following "Zephyr base not set" issue:

Looks as if the installation was not successful at all, below is the installation log:

11:48:05.932
Finished downloading version v1.5.1 of the toolchain after approximately 6 minute(s)
11:48:05.933
Unpacking toolchain v1.5.1
11:49:07.500
Finished unpacking version v1.5.1; win32; ia32 of the toolchain after approximately 1 minute(s)
11:49:07.500
Update config file
11:49:07.508
Cloning nRF Connect SDK v1.5.1
11:49:07.526
Initializing environment for v1.5.1
11:49:09.458
Finished cloning version v1.5.1 of the nRF Connect SDK after approximately 0 minute(s)
I do not have a VPN enabled, I always disabled the antivirus as well as the network firewall, and no success. Please advise as soon as possible as we are on a tight timeline to decide on hardware.
Thanks,
Kind regards,
Frikkie Badenhorst
Parents
  • 0

    Hi Frikkie, 

    However, after installation, the "Open IDE" button is not present.

    I think we should focus her first, as any issues you see later may be related to the complete distribution not being properly installed.

    Which OS / Windows version do you use?

    Do you get the same behavior if you uninstall nRF Connect, delete %AppData%\nrfconnect\ and try again?

  • 0 in reply to Einar Thorsrud

    Hi Einar,

    I am using the latest update of Windows 10. 

    I will try uninstalling nRF connect and the AppData directory, and reinstall with the VPN deactivated, Antivirus deactived and firewall deactivated.

    Will keep you updated

  • 0 in reply to Frikkie Badenhorst

    Hi Einar,

    We are still not able to install the SDK and SES on our machine.

    What are the possibilities of a nRF Connect for Desktop team member doing a remote desktop connection on our machine in order the see what is going on? We can not waste any more time on this

  • 0 in reply to Frikkie Badenhorst

    Hi,

    I have bumped the internal ticket. However, it is vacation time in Norway now unfortunately it may take some time.

  • 0 in reply to Einar Thorsrud

    Thanks, Einar. We do hope to hear an update soonest

  • 0 in reply to Frikkie Badenhorst

    Any update on this issue? Can we get someone to do a remote connection ASAP?

  • 0 in reply to Frikkie Badenhorst

    Hello, Frikke!

    Einar is away on holiday and I'm taking over the case. There haven't been any updates from the developers on this unfortunately and I've pinged them (again). While we wait please try to reinstall nRF Connect SDK for desktop completely (with any anti-virus or problematic Firewall disabled) by following this procedure:

    - Go to the Toolchain manager app, press the dropdown beside the nRF Connect SDK installation and select Remove. Verify that it is removed by checking the NCS installation folder (C:\Users\<username>\ncs by default).
    - Uninstall the nRF Connect for desktop application
    - Delete the  %appdata%/nrfconnect directory (as you've done before)
    - Delete the C:\Users\<username>\.nrfconnect-apps directory

    Then reinstall nRF Connect for Desktop along with the toolchain manager before installing NCS again. If acceptable please try the most recent release of NCS (v1.6.0), but if 1.5.1 is required you choose that of course. If it fails again please provide the most recent log file located at  %appdata%/nrfconnect/pc-nrfconnect-toolchain-manager/logs.

    Thank you for your patience.

    Best regards,
    Carl Richard

Reply
  • 0 in reply to Frikkie Badenhorst

    Hello, Frikke!

    Einar is away on holiday and I'm taking over the case. There haven't been any updates from the developers on this unfortunately and I've pinged them (again). While we wait please try to reinstall nRF Connect SDK for desktop completely (with any anti-virus or problematic Firewall disabled) by following this procedure:

    - Go to the Toolchain manager app, press the dropdown beside the nRF Connect SDK installation and select Remove. Verify that it is removed by checking the NCS installation folder (C:\Users\<username>\ncs by default).
    - Uninstall the nRF Connect for desktop application
    - Delete the  %appdata%/nrfconnect directory (as you've done before)
    - Delete the C:\Users\<username>\.nrfconnect-apps directory

    Then reinstall nRF Connect for Desktop along with the toolchain manager before installing NCS again. If acceptable please try the most recent release of NCS (v1.6.0), but if 1.5.1 is required you choose that of course. If it fails again please provide the most recent log file located at  %appdata%/nrfconnect/pc-nrfconnect-toolchain-manager/logs.

    Thank you for your patience.

    Best regards,
    Carl Richard

Children
  • 0 in reply to Carl Richard

    Thanks for your response Carl!

    I followed the steps as you explained above (with antivirus and firewall disabled), however the same issue is still present.

    Here is the log file

    Fullscreen 2021-07-20T07_11_55.049Z-log.txt Download

    As you can see, the issue seems to be at the cloning of the toolchain:

    Finished cloning version v1.6.0 of the nRF Connect SDK after approximately 0 minute(s)

    I really hope we can get a response soon as this is holding us up quite a lot. We have seen the installation done successfully on some of our machines, but on other machines this exact issue arises - thus it will probably be best if a team member can do a remote connection on one of our machines in order to identify the issue.

    Regards,

    Frikkie

  • 0 in reply to Frikkie Badenhorst

    Thank you for the logs, Frikkie! I was in contact with one of the developers earlier today. They reassured that these issues are usually a result of anti-virus (including corporate anti-virus), VPN or firewall issues. However, they mentioned that it can arise if the ".west" directory exists in some higher level directory, so please verify that this isn't the case. Did you also have VPN disabled when doing the previous attempt?

    Please contact contact your Regional Sales Manager (RSM) with regards to support meetings. If you aren't aware of who this is I'll DM you their contact details.

    Best regards,
    Carl Richard

  • 0 in reply to Carl Richard

    Hi Carl. I indeed had VPN disabled.

    My install directory is directly on the C: drive. After downloading and installing via Toolchain Manager, the directories are as follow (download folder containing the downloaded .zip files and v1.6.0 as a result from the installation):

    Within v1.6.0, the following directories are available:

    The .west folder is empty. The toolchain folder also does not appear to be complete when comparing to a successful installation. I do not see any other .west directories directly on the C: drive. Any other place I should look?

    Also, antivirus is disabled and no other third party antivirus is installed. Firewall is also disabled during installation.

    I will contact you via DM with regards to contact details for support meetings.

  • 0 in reply to Carl Richard

    I have very similar issue. I have tried the steps given above and resulted in same behavior as @Frikkie B mentioned. The log ends with "Finished cloning version v1.6.0 of the nRF Connect SDK after approximately 0 minute(s)"

    I am attempting installation of 1.6 SDK on a Windows 10 Machine and on a private network.

  • +1 in reply to vin365

    With the help of Carl we have managed to fix this issue yesterday. Below is the summary of the solution for if someone else also encounters the problem:

    The git connection to the github repository/hosted files failed due to an issue on the SSL layer / certificate setup on the host.

    1) Open nRF Connect Toolchain Manager
    Right Click on the arrow of the SDK version to install -> Open Bash

    2) Execute the following command to change git’s SSL config:
    git config --global http.sslbackend schannel

    3) Run "ncsmgr init-ncs". When running this command, you should see all the repositories download and installation proceeding. (Note for command to run successfully there should be no west folder present inside the SDK root directory (e.g. C:\Nordic\SDK\v1.6.0), delete west folder if it is present).

    When closing and restarting nRF Connect, the Open IDE button should be present and you can build some applications :) 

Terms of service