Attachments (0)
Nordic Case Info
  • Case ID: 283918
Options

NRF Connect - Can't Open VS Code from Toolchain

Dan

Hi - Recently, the NRF Connect Toolchain manager stopped being able to open VS Code and hangs spinning - screenshot below. It used to work so I'm not sure what's changed...

I am on a Mac M1 MacOS Monterey 12.0.1.

Toolchain manager v.0.10.3

nRF Connect for Desktop v3.10.0; SDK v.1.8.0

I include the output from VS Code  - Generate Support Info below (I ran VS code separately after Toolchain manager failed to open it).

Is there a way to manually set all the proper VS Code extension variable settings so I can develop from within VS Code without relying on the Toolchain manager to launch VS Code, or is there something obvious I'm not doing properly?

I saw someone else report that they encountered a similar error but they mistakenly already had VS Code running - that is not my issue. I made sure VS Code was not already running.

Thanks - appreciate any help or guidance! Dan.

Note: per the installation instructions, I installed the x64 version of VS Code: Version: 1.64.1


Commit: d6ee99e4c045a6716e5c653d7da8e9ae6f5a8b03
Date: 2022-02-07T17:26:08.977Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.1.0

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
[19:59:59] west build --build-dir /Users/me/dev/nordic/blinky/build /Users/me/dev/nordic/blinky --pristine --board nrf5340dk_nrf5340_cpuapp -- -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=On -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DBOARD_ROOT:STRING="/Users/me/dev/nordic/mylock" -DCONFIG_DEBUG_OPTIMIZATIONS:STRING="y" -DCONFIG_DEBUG_THREAD_INFO:STRING="y" -DCONF_FILE:STRING="/Users/me/dev/nordic/blinky/prj.conf"
[19:59:59] Failure (code 2).
[20:00:09] west build --build-dir /Users/me/dev/nordic/blinky/build /Users/me/dev/nordic/blinky --pristine --board nrf5340dk_nrf5340_cpuapp -- -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=On -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DBOARD_ROOT:STRING="/Users/me/dev/nordic/mylock" -DCONFIG_DEBUG_OPTIMIZATIONS:STRING="y" -DCONFIG_DEBUG_THREAD_INFO:STRING="y" -DCONF_FILE:STRING="/Users/me/dev/nordic/blinky/prj.conf"
[20:00:09] Failure (code 2).
IMPORTANT: The data below could contain sensitive or confidential information about your environment.
If you do not wish this to be seen by others, please make sure to remove it before sharing.
For help and support, visit the Nordic DevZone at https://devzone.nordicsemi.com/.
{
"platform": {
"os": "darwin",
"osVersion": "Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:01 PDT 2021; root:xnu-8019.41.5~1/RELEASE_ARM64_T6000",
"osKernel": "21.1.0",
"vscode": "1.64.1",
"electron": "13.5.2",
"node": "v14.16.0"
},
"system": {
"date": "2022-02-09T04:02:34.189Z",
"vscodeRoot": "/Applications/Visual Studio Code.app/Contents/Resources/app",
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0

    Hi Dan,

    I would like to have some more information. Did this happen after you did any updates to any application or firmware etc. ?

    Also, is it possible to get some error logs? For eg., if you could get the error messages from developer console, this would be really helpful. I am not quite sure how to do this on a Mac.

    But, I would like to mention that you do not need to use the VS Code through the Toolchain Manager.

    Regards,

    Priyanka

  • 0 in reply to Priyanka

    Hi Priyanka - I attach the log file generated by toolchain manager below. The line that jumps out at me is the one that says "west not found".

    I am surprised to hear that I don't need to launch VS Code from Toolchain Manager on a Mac. In the past, if I didn't do so, the environment variables weren't properly set. For example, now I still can't build the Blinky example and get the following error:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    > Executing task: nRF Connect: Generate config nrf5340dk_nrf5340_cpuapp for /Users/me/dev/nordic/blinky <
    Building blinky
    west build --build-dir /Users/me/dev/nordic/blinky/build /Users/me/dev/nordic/blinky --pristine --board nrf5340dk_nrf5340_cpuapp -- -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=On -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y -DBOARD_ROOT:STRING="/Users/me/dev/nordic/mylock"
    usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
    west: error: argument <command>: invalid choice: 'build' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'help', 'config', 'topdir', 'selfupdate')
    The terminal process failed to launch (exit code: 2).
    Terminal will be reused by tasks, press any key to close it.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Logfile from Toolchain Manager:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    2022-02-09T16:17:29.591Z INFO Initializing environments...
    2022-02-09T16:17:29.594Z INFO Locally exsisting environment found at /opt/nordic/ncs/v1.8.0/toolchain
    2022-02-09T16:17:29.594Z INFO With version: v1.8.0
    2022-02-09T16:17:29.594Z INFO With west found: no
    2022-02-09T16:17:29.696Z INFO Application data folder: /Users/me/Library/Application Support/nrfconnect/pc-nrfconnect-toolchain-manager
    2022-02-09T16:17:31.063Z DEBUG iface: en0
    2022-02-09T16:17:31.063Z DEBUG IP4: 10.0.0.32
    2022-02-09T16:17:31.063Z DEBUG IP6: [i removed this]
    2022-02-09T16:17:31.063Z DEBUG MAC: [i removed this]
    2022-02-09T16:17:31.065Z DEBUG Client Id: 7659xxxxxxxxx [i removed this]
    2022-02-09T16:17:31.073Z DEBUG Google Analytics for category pc-nrfconnect-toolchain-manager has initialized
    2022-02-09T16:17:31.309Z DEBUG App pc-nrfconnect-toolchain-manager v0.10.3 official
    2022-02-09T16:17:31.309Z DEBUG App path: /Users/me/.nrfconnect-apps/node_modules/pc-nrfconnect-toolchain-manager
    2022-02-09T16:17:31.309Z DEBUG nRFConnect 3.10.0, required by the app is (^3.7.0)
    2022-02-09T16:17:31.309Z DEBUG nRFConnect path: /Applications/nRF Connect for Desktop.app/Contents/Resources/app.asar
    2022-02-09T16:17:31.309Z DEBUG HomeDir: /Users/me
    2022-02-09T16:17:31.309Z DEBUG TmpDir: /var/folders/lh/86j7kz7x3kl3xqd_zsw8vhzh0000gn/T/
    2022-02-09T16:17:31.400Z DEBUG Downloading index json with buffer length: 3848
    2022-02-09T16:17:31.420Z DEBUG Downloading index json with buffer length: 2761
    2022-02-09T16:17:31.421Z DEBUG Index json has been downloaded with result: [
    {
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • 0 in reply to Dan

    Hi Dan,

    The Toolchain Manager never sets the environment variables and hence it should work if you do not open VS Code via Toolchain Manager. Also, when building the blinky sample, did you enable the Debug options? 

    Could you try to NOT enable the debug options when you build the blinky sample?

    Regards,

    Priyanka

  • 0 in reply to Priyanka

    HI Priyanka - I ended up doing a clean reinstall of NRF Connect, the Toolchain and VS Code and was able to build and flash the Blinky program (with debug options enabled).

    Although I can launch VS Code directly from the system, I am still unable to launch VS Code from the Toolchain Manager (after the first time where it successfully looks for and installs dependencies, on subsequent launch attempts, it spins endlessly looking for dependencies).

    I would encourage the Nordic team to try this out themselves on an M1 Mac with the latest versions and see if it is reproducible. I am unblocked for now. Thanks, Dan.

  • 0 in reply to Dan

    Hi Dan, 

    Really sorry that you are facing this issue and thanks for the input. I will let the team know.

    Regards,

    Priyanka

1 2 3
Terms of service