• State Suggested Answer
  • Replies 24 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 10379 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 276895
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF Connect VS Code extension no connected devices

julien.h

Hello,

I recently installed the nRF Connect extension for VS Code on my Mac M1. I am unable to see my connected board as part of the nRF Connect extension.

Setup

  • nrfjprog version: 10.14.0 external
  • JLinkARM.dll version: 7.54c
  • M1 Macbook

Something odd I noticed is when I ran the nrfjprog command in the terminal I get:

nrfjprog --version --log
ERROR: [SeggerBackend] - The J-Link library does not support execution inside rosetta 2. Try executing with arch -arch arm64 nrfjprog...
ERROR: An internal error has occurred, please try again.

If I run with the suggested option then it completes successfully:

arch -arch arm64 nrfjprog -v
nrfjprog version: 10.14.0 external
JLinkARM.dll version: 7.54c

I am then also able to see the serial number of the debugger connected:

arch -arch arm64 nrfjprog --ids
683511319

Am I missing something in my VS Code setup? Is there a known issue with the VS Code extension on M1 mac?

  • 0 in reply to abvio

    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

  • 0 in reply to Doug_H

    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

  • 0

    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"

  • 0 in reply to abvio

    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?

  • 0 in reply to 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.

Related