M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

RE: M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

jcvandegrift — Thu, 16 Jun 2022 18:46:59 GMT

Success...

Downloaded the latest MacOS from Nordic and UNIVERSAL (NOT m1) from Segger.

Segger J-Link 7.66c - Universal Installer (again, NOT the m1 choice)
nRF Command Line Tools 10.16.0 MacOS
nRF Connect for Desktop 3.11.1 MacOS

(I'm curious if non-Nordic folks can use Segger's M1 J-Link, otherwise it would have no reason to exist.)

RE: M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

Einar Thorsrud — Thu, 16 Jun 2022 06:35:17 GMT

It is the same in that case. Download nRF Command Line tools, and then separately download the universal J-Link driver package from Segger. (I expect we will start bundling that soon so that you can use the J-Link installer supplied with nRF Command Line tools in the future.)

RE: M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

jcvandegrift — Wed, 15 Jun 2022 17:27:33 GMT

Thanks, I don't believe I use VS Code, I just want nRF Connect and the nrfjprog executables to work on M1 Silicon, Monterrey OS. I'll poke around the website and try to figure out precisely what I'm supposed to download.

RE: M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

Einar Thorsrud — Wed, 15 Jun 2022 07:17:26 GMT

Hi Jeff,

Everything should work with the ARM build of VS Code now, as long as you install the universal J-Link package. I use that combination myself.

RE: M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

jcvandegrift — Tue, 14 Jun 2022 20:41:53 GMT

My Requirements:

M1 platform
nrf52 target
nrfjprog
nrf connect

Given my requirements should I:

Install Universal, or
Follow je90's instructions, or
something else?

- Jeff

RE: M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

jcvandegrift — Tue, 14 Jun 2022 20:41:18 GMT

My Requirements:

M1 platform
nrf52 target
nrfjprog
nrf connect

Given my requirements should I:

Install Universal, or
Follow je90's instructions, or
something else?

- Jeff

RE: M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

Scott — Mon, 09 May 2022 15:05:52 GMT

I appreciate all of this and found the same but it took a long time to figure all of this stuff out and worse it also doesn't get all the way there

For me the damage is done. I wasted a week that I could have spent porting code from our old nRF5 SDK implementation trying to get this stuff to barely work and then I hit one road block too many and decided not to fall for the fallacy of sunk costs and to cut my losses

The fact that you or I could (mostly) get there in time says that it's totally possible and I just increasingly have no tolerance for companies that make the better part of a billion dollars a year in revenue who can't drop less than a hundred grand to get a M1 based MacBook Pro and an intern or two to spend a few weeks sorting out and deploying a good solution to save all of their customers from having to fight with their tools

I'm so tired of wanting to spend my time on interesting and genuinely hard problems and having to waste most of my time and effort overcoming little piddly roadblocks like this that shouldn't exist in the first place.

RE: M1 Mac fixes for nRF Connect, VS Code, and nrfjprog

Einar Thorsrud — Mon, 09 May 2022 12:44:37 GMT

Hi,

Thank you for sharing!

I want to mention that you can also use the Universal installer of J-Link, which will should solve much of this. There are some problems with nRF51 though, which is why the universal installer is currently not bundled with nRF Command Line Tools (this should be solved in an upcoming version, though).