Invalid nRF Connect SDK. Valid SDK folders contain either an nrf/VERSION or zephyr/VERSION file.

i cannot seem to select nRF Connect SDK when creating application in vs code. i already install the nRF Connect SDK v2.0.0 from the toolchain and the nRF Connect Toolchain is detected. when i click "Open SDK directory" it open v2.0.0 folder but it's empty.

i use pop-os 22.04 and 

  • Hello, 

    Are you behind a firewall? Do you have access to github.com? The SDK is downloaded from github. Can you try to enable verbose mode under settings of Toolchain Manager


    Please note that according to the documentation of nRF Connect for Desktop Ubuntu Linux (latest Long Term Support (LTS) version) is supported, but we do not test against other versions. 

    Thanks. 

    Kind regards,
    Øyvind

  • 18:20:54.163 Start to install toolchain v2.0.0
    18:20:54.164 Installing ncs-toolchain-linux-x86_64-v2.0.0-20220602T091954-9389261.tar.gz at /home/salman/ncs/toolchains/v2.0.0
    18:34:49.752 Cloning nRF Connect SDK v2.0.0
    18:34:49.756 Initializing environment for v2.0.0
    18:34:52.132 Finished cloning version v2.0.0 of the nRF Connect SDK after approximately 0 minute(s)

    this is what it show after verbose enabled. it still do nothing for sdk. it just clone github rep? is there anyway i can do it manually?

  • Sounds like you should try the manual install of the nRF Connect SDK.

    Muhammad Salman Galileo said:
    it just clone github rep?

    Yes, it will clone the needed repos based on west.yml found in the sdk-nrf repo.

    Kind regards,
    Øyvind

  • I am experiencing the same issue on Fedora 36. With verbose logging enabled, the output is the same:

    However, opening the log file gives more information:

    2022-06-28T17:03:27.702Z DEBUG Traceback (most recent call last):
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/bin/west", line 8, in <module>
    
    2022-06-28T17:03:27.703Z DEBUG     sys.exit(main())
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/app/main.py", line 786, in main
    
    2022-06-28T17:03:27.703Z DEBUG     app.run(argv or sys.argv[1:])
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/app/main.py", line 101, in run
        self.load_manifest()
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/app/main.py", line 119, in load_manifest
    
    2022-06-28T17:03:27.704Z DEBUG     self.manifest = Manifest.from_topdir(topdir=self.topdir,
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/manifest.py", line 1105, in from_topdir
    
    2022-06-28T17:03:27.704Z DEBUG     return Manifest(topdir=topdir, config=config,
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/manifest.py", line 1373, in __init__
    
    2022-06-28T17:03:27.705Z DEBUG     self._ctx = self._top_level_init(source_data,
    
    2022-06-28T17:03:27.705Z DEBUG   File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/manifest.py", line 1715, in _top_level_init
    
    2022-06-28T17:03:27.706Z DEBUG     manifest_path_option = get_option('manifest.path')
    
    2022-06-28T17:03:27.706Z DEBUG   File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/manifest.py", line 1712, in get_option
    
    2022-06-28T17:03:27.709Z DEBUG     return config.get(option, default=default,
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/configuration.py", line 169, in get
        return self._get(lambda cf: cf.get(option), default, configfile)
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/configuration.py", line 208, in _get
        for cf in self._whence(configfile):
      File "/home/theol/ncs/toolchains/v2.0.0/usr/local/lib/python3.8/site-packages/west/configuration.py", line 229, in _whence
        raise RuntimeError('local configuration file not found')
    RuntimeError: local configuration file not found
    
    2022-06-28T17:03:27.756Z DEBUG Sending usage data {"category":"pc-nrfconnect-toolchain-manager","action":"Clone nRF Connect SDK successfully","label":"v2.0.0; linux; x64"}
    2022-06-28T17:03:27.760Z DEBUG Sending usage data {"category":"pc-nrfconnect-toolchain-manager","action":"Clone nRF Connect SDK time consumed","label":"0 min; v2.0.0"}
    2022-06-28T17:03:27.762Z INFO Finished cloning version v2.0.0 of the nRF Connect SDK after approximately 0 minute(s)

    This seems to be a similar problem to devzone.nordicsemi.com/.../runtime-error-while-installing-nrf-connect-sdk-in-ubuntu

  • Hello  , I'm afraid Fedora is not supported by the Toolchain Manager. Currently our team is focused on Ubuntu v20.04 support. Our developers are aware that the use of "Linux" is too vague in regards to the Linux community. We will update our documentation to reflect this better. 

      in regards to Pop! OS, we are aware of issues in Ubuntu v22.04 which your OS might have inherited. 

    That said, you are both welcome to test the latest version of Toolchain Manager v1.1.0 released yesterday. 

    Kind regards,
    Øyvind

Related