This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Proper mac M1 Support for nRF Connect, VS Code, and nrfjprog?

There have been several releases to both the Command Line Tools and Segger's JLink Software however the full Nordic toolchain still does not properly support the M1.

In order for me to use the command line tools via terminal for a command like nrfjprog --recover I have to install the Command Line Tool (latest 10.15.2) with the JLink M1. However this version of the JLink Software is not supported in NRF Connect Programmer and NEITHER work if using nRF Connect for VS Code.  

I see that the nRF Connect VS Code Extension blames node-usb-native as the reason M1 is not supported, but this is looks to be based on a repo that has not had an update for 9 months and the "native" detector files are all just compiled binaries, so it's unclear if the open source community can contribute to help with this. We would gladly contribute if there was any guidance. v

Just seems odd that nrfjprog works fine from the command line if the JLink M1 inside the latest Command Line Tools works fine, but the other applications do not work. 

Currently development on an M1 is pretty hindered, just an idea when it will be supported in NRF Connect and VS Code would be greatly appreciated. 

  • Hi,

    On M1 Mac you must use the Intel version of the tools for the VS Code extension due to driver incompatibilities. I am not sure if node-usb-native is the only issue, as all I know is that we do not have M1 versions of all components. The long term goal is to get native M1 support, but I do not know when that will happen. If you have questions regarding roadmap or releases, please contact your regional sales manager.

    The relevant tools that you need to run the Intel versions of are:

    • VS Code
    • nRF Command line tools
    • Jlink software from Segger

    Best regards,

    Marte

  • Sort of.

    Here is the compatibility as best as I understand it (as of Feb 2022).

    Now VS Code on M1 will build but no device operations work (Flash, Erase, Debug, etc) due to listed "Known Issues" under the Extension with M1 not supported by node-usb-native.

    Hopefully this helps others who are wondering what works and what doesn't.

Related