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,

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.

[JRSN]

Hi Øyvind,

Thanks for reminding me that the "git version" command should be issued from nRF Connect for Desktop's terminal.

However, once the installation process has failed, only the "Install" button remains visible (no "First steps" and no "Open VS Code" buttons) and the drop down menu is not active (cannot be dropped down).

Ill keep on help as long as I can

Best rgds

JRSN

[Øyvind]

JRSN said:

once the installation process has failed, only the "Install" button remains visible (no "First steps" and no "Open VS Code" buttons)

One workaround that I have used before when I encountered a similar issue, was to open VS Code and from the command palette run nRF Connect: Uninstall SDK. 

Then from the drop down list, hopefully, NCS v2.5.1 will be visible and you can choose this one. 

JRSN said:

Thanks for reminding me that the "git version" command should be issued from nRF Connect for Desktop's terminal.

What does git --version return from this terminal? Here is my normal terminal vs nRF Connect for Desktop

[JRSN]

Hi Øyvind,

A short message to tell you that I am now using another Mac for development, fully erased and reset.

The nRF Connect for Desktop went through nicely and I can now see the samples listed when trying to create a new application from Nordic's nRF samples.

Hence I reached the point I was wanting to be back to for months.

I suspect the previous development Mac had to many years of incremental installs, configurations, different software releases and file privileges variations.

Thanks for your help and the one of Charlie too.

I really value Nordic's support in such hindering situations.

Best regards

JRSN

[Øyvind]

JRSN said:

Thanks for your help and the one of Charlie too.

I really value Nordic's support in such hindering situations.

My apologies for the late reply. I am really happy to hear that you found the solution to your issue. I agree that "many years of incremental installs, configurations, different software releases and file privileges variations" could be the root cause of the issue. 

Hope you are able to develop without any issues from here

Kind regards,
Øyvind