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

[Einar Thorsrud]

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?

[Frikkie Badenhorst]

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

[Carl Richard]

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

[Frikkie Badenhorst]

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.

[vin365]

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.

[Frikkie Badenhorst]

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 :) 

[Carl Richard]

Hi, Vin!

Try the method Frikkie just added. If that doesn't work, please open a new ticket for the issue.

Best regards,
Carl Richard

[Major Tom]

Hi Carl,

I've executed everything as mentioned above, but the "Open IDE" is still missing. Here are the loggings from the bash terminal (I have replaced my user name with $user$ here). Can you please advice?

$ ncsmgr init-ncs
Checking out NCS v1.6.1 ...=== Initializing in C:\Users\$user$\ncs\v1.6.1
--- Cloning manifest repository from github.com/.../sdk-nrf, rev. v1.6.1
Initialized empty Git repository in C:/Users/$user$/ncs/v1.6.1/.west/manifest-tmp/.git/
remote: Enumerating objects: 80236, done.
remote: Counting objects: 100% (31/31), done.
remote: Compressing objects: 100% (22/22), done.
remote: Total 80236 (delta 13), reused 17 (delta 8), pack-reused 80205
Receiving objects: 100% (80236/80236), 44.61 MiB | 6.83 MiB/s, done.
Resolving deltas: 100% (58674/58674), done.
From github.com/.../sdk-nrf
* tag v1.6.1 -> FETCH_HEAD
* [new branch] backport-4558-to-v1.5-branch -> origin/backport-4558-to-v1.5-branch
* [new branch] backport-5019-to-v1.6-branch -> origin/backport-5019-to-v1.6-branch
* [new branch] doc/working-thingy53 -> origin/doc/working-thingy53
* [new branch] master -> origin/master
* [new branch] sdc_supports_nrf21540_gpio -> origin/sdc_supports_nrf21540_gpio
* [new branch] v1.0-branch -> origin/v1.0-branch
* [new branch] v1.1-branch -> origin/v1.1-branch
* [new branch] v1.2-branch -> origin/v1.2-branch
* [new branch] v1.3-branch -> origin/v1.3-branch
* [new branch] v1.4-branch -> origin/v1.4-branch
* [new branch] v1.5-branch -> origin/v1.5-branch
* [new branch] v1.6-branch -> origin/v1.6-branch
* [new tag] v0.1.0 -> v0.1.0
* [new tag] v0.1.0-rc1 -> v0.1.0-rc1
* [new tag] v0.3.0 -> v0.3.0
* [new tag] v0.3.0-rc1 -> v0.3.0-rc1
* [new tag] v0.3.0-rc2 -> v0.3.0-rc2
* [new tag] v0.4.0 -> v0.4.0
* [new tag] v0.4.0-rc1 -> v0.4.0-rc1
* [new tag] v0.4.0-rc2 -> v0.4.0-rc2
* [new tag] v1.0.0 -> v1.0.0
* [new tag] v1.0.0-rc1 -> v1.0.0-rc1
* [new tag] v1.0.0-rc2 -> v1.0.0-rc2
* [new tag] v1.0.0-rc3 -> v1.0.0-rc3
* [new tag] v1.0.0-rc4 -> v1.0.0-rc4
* [new tag] v1.1.0 -> v1.1.0
* [new tag] v1.1.0-rc1 -> v1.1.0-rc1
* [new tag] v1.1.0-rc2 -> v1.1.0-rc2
* [new tag] v1.1.0-rc3 -> v1.1.0-rc3
* [new tag] v1.2.0 -> v1.2.0
* [new tag] v1.2.0-rc1 -> v1.2.0-rc1
* [new tag] v1.2.0-rc2 -> v1.2.0-rc2
* [new tag] v1.2.1 -> v1.2.1
* [new tag] v1.2.99-dev1 -> v1.2.99-dev1
* [new tag] v1.3.0 -> v1.3.0
* [new tag] v1.3.0-rc1 -> v1.3.0-rc1
* [new tag] v1.3.0-rc2 -> v1.3.0-rc2
* [new tag] v1.3.0-rc3 -> v1.3.0-rc3
* [new tag] v1.3.1 -> v1.3.1
* [new tag] v1.3.2 -> v1.3.2
* [new tag] v1.3.2-rc1 -> v1.3.2-rc1
* [new tag] v1.4.0 -> v1.4.0
* [new tag] v1.4.0-rc1 -> v1.4.0-rc1
* [new tag] v1.4.0-rc2 -> v1.4.0-rc2
* [new tag] v1.4.1 -> v1.4.1
* [new tag] v1.4.1-rc1 -> v1.4.1-rc1
* [new tag] v1.4.2 -> v1.4.2
* [new tag] v1.4.99-dev1 -> v1.4.99-dev1
* [new tag] v1.5.0 -> v1.5.0
* [new tag] v1.5.0-rc1 -> v1.5.0-rc1
* [new tag] v1.5.1 -> v1.5.1
* [new tag] v1.5.1-rc1 -> v1.5.1-rc1
* [new tag] v1.6.0 -> v1.6.0
* [new tag] v1.6.0-rc1 -> v1.6.0-rc1
* [new tag] v1.6.0-rc2 -> v1.6.0-rc2
* [new tag] v1.6.0-rc3 -> v1.6.0-rc3
* [new tag] v1.6.1 -> v1.6.1
* [new tag] v1.7.0-rc1 -> v1.7.0-rc1
af7a24bd89fc0cd134232975aceaa1c176b23b6f refs/tags/v1.6.1
Updating files: 100% (4280/4280), done.
Note: switching to 'v1.6.1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 651d785a0 version: Update VERSION to 1.6.1
FATAL ERROR: Destination path 'C:\Users\$user$\ncs\v1.6.1\nrf\manifest-tmp' already exists
HEAD is now at 651d785a0 version: Update VERSION to 1.6.1
/C/Users/$user$/ncs/v1.6.1
done
Updating repos ...
Traceback (most recent call last):
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\manifest.py", line 172, in _mpath
path = cp.get('manifest', 'path')
File "configparser.py", line 781, in get
File "configparser.py", line 1149, in _unify_values
configparser.NoSectionError: No section: 'manifest'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "runpy.py", line 193, in _run_module_as_main
File "runpy.py", line 86, in _run_code
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Scripts\west.exe\__main__.py", line 7, in <module>
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\app\main.py", line 779, in main
app.run(argv or sys.argv[1:])
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\app\main.py", line 106, in run
self.run_command(argv)
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\app\main.py", line 336, in run_command
cmd.run(args, unknown, self.topdir, manifest=self.manifest)
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\commands.py", line 132, in run
self.do_run(args, unknown)
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\app\project.py", line 806, in do_run
self.update_all()
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\app\project.py", line 860, in update_all
self.manifest = Manifest.from_file(
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\manifest.py", line 1103, in from_file
(mpath, mname) = _mpath(topdir=topdir)
File "C:\Users\$user$\ncs\v1.6.1\toolchain\opt\bin\Lib\site-packages\west\manifest.py", line 177, in _mpath
raise MalformedConfig('no "manifest.path" config option is set') from e
west.manifest.MalformedConfig: no "manifest.path" config option is set
done
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: error: argument <command>: invalid choice: 'zephyr-export' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate')

Best regards,

Tomislav