“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 

[paul_tanner]

2 things bothering me.  fFrstly if you look at the image showing the red error message you will see that the Toolchain version is not set (cannot be set).

Secondly in the Connect SDK there is a side panel to show settings such as ncs_tag.  Should these be blank.  The GnuArmEmb_path is not the one I have set.

Is this OK?

[Einar Thorsrud]

Hi,

paul_tanner said:

2 things bothering me.  fFrstly if you look at the image showing the red error message you will see that the Toolchain version is not set (cannot be set).

I do not see any error message. Can you clarify?

paul_tanner said:

Secondly in the Connect SDK there is a side panel to show settings such as ncs_tag.  Should these be blank.  The GnuArmEmb_path is not the one I have set.

These are used for the getting started assistant to verify your steps. It makes sense to set them correctly when using the getting started assistant, but it does not have any other consequences. 

Regarding the log, I notice "CMAKE_MAKE_PROGRAM is not set". Can you double-check that you have followed every step in the guide so that all dependencies are correctly installed? I should also note that another good guide (which I personally prefer) is the one in the nRF Connect SDK documentation under Installing the nRF Connect SDK manually. Following that in detail should give you a working setup. Just remember that there is one exception which is that you need to install a signed ARM GCC on recent macOS versions, as we have allready discussed.

Lastly, if you do not have success in getting this working, it might be worth trying the Toolchain Manager, even though it is still experimental for macOS.

[paul_tanner]

The image I refer to is near the top of this post.  It contains a red highlighted error message.  Behind that is the field I was concerned about.

You have pointed out that settings such as ncs_tag are only needed for verification.  How could I set them?

In the options for CMake Executable I have /usr/local/bin/cmake which resolves to

```

lrwxr-xr-x  1 paul_tanner  admin  32  4 Jun 16:34 /usr/local/bin/cmake -> ../Cellar/cmake/3.17.3/bin/cmake

```

 

[Einar Thorsrud]

Hi, 

paul_tanner said:

The image I refer to is near the top of this post.  It contains a red highlighted error message.  Behind that is the field I was concerned about.

Ah, now I understand which image you refer to. That is all correct. When NONE is selected there, you use the SES configuration where you set the Zephyr base directory and ARM GCC toolchain path. The toolchain drop-down only provides alternatives when you use the toolchain manager. If not, you use what you have configured.

paul_tanner said:

You have pointed out that settings such as ncs_tag are only needed for verification.  How could I set them?

You just write into the boxed on the left side. And then if you try to use the verify feature for some steps that rely on the fields, it will use that information.

[paul_tanner]

OK. So everything is set now.

Comment: writeable boxes that don't look writeable are not good UI.  I suggest adding a note to say how to set them.

Returning to "create_nordic_project.py".  I see that we have that file

```

-rw-r--r--@ 1 paul_tanner  staff  20510 16 Oct 19:42 /Applications/arm_segger_embedded_studio_v510d_macos_x64_nordic/html/create_nordic_project.p

```

Is that the right version/ location?