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

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

Einar Thorsrud — Fri, 20 Nov 2020 13:50:51 GMT

Hi,

[quote user="paul_tanner"]I have looked at these permissions and they look OK.[/quote]

I see.

[quote user="paul_tanner"]Note also, I can build manually with west. Presumably that and SES use the same tools.[/quote]

Yes, SES use mostly the same tools. It was just a shot in the dark, really...

Which MacOS version are you using? We see what appears to be the same issue with the toolchain manager and SES under Catalina and other issues under Big Sur. It has been reported and is being looked into but I do not have any further suggestions at the moment.

In the mean-time though, building on the command line should be a good alternative. You can combine that with the Segger Ozone debugger, which will still give you a user friendly debugging experience.

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

paul_tanner — Thu, 19 Nov 2020 19:44:24 GMT

I have looked at these permissions and they look OK.

Note also, I can build manually with west. Presumably that and SES use the same tools.

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

Einar Thorsrud — Thu, 19 Nov 2020 12:18:05 GMT

Hi,

[quote user="paul_tanner"]Is that the right version/ location?[/quote]

Yes, that looks correct (matches SES (Nordic) 5.10d).

It is a bit difficult to suggest anything as I have not reproduced this, but a colleague of mine had a similar issue and found that it was a problem that ninja only had execute permissions but not read. That was also suggested in this thread. Can you try that and see if changing the file permissions of ninja helps?

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

paul_tanner — Wed, 18 Nov 2020 15:28:04 GMT

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?

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

Einar Thorsrud — Wed, 18 Nov 2020 14:13:24 GMT

Hi,

[quote user="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.[/quote]

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.

[quote user="paul_tanner"]You have pointed out that settings such as ncs_tag are only needed for verification. How could I set them?[/quote]

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.

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

paul_tanner — Wed, 18 Nov 2020 13:53:15 GMT

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

```

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

Einar Thorsrud — Wed, 18 Nov 2020 13:29:14 GMT

Hi,

[quote user="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).[/quote]

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

[quote user="paul_tanner"]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.[/quote]

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.

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

paul_tanner — Wed, 18 Nov 2020 11:31:59 GMT

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?

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

paul_tanner — Tue, 17 Nov 2020 16:15:08 GMT

ok. after a couple of tries I got the log:

```

Creating solution blinky.emProject
/usr/local/bin/cmake -GNinja -DBOARD=nrf9160dk_nrf9160ns -DBOARD_DIR=/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/boards/arm/nrf9160dk_nrf9160 -B/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns -S/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/Applications/ARM -DPYTHON_EXECUTABLE=/usr/local/bin/python3 -DCMAKE_MAKE_PROGRAM=/usr/local/bin/ninja -DDTC=/usr/local/bin/dtc -D WEST=/usr/local/bin/west -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=/Applications/arm_segger_embedded_studio_v510d_macos_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Application: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky
-- Zephyr version: 2.4.0 (/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr)
-- Found west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160ns
-- Cache files will be written to: /Users/paul_tanner/Library/Caches/zephyr
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Applications/ARM)
-- Found BOARD.dts: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns.dts
-- Generated zephyr.dts: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/Kconfig
Loaded configuration '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/.config'
No change to configuration in '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/.config'
No change to Kconfig header in '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/include/generated/autoconf.h'
-- Application: /Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/samples/spm
-- Zephyr version: 2.4.0 (/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr)
-- Found west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160
-- Cache files will be written to: /Users/paul_tanner/Library/Caches/zephyr
-- Found toolchain: gnuarmemb (/Applications/ARM)
-- Found BOARD.dts: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts
-- Found devicetree overlay: /Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/samples/spm/nrf9160dk_nrf9160.overlay
-- Generated zephyr.dts: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/Kconfig
Loaded configuration '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/.config'
No change to configuration in '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/.config'
No change to Kconfig header in '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/include/generated/autoconf.h'
-- Configuring incomplete, errors occurred!
See also "/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/CMakeFiles/CMakeOutput.log".
-- Configuring incomplete, errors occurred!
See also "/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/CMakeFiles/CMakeOutput.log".
See also "/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/CMakeFiles/CMakeError.log".
Including boilerplate (Zephyr base (cached)): /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/cmake/app/boilerplate.cmake
nrf9160dk_nrf9160ns.dts.pre.tmp:357.32-361.5: Warning (simple_bus_reg): /soc/cryptocell-sw: missing or empty reg/ranges property
nrf9160dk_nrf9160ns.dts.pre.tmp:56.42-68.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/flash-controller@39000: duplicate unit-address (also used in node /soc/peripheral@40000000/kmu@39000)
nrf9160dk_nrf9160ns.dts.pre.tmp:305.19-311.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/clock@5000: duplicate unit-address (also used in node /soc/peripheral@40000000/power@5000)
Changed board to secure nrf9160dk_nrf9160 (NOT NS)

=== child image spm - begin ===
Including boilerplate (Zephyr base (cached)): /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/cmake/app/boilerplate.cmake
CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
CMake Error at /Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/cmake/multi_image.cmake:214 (message):
CMake generation for spm failed, aborting. Command: 1
Call Stack (most recent call first):
/Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/cmake/multi_image.cmake:75 (add_child_image_from_source)
/Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/samples/CMakeLists.txt:22 (add_child_image)

error: cmake failed
create_nordic_project.py failed (1)

```

Not sure how to fix it tho'

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

Einar Thorsrud — Tue, 17 Nov 2020 15:36:14 GMT

Hm, then I am not sure... Can you show the log form SES? (you will be able to see it in the lower part of the SES window after you click OK on the error message).

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

paul_tanner — Tue, 17 Nov 2020 15:21:58 GMT

get the same error with that board. Also tried to build blinky. same error.

create_nordic_project.py failed (1).

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

Einar Thorsrud — Tue, 17 Nov 2020 15:06:27 GMT

Hi,

Ah, sorry. I did not remember that. But now I spotted another issue, which would also give you this error. You have specified the wrong board. You ned to use nrf9160dk_nrf9160ns. It is not possible to run sample projects that use the modem in any thing other than non-secure mode (ns).

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

paul_tanner — Tue, 17 Nov 2020 14:38:16 GMT

Thx but ...

If you look further up this post you will see that I have indeed set those correctly

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

Einar Thorsrud — Tue, 17 Nov 2020 14:24:15 GMT

Hi,

Update on this. In my case the issue was that I had not updated the paths correctly (after moving things around). Perhaps you did the same, or forgot to set zephyr and toolchain base in the first place?

Before opening a NCS project you need to start SES, then go to Tools -> Options ... and select nRF Connect. Then you need to set the two Directories correctly. In my case it is like this, but you need to adjust it for your setup:

After that, you should be able to open a NCS project from File -> Open nRF Connect SDK Project...

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

Einar Thorsrud — Tue, 17 Nov 2020 14:11:12 GMT

Hi,

I see. I just updated to Big Sur an SES (Nordic) 5.10d and now I get the same error as you see. I have not found an explanation for this or workaround yet, though.

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

paul_tanner — Tue, 17 Nov 2020 12:25:18 GMT

Thx for that. That method builds OK (i.e. I don't see any errors) and generates the .hex file.

Still can't build with SES (see error below).

I have not tried to reinstall the toolchain as yet. Do you think that would fix this error

```

create_nordic_project.py failed (1).

```

? which looks more like a file protection problem.

Thx.

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

Einar Thorsrud — Tue, 17 Nov 2020 10:12:21 GMT

Hi,

[quote user="paul_tanner"]Where should .zephyrrc be located? Tried it in my home directory to no effect.[/quote]

Yes, it should be in your home directory.

To build from the command line you navigate to the nRF Connect SDK folder. Then you first need to source zephyr/zephyr-env.sh:

source zephyr/zephyr-env.sh

After that, navigate to the project you want to build, e.g. at_client:

cd nrf/samples/nrf9160/at_client

and then build with west like this:

west build -b nrf9160dk_nrf9160ns --pristine

Does that work? If not, what error do you get?

I should also note that the Toolchain Manager has experimental support for macOS now, and using that you will get a sandboxed toolchain automatically and would not have to to through this manual setup.

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

paul_tanner — Tue, 17 Nov 2020 10:00:32 GMT

Thx Einar,

Where should .zephyrrc be located? Tried it in my home directory to no effect.

Also, working from nRF Connect v3.6.0, I do not see any instructions for building from the command line. This is what I would usually want to do but have been following "Getting Started Assistant".

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

Einar Thorsrud — Tue, 17 Nov 2020 09:20:48 GMT

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.

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

paul_tanner — Tue, 17 Nov 2020 09:10:01 GMT

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

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

Einar Thorsrud — Tue, 17 Nov 2020 07:38:55 GMT

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"

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

paul_tanner — Mon, 16 Nov 2020 17:06:00 GMT

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

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

Einar Thorsrud — Mon, 16 Nov 2020 13:34:56 GMT

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