nRF connect SDK issue on VS code and SES V1.7.1

[hiteshk014]

Hi,

I installed NRF connect SDK, 

after installation I navigate from NRF connect desktop app -> Toolchain Manager 

V1.71 is installed in D:\Nordic_App\Nordic_SDK\nCS directory

Problem 1:

I didn't get option of opening SDK in SES, it showed open in VScode, SES version installed is SEGGER Embedded Studio for ARM Release 5.66  Build 2021110300.48263 Windows x64

why it didn't show option of open project in SES? SES is already installed

Problem 2:

after opening in VS code I opened the folder an tried creating new application from samole project it gave me error as attached in screenshot.

Please provide solution to this problem,

I cant change path I want to have folder directory in this way only D:\Nordic_App\Nordic_SDK\nCS

Thank you,

[hiteshk014]

Hi Priyanka,

Please find screenshots,

Thank you,

[hiteshk014]

Hi,

I've installed nRF connect for Desktop & nRF Command Line Tool,

Please find screenshot for version,

Similar issue I had faced earlier which i raised its Case ID: 274751(https://devzone.nordicsemi.com/support/274751),

I had got a solution which I'm mentioning here in this case (https://devzone.nordicsemi.com/f/nordic-q-a/76895/zephyr-base-not-set-and-open-ide-not-present-in-toolchain-manager/321463#321463)

the solution which was mentioned in that was to run 2 commands in git bash

git config --global http.sslbackend schannel

ncsmgr init-ncs

as attached in git bash logs 1st comment which was printed was 

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

ncsmgr init-ncs"

I've attached logs on executing the above 2 commands

Fullscreen git_logs.txt Download

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

ncsmgr init-ncs

LNTIES+40016482@MUTSL02323 MINGW64 /d/Nordic_App/Nordic_SDK/nCS/v1.7.1
$ git config --global http.sslbackend schannel

LNTIES+40016482@MUTSL02323 MINGW64 /d/Nordic_App/Nordic_SDK/nCS/v1.7.1
$ ncsmgr init-ncs
Checking out NCS v1.7.1 ...=== Initializing in D:\Nordic_App\Nordic_SDK\nCS\v1.7.1
--- Cloning manifest repository from https://github.com/nrfconnect/sdk-nrf, rev. v1.7.1
Cloning into 'D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\.west\manifest-tmp'...
fatal: unable to access 'https://github.com/nrfconnect/sdk-nrf/': schannel: next InitializeSecurityContext failed: SEC_E_UNTRUSTED_ROOT (0x80090325) - The certificate chain was issued by an authority that is not trusted.
FATAL ERROR: command exited with status 128: git clone --branch v1.7.1 https://github.com/nrfconnect/sdk-nrf 'D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\.west\manifest-tmp'
/ncsmgr/ncsmgr_init-ncs.sh: line 10: cd: nrf: No such file or directory
fatal: not a git repository (or any of the parent directories): .git
/d/Nordic_App/Nordic_SDK/nCS/v1.7.1
done
Updating repos ...
Traceback (most recent call last):
  File "D:\Nordic_App\Nordic_SDK\nCS\v1.7.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 "D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\toolchain\opt\bin\Scripts\west.exe\__main__.py", line 7, in <module>
  File "D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\toolchain\opt\bin\Lib\site-packages\west\app\main.py", line 779, in main
    app.run(argv or sys.argv[1:])
  File "D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\toolchain\opt\bin\Lib\site-packages\west\app\main.py", line 106, in run
    self.run_command(argv)
  File "D:\Nordic_App\Nordic_SDK\nCS\v1.7.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 "D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\toolchain\opt\bin\Lib\site-packages\west\commands.py", line 132, in run
    self.do_run(args, unknown)
  File "D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\toolchain\opt\bin\Lib\site-packages\west\app\project.py", line 801, in do_run
    self.update_all()
  File "D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\toolchain\opt\bin\Lib\site-packages\west\app\project.py", line 855, in update_all
    self.manifest = Manifest.from_file(
  File "D:\Nordic_App\Nordic_SDK\nCS\v1.7.1\toolchain\opt\bin\Lib\site-packages\west\manifest.py", line 1104, in from_file
    (mpath, mname) = _mpath(topdir=topdir)
  File "D:\Nordic_App\Nordic_SDK\nCS\v1.7.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')

LNTIES+40016482@MUTSL02323 MINGW64 /d/Nordic_App/Nordic_SDK/nCS/v1.7.1
$

Thank you,

[Priyanka]

Hi Hitesh,

Which version of J-Link are you using? We are looking into issues with the v3.9.0 update of the nRF Connect for Desktop and would suggest you to try using the JLink v6.88. Kindly try this and let me know how it goes.

[Nikkolaus]

Hello :)

I want also work with the ncs (V. 1.8) and I have to same issues. It´s kind of sadly for me that the question wasn´t answered jet. 

Can u help me to fix to problem? My task is the same like Hitesh said: if I change the path to the folder to the ncs in VS code i get an error: Invalid NCS installation. And the toolchain manager has no button to open SEGGER. 

I use: -toolchain manager v. 0.10.3
-nRF Connect for Desktop v3.9.3
-nRF command line tool v10.15.2

[Nikkolaus]

.. and I use J-link v6.88a

[Priyanka]

Hi Nikkolaus,

We are working on fixing some issues with the nRF Connect for Desktop and a new version will be released soon with the fixes. But if your issue still persists then, could you upgrade to J-Link versions after v7.20 and also, remove all previous installations from your PC and install everything from our official website once again? I can provide the links below:

nRF Command Line Tools

nRF Connect for Desktop

Hope this helps.

In case your issue persists, kindly open a separate issue and we can delve more into it

Regards,

Priyanka

[Nikkolaus]

Thank you for the answere. 
I just had fixed the problem: the problem was the network. After I changed the Network from my Computer, was there no Proxy anymore and the automatic installation was working. 
The installation of the connect sdk gives the user not mutch feedback, so the issue wasn´t clear for me. But now it works :)