nrf Connect SDK Issues with west.yml workspaces in VS Code

I am trying to add s2opc to my project. But everytime i try to open the complete Workspace in VSCode, the nrf Connect extension, just does nothing.

How to reproduce. Take the blinky example, make it a git repo, create a west.yml file looking like this:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
manifest:
remotes:
- name: ncs
url-base: https://github.com/nrfconnect
projects:
- name: nrf
remote: ncs
repo-path: sdk-nrf
revision: v2.7.0
import: true
- name: s2opc
groups:
- s2opc
path: deps/modules/lib/s2opc
revision: master
url: git@gitlab.com:systerel/S2OPC.git
self:
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX


Now do a west init -m <git clone url>
West update, west zephyr export, pip install all the required requirements etc...

If i now open the app folder or the overarching folder containing the nrf sdk and zephyr, the VSCode extension just spins indefinetly. Sometimes it works, by just opening the app folder, but then it still fails to compile, something that is easily reproducable on the command line.

Parents
  • Finally got it working. Using the following approach.
    Stop using the WSL.

    Using Windows normally for setting everything up now i can get it to a workable state, and finally start debugging the s2opc example code.

  • Hi donpavlov,

    It could be that your initial environment does not have SSH access to GitLab. To confirm, try ssh -T git@gitlab.com and refer to this Stack Overflow discussion: timeout - gitlab.com SSH connection timed out - Stack Overflow

    If you replace the URL with the HTTPS one, it should work.

    Hieu

  • that was working fine, but additionally i installed the toolchain using the commmand line method completely for the linux system, to be tool agnostic, but that might have been my downfall. Might try removing that and then using the  VSCode method only, as that is the setup on the Windows part of the machine.

Reply
  • that was working fine, but additionally i installed the toolchain using the commmand line method completely for the linux system, to be tool agnostic, but that might have been my downfall. Might try removing that and then using the  VSCode method only, as that is the setup on the Windows part of the machine.

Children
  • I think being tool agnostic is a reasonable goal to strive for. I still think the primary issue is with the SSH connection, so if you ever decided to revisit this topic, I would recommend checking that.

  • I explicitly tried the ssh connection and it worked. Also already set ssh keys and .ssh/config for gitlab so it is using the correct credentials.

  • If the SSH connection works but west still fails, then can you retry with more verbose logging?

    To make it faster, remove all projects from the manifest except for s2opc and add -vvvvv after west for good measure.

    For reference, here are the commands I used with a local manifest file.

    Fullscreen
    1
    2
    west -vvvvv init -l
    west -vvvvv update
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX