Incomplete installation on MacOS, file permission issue ?

[JRSN]

Hi All,

After hours of reading this forum, I could not find a solution to an annoying issue I have with nRF Connect SDK installation on macOS Sonoma.

Please kindly note that I don't want to go through manual installation ;-)

Whenever I try to install the SDK (both via the nRF Connect for desktop App or from with Visual Studio Code):

- in my development account, the SDK directory is not populated at first and further, any attempt to "Update SDK" does not populate it neither

- in my "root" account, the SDK directory is properly populated and the visual studio environment is ready for development.

    - but when back in my account, the visual studio nRF panel, "WELCOME" zone, only allows to create a blank application: the "copy from sample" is missing.

I have redone the automatic process many times, rebooted in between, deleted the installed directories, ...

No way to succeed

Any help would be much appreciated !

[Charlie]

Hi Jean,

I am a Mac user (M1 Macboo+Sonoma) with an Admin account. There is no problem in my experience.

nRF Connect Extension supports full management with nRF Connection SDK(installation, toolchain and so on). nRF Connect for Desktop->ToolChain Manager app is not needed anymore.

For the problem you experienced, I also suspect it is permission-related. Could you try to assign your development account as Admin using your "root account"? then reinstall NCS and Toolchain in VS code through the nRF Connect Extension.

Best regards,

Charlie

[JRSN]

Hi Charlie,

Thanks for the hint.

I have tried giving my account the Administration privileges, deleting the nRF Connect for Desktop and then reinstalling it.

Then deleting the nordic directory and reinstalling everything under my account (not root).

But, still the same issue !

Any other idea ?

TIA

[JRSN]

Hi Charlie,

I wish I could try on another computer or environment but I cannot. Sorry not to be able to help solving this issue with such a try.

Dis you manage to understand the cloning issue ?

Thanks for your help

Regards

JRSN

[Charlie]

No, I did not see any other similar issue reports by far.

May I know your network environment? Is this a PC in the office or school for dedicated usage?

Best regards,

Charlie

[JRSN]

I doubt the issue comes from the network : I usually download GitHub files, applications updates and so on. Its a multi-purpose Mac.

Also, I did successfully managed to install previous releases of Nrf SDK and toolchain, for years and years

JRSN

[Charlie]

Hi JRSN,

I see you mentioned you have successfully installed the toolchain.

Could you try to install NCS through the toolchain with command lines? You can find instructions on this page Updating repositories and tools — nRF Connect SDK 2.5.1 documentation (nordicsemi.com).

Best regards,

Charlie

[JRSN]

Hi Charlie,

Thanks for keeping proposing hints.

I wanted to update manually this way, but the nerf directory is not even created by the NSF Connect for Desktop installation proceed. Only the "toolchains", "tmp" and "downloads" directory do exist.

So the first command "git fetch origin" fails (of course even after manually creating the nerf directory since it does not contain the.git

Still hitless ;-(

Regards,

JRSN

[Charlie]

Hi JRSN

Here is what I get after "Open Terminal" and running git commands. How did your "git fetch origin" fails?

Best regards,

Charlie

[JRSN]

Hi Charlie,

I was hoping the release of v2.5.2 would bring a fix for my issue. unfortunately no.

But an assessment might help :

I saw that during the install, the v2.5.2 directory was created but then was deleted beforre the arm-long error message (starting with "There are multiple errors:").

Also, I tried creating the v2.5.2 before trying the install again and did a git init in it. But again, this directory was deleted when the error message was displayed.

By the way, the "git --version" yields in :

git version 2.39.3 (Apple Git-145)

Then I am still blocked from using the development tools.

Don't you have any ideas where this issue comes from ?

Thanks for your help, Charlie

JRSN

[Øyvind]

Hello JRSN, 

Charlie is currently out of office. I will have a look at your case and follow up with our nRF Connect for Desktop team. 

Kind regards,
Øyvind

[JRSN]

Hi Øyvind,

Welcome on this annoying issue. I hope it can be explained and solved.

However I am to give up on trying to develop on this Mac. I need to go forward.

I'll help as much as I can 

Best regards,

JRSN

[Øyvind]

Hi, sorry to hear that this is causing problems on your end. This does seems to be an issue between the MacOS environment and our toolchain bundles. 

Just to understand the issue correctly. You are using the Toolchain Manager in the nRF Connect for Desktop application? Are you also using the VS Code extension? Could you please provide the output from the nRF Connect: Generate support information, from the VS Code - Command Palette?

JRSN said:

git version 2.39.3 (Apple Git-145)

This is a good indication that there could be an issue between OS and toochain bundle. Are you running this command in the nRF Connect terminal, as Charlie referred to in his last comment? The nRF Connect SDK should run in a sandbox environment when installing through the Toolchain Manager and opening Terminal through the same GUI. 

You can also open this environment in the VS Code terminal (I'm currently on Windows).

I will have access to my Macbook Air M2 later today to provide more guidance on this.