Attachments (0)
Nordic Case Info
  • Case ID: 259869
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

“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 

Parents
  • 0

    Hi,

    paul_tanner said:
    I have looked at these permissions and they look OK.

    I see. 

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

    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.

Reply
  • 0

    Hi,

    paul_tanner said:
    I have looked at these permissions and they look OK.

    I see. 

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

    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.

Children
No Data
Terms of service