“arm-none-eabi-gcc” cannot be opened because the developer cannot be verified.

[paul_tanner]

trying to usenRF Connect SDK for the first time.

Could be because of recent upgrades to MacOS.

(I have used gcc with nRF SDKs before)

Paul 

[Einar Thorsrud]

Hi Paul,

Can you try to download and install gcc-arm-none-eabi-9-2020-q2-update-mac.pkg from here? That distribution is signed and sould work also with recent macOS versions.

Einar

[paul_tanner]

That download installs OK.  I think the error is to do with SES trying to use an older version that is still on my machine.

/opt/gnuarmemb seems to be the path it's using.  Is that so?

Maybe I need to change this to wherever the correct version is?

Where is that set?

I think it should point to /Applications/ARM/bin/arm-none-eabi-gcc which reports that it's v9.3.1

[Einar Thorsrud]

Hi, 

You need to point to where the toolchain is by setting GNUARMEMB_TOOLCHAIN_PATH correctly, as indicated under Installing the toolchain. Assuming you install to the default location, you GNUARMEMB_TOOLCHAIN_PATH should point to /Applications/ARM.

Then you need to configure this by adding the following snippet to ~/.zshrc (or ~/.bash_profile if using bash):

# Zephyr related configurations
export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb
export GNUARMEMB_TOOLCHAIN_PATH="/Applications/ARM"

[paul_tanner]

Thanks.  I did that and at first it didn't work as I am running a current version of MacOS that uses zsh.

For that I added the first line:

```

#! /usr/bin/env zsh

```

However, despite the setup now looking as it should, SES is still throwing errors:

create_nordic_project.py failed (1). 

Looks like a different config error. 

Configuration looks OK

[Einar Thorsrud]

Hi,

Ah, yes. I filtered out SES in my head, and focused only on the command line. You should also add the exports in .zephyrrc (adding the same lines). Does that work? If not, can you try building from the command line first, before trying with SES? It would be easier to understand the issue there, and once that works then getting it working in SES should be simpler.