nRF Connect VS Code extension no connected devices

RE: nRF Connect VS Code extension no connected devices

Bence — Thu, 05 May 2022 13:29:22 GMT

Regarding VS Code on Apple M1 the only limitation according to our latest findings is that any flavour of VS Code works, the only limitation is that JLink package from SEGGER must be universal.

https://nrfconnect.github.io/vscode-nrf-connect/connect/install.html#installing-on-windows-and-macos

The tools in the SDK toolchain are still Intel only, but they seem to work just fine in M1 environment.

RE: nRF Connect VS Code extension no connected devices

jcvandegrift — Thu, 05 May 2022 13:23:08 GMT

I am replying to a six month old posting about Apple M1. Is the information I'm replying to still correct? Is there a webpage that accurately describes how to work with Nordic on an M1 platform? There needs to be ONE PLACE that is current and accurate that describes the state of M1 tools.

RE: nRF Connect VS Code extension no connected devices

David Elvig — Wed, 03 Nov 2021 14:39:14 GMT

Thanks for this.

I'll install the Intel version of VS Code and report back

RE: nRF Connect VS Code extension no connected devices

abvio — Wed, 03 Nov 2021 12:41:57 GMT

I'm happy to report that my M1 MacBook Air is able to use VS Code and nRF Connect v1.7.1 to compile and debug on my nRF52 DK board. As Vidar said, the key thing is to be sure to install the "Intel Chip" version of VS Code from the VS Code download page, which is here. If you install the Universal version, I've found that it does not give the checkbox to use Rosetta.

Steve

RE: nRF Connect VS Code extension no connected devices

Vidar Berg — Wed, 03 Nov 2021 08:33:54 GMT

David Elvig , please see my other reply in this thread. You need to have the intel version of VS code and Command line tools installed.

RE: nRF Connect VS Code extension no connected devices

David Elvig — Tue, 02 Nov 2021 23:42:58 GMT

I think I'm having this too:

MacBook Pro M1
Big Sur: 11.6
VS Code: 1.61.2 (Universal)
nRF Connect v3.7.2
Toolchain Manager: v0.10.0
nRF Connect SDK: v1.7.1

and this error in the bottom right of VS Code after opening a sample project (peripheral_hr)

nRF52840-DK

Trying to connect the DK, I get this error

I'm excited by the possibilities here...

Any guidance, or should I just watch this thread?

RE: nRF Connect VS Code extension no connected devices

Vidar Berg — Thu, 21 Oct 2021 12:13:32 GMT

We currently recommend to use the intel/x86_64 variant of the SDK development tools:

"For M1 based Mac machines you need to run the Intel versions of the tools, not the M1 versions. This is due to driver incompatibilities and since we do not have M1-versions of all components we are forced to do this now. Long term goal is to get native M1 support. And for those of you worried about performance: Performance will not be significantly reduced by running the Intel versions for our type of applications.

The relevant tools are:

VS Code
nRF Command line tools: Here you need to run version 10.13.0 on M1 due to an issue with 10.14.0. This will be fixed in 10.15.0 to be release within a few weeks.
Jlink software from Segger

The other tools are all intel versions if installed using the Toolchain manager"

RE: nRF Connect VS Code extension no connected devices

abvio — Mon, 11 Oct 2021 02:50:17 GMT

You're in good company, Doug. A few of us are raring to go with VS Code and our M1 Macs, but we're waiting for the good folks at Nordics to update the command line tools.

Bence on the Nordic VS Code team acknowledged this around October 1 2021, thankfully.

Thanks for pointing out that using nrfjprog could be a simple workaround in the mean time.

Best, Steve

RE: nRF Connect VS Code extension no connected devices

Doug_H — Mon, 11 Oct 2021 01:17:02 GMT

I'm having the same problems on my M1 Mac Mini with VS Code extension. I can build the NCS project no problems but cannot connect to the development board. It is failing with a JLink error that it isn't able to find the connected board, but when I issue the same nrfjprog command from a zsh terminal it works fine. I can also read and write to the board using the nRF Connect Desktop Programmer App so it's not an issue with the M1 Mac. It's only having trouble within VS Code. -- Doug

RE: nRF Connect VS Code extension no connected devices

abvio — Thu, 07 Oct 2021 19:34:40 GMT

This is a different issue than the original poster and I have. Ours is caused by the fact that we are using MacBook M1 devices, and the toolchain has some components that do not work under the MacBook M1. We look forward to this being updated. -- Steve

RE: nRF Connect VS Code extension no connected devices

jdorn — Thu, 07 Oct 2021 19:30:19 GMT

I was able to fix this issue on windows 10 by installing the nRF Command Line Tools.

www.nordicsemi.com/.../Download

RE: nRF Connect VS Code extension no connected devices

y009 — Thu, 07 Oct 2021 08:27:16 GMT

I am on windows and experiencing a similar issue after switching to nrf connect extension.

The "tools" in the json settings all show a null.

Might help with debugging this issue

After adding

"terminal.integrated.inheritEnv": false

to my vsc setting.json I get :

"tools": {
"jlink": null,
"nrfjprog": null,
"cmake": "3.21.3",
"west": "0.11.1",
"python": "3.10.0",
"ninja": "1.10.2",
"gperf": "3.1",
"dtc": null,
"gnuarmemb": null,
"gn": null
},

And connected devices show up but unable to flash since nrfjprog still isnt detected properly.

Might be worth mentioning that the first flash with using the extension worked before changign vsc settings. Subsequent tries failed.

EDIT:
Reinstalling nrf connect and nrf terminal extensions in vsc fixed my issues on windows for now.

RE: nRF Connect VS Code extension no connected devices

shybeetle — Thu, 07 Oct 2021 00:15:37 GMT

I am having the same issue!

"tools": {

"jlink": null,

"nrfjprog": null,

"cmake": null,

"west": null,

"python": "3.8.9",

"ninja": null,

"gperf": "3.0.3",

"dtc": null,

"gnuarmemb": null,

"gn": null

"environment": {

"westExe": "/opt/nordic/ncs/v1.7.0/toolchain/bin/west",

"westEnv": {

"ELECTRON_RUN_AS_NODE": "1",

"GIT_EXEC_PATH": "/opt/nordic/ncs/v1.7.0/toolchain/Cellar/git/2.32.0_1/libexec/git-core",

"HOME": "/Users/ndelafuente",

"PATH": "/opt/nordic/ncs/v1.7.0/toolchain/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin",

"ZEPHYR_BASE": "/opt/nordic/ncs/v1.7.0/zephyr",

"GNUARMEMB_TOOLCHAIN_PATH": "/opt/nordic/ncs/v1.7.0/toolchain",

"ZEPHYR_TOOLCHAIN_VARIANT": "gnuarmemb",

"USER": "ndelafuente"

"toolchainPath": "/opt/nordic/ncs/v1.7.0/toolchain",

"toolchainBinPath": "/opt/nordic/ncs/v1.7.0/toolchain/bin",

"toolchainVersion": "1.7.0"

RE: nRF Connect VS Code extension no connected devices

abvio — Mon, 04 Oct 2021 16:09:07 GMT

Glad I found this post! I'm experiencing the same issue. -- Steve

RE: nRF Connect VS Code extension no connected devices

Bence — Thu, 30 Sep 2021 12:56:23 GMT

Hi julien.h,

Unfortunately there is no fix at the moment to this issue since there are some parts in this setup that have no M1 support. In any case we are aware and we try to work out the solution.

Bence

VS Code Team

RE: nRF Connect VS Code extension no connected devices

julien.h — Tue, 28 Sep 2021 15:29:18 GMT

Hi,

My tools are indeed in /usr/local/bin directory which is missing from "PATH": "/opt/nordic/ncs/v1.6.1/toolchain/bin:/usr/bin:/bin:/usr/sbin:/sbin" in westEnv. However, I don't know how this west environemnt path is generated. I know the first part is based on the settings for the toolchain (/opt/nordic/ncs/v1.6.1/toolchain/bin) however I don't know how the second part is picked up (/usr/bin:/bin:/usr/sbin:/sbin).

I put in my ~/.profile:

export PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:$PATH

Which seems to be working fine when I do:

echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Contents/Public:/Library/TeX/texbin:/opt/X11/bin

But still not updating the PATH in westEnv and not seeing the tools picked up.

Thanks.

RE: nRF Connect VS Code extension no connected devices

Dee Roberts — Tue, 28 Sep 2021 07:22:01 GMT

Hi,

It looks like your PATH is missing the /usr/local/bin directory. When I run which on the various tools, they are all located there. If that directory is not in your PATH, please add it and try again.

If you still have problems, can you confirm which shell you are using? If you're using zsh, please try copying your environment variables to your ~/.profile file. The extension currently has a few issues with picking up variables defined in .zshrc, which we're working to improve.

-Dee

RE: nRF Connect VS Code extension no connected devices

julien.h — Mon, 27 Sep 2021 15:18:50 GMT

Hi Dee,

It looks like the tools section doesn't find the different paths. Why is that?

"tools": {

"jlink": null,

"nrfjprog": null,

"cmake": null,

"west": null,

"python": null,

"ninja": null,

"gperf": null,

"dtc": null,

"gnuarmemb": null,

"gn": null

"environment": {

"westExe": "/opt/nordic/ncs/v1.6.1/toolchain/bin/west",

"westEnv": {

"ELECTRON_RUN_AS_NODE": "1",

"GIT_EXEC_PATH": "/opt/nordic/ncs/v1.6.1/toolchain/Cellar/git/2.32.0_1/libexec/git-core",

"HOME": "/Users/user",

"PATH": "/opt/nordic/ncs/v1.6.1/toolchain/bin:/usr/bin:/bin:/usr/sbin:/sbin",

"ZEPHYR_BASE": "/opt/nordic/ncs/v1.6.1/zephyr",

"GNUARMEMB_TOOLCHAIN_PATH": "/opt/nordic/ncs/v1.6.1/toolchain",

"ZEPHYR_TOOLCHAIN_VARIANT": "gnuarmemb",

"USER": "user"

"toolchainPath": "/opt/nordic/ncs/v1.6.1/toolchain",

"toolchainBinPath": "/opt/nordic/ncs/v1.6.1/toolchain/bin",

"toolchainVersion": "1.6.1"

Kind regards

RE: nRF Connect VS Code extension no connected devices

Dee Roberts — Mon, 27 Sep 2021 08:38:51 GMT

Hi,

This sounds similar to another issue that we're investigating. We'll hopefully have a fix soon. Just so we have an additional data point to work with, could you please run the following steps:

1. Open the command palette, and run the "nRF Connect: Generate Support Information" command.

2. Find the "tools" and "environment" entries in the JSON entry that should have opened up.

3. Paste that in a reply here

It would be particularly interesting to see if the extension can find nrfjprog in your PATH.

Kind regards,

Dee,

VS Code Team

RE: nRF Connect VS Code extension no connected devices

julien.h — Fri, 24 Sep 2021 15:17:46 GMT

Hi Dee,

Thank you for the answer. I was indeed running the x86 version. I installed the ARM version of VS Code now. However, I am still unable to find the device in VS Code. I still it connected when running "nrfjprog" tool direclty.

Here is the VS Code version I am running:

Version: 1.60.2 (Universal)
Commit: 7f6ab5485bbc008386c4386d08766667e155244e
Date: 2021-09-22T11:59:27.195Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin arm64 20.2.0

Kind regards

RE: nRF Connect VS Code extension no connected devices

Dee Roberts — Fri, 24 Sep 2021 12:16:47 GMT

Hi julien.h,

Thanks for this report. It looks like you're using a version of VS Code compiled for Intel processors. Running this on an M1 machine causes VS Code, and all child processes launched by the extension, to be run inside the Rosetta 2 translation environment. As the error message you received states, nrfjprog isn't compatible with this environment.

Please try uninstalling your current VS Code installation, and instead install the Universal version. That will prevent nrfjprog running inside Rosetta 2, so the connected devices should appear.

Kind regards,

Dee

VS Code Team

RE: nRF Connect VS Code extension no connected devices

Amanda Hsieh — Fri, 24 Sep 2021 08:04:01 GMT

Hi,

It looks like a bug. We will look into this. Thanks for the report.

-Amanda

RE: nRF Connect VS Code extension no connected devices

julien.h — Wed, 22 Sep 2021 14:27:08 GMT

Hi Amanda,

The version is v2021.9.314

RE: nRF Connect VS Code extension no connected devices

Amanda Hsieh — Wed, 22 Sep 2021 07:20:11 GMT

Hi,

What is the extension version number? Is it 2021.8.579 as the figure?

Regards,
Amanda