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
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
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
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
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
```
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.
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?
Hi,
paul_tanner said:Is that the right version/ location?
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?
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.
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.