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 looking again at this issue. Much appreciated !

*************** Here is the System report

# nRFConnect System Report - 2024-01-08T20-44-13.311Z

- System: Apple Inc. MacBookPro15,1
- BIOS: Apple Inc. 2020.61.1.0.0
- CPU: 1 x Intel Core i7-8750H 2.2 GHz 12 cores (6 physical)
- Memory: 302.1 MB free of 16 GB total
- Filesystem: /dev/disk1s5s1 (APFS) 931.5 GB 10.6% used

- OS: macOS (14.2.1) darwin x64

- Versions
- kernel: 23.2.0
- git: 2.39.3
- node: 16.17.1
- python:
- python3: 3.9.6
- Connected devices:

****************

Here attached are two files : the content of the error panel and the log file as requested

Fullscreen ErrorPanel_2024-01-08-21-49.txt Download

																																																																									
Error
There are multiple errors:
Failed to clone the repositories: Error: Cloning into '/opt/nordic/ncs/v2.5.1/.west/manifest-tmp'... Note: switching to '87355af5914e498f449b7a68bb5641031a7b8885'.

You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

Updating files: 57% (4629/8086) Updating files: 58% (4690/8086) Updating files: 59% (4771/8086) Updating files: 60% (4852/8086) Updating files: 61% (4933/8086) Updating files: 62% (5014/8086) Updating files: 63% (5095/8086) Updating files: 64% (5176/8086) Updating files: 65% (5256/8086) Updating files: 66% (5337/8086) Updating files: 67% (5418/8086) Updating files: 68% (5499/8086) Updating files: 69% (5580/8086) Updating files: 70% (5661/8086) Updating files: 71% (5742/8086) Updating files: 72% (5822/8086) Updating files: 73% (5903/8086) Updating files: 74% (5984/8086) Updating files: 75% (6065/8086) Updating files: 76% (6146/8086) Updating files: 77% (6227/8086) Updating files: 78% (6308/8086) Updating files: 79% (6388/8086) Updating files: 80% (6469/8086) Updating files: 81% (6550/8086) Updating files: 82% (6631/8086) Updating files: 83% (6712/8086) Updating files: 84% (6793/8086) Updating files: 85% (6874/8086) Updating files: 86% (6954/8086) Updating files: 87% (7035/8086) Updating files: 88% (7116/8086) Updating files: 89% (7197/8086) Updating files: 90% (7278/8086) Updating files: 91% (7359/8086) Updating files: 92% (7440/8086) Updating files: 93% (7520/8086) Updating files: 94% (7601/8086) Updating files: 95% (7682/8086) Updating files: 96% (7763/8086) Updating files: 97% (7844/8086) Updating files: 98% (7925/8086) Updating files: 99% (8006/8086) Updating files: 100% (8086/8086) Updating files: 100% (8086/8086), done. Traceback (most recent call last): File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/manifest.py", line 1296, in init validate(source_data) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/manifest.py", line 474, in validate raise ManifestVersionError(min_version_str) west.manifest.ManifestVersionError: ('0.13', None)

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "/opt/nordic/ncs/toolchains/20d68df7e5/bin/west", line 8, in <module> sys.exit(main()) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/main.py", line 781, in main app.run(argv or sys.argv[1:]) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/main.py", line 106, in run self.run_command(argv) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/main.py", line 336, in run_command cmd.run(args, unknown, self.topdir, manifest=self.manifest) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/commands.py", line 140, in run self.do_run(args, unknown) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/project.py", line 198, in do_run topdir = self.bootstrap(args) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/project.py", line 286, in bootstrap projects = Manifest.from_file(temp_manifest, File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/manifest.py", line 1153, in from_file return Manifest(**kwargs) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/manifest.py", line 1298, in init raise ManifestVersionError(mv.version, file=source_file) from mv west.manifest.ManifestVersionError: ('0.13', PosixPath('/opt/nordic/ncs/v2.5.1/.west/manifest-tmp/west.yml')) Error: Launched process exited with non-zero status: 1

Error: Cloning into '/opt/nordic/ncs/v2.5.1/.west/manifest-tmp'... Note: switching to '87355af5914e498f449b7a68bb5641031a7b8885'.

You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may do so (now or later) by using -c with the switch command. Example:

git switch -c <new-branch-name>

Or undo this operation with:

git switch -

Turn off this advice by setting config variable advice.detachedHead to false

Updating files: 57% (4629/8086) Updating files: 58% (4690/8086) Updating files: 59% (4771/8086) Updating files: 60% (4852/8086) Updating files: 61% (4933/8086) Updating files: 62% (5014/8086) Updating files: 63% (5095/8086) Updating files: 64% (5176/8086) Updating files: 65% (5256/8086) Updating files: 66% (5337/8086) Updating files: 67% (5418/8086) Updating files: 68% (5499/8086) Updating files: 69% (5580/8086) Updating files: 70% (5661/8086) Updating files: 71% (5742/8086) Updating files: 72% (5822/8086) Updating files: 73% (5903/8086) Updating files: 74% (5984/8086) Updating files: 75% (6065/8086) Updating files: 76% (6146/8086) Updating files: 77% (6227/8086) Updating files: 78% (6308/8086) Updating files: 79% (6388/8086) Updating files: 80% (6469/8086) Updating files: 81% (6550/8086) Updating files: 82% (6631/8086) Updating files: 83% (6712/8086) Updating files: 84% (6793/8086) Updating files: 85% (6874/8086) Updating files: 86% (6954/8086) Updating files: 87% (7035/8086) Updating files: 88% (7116/8086) Updating files: 89% (7197/8086) Updating files: 90% (7278/8086) Updating files: 91% (7359/8086) Updating files: 92% (7440/8086) Updating files: 93% (7520/8086) Updating files: 94% (7601/8086) Updating files: 95% (7682/8086) Updating files: 96% (7763/8086) Updating files: 97% (7844/8086) Updating files: 98% (7925/8086) Updating files: 99% (8006/8086) Updating files: 100% (8086/8086) Updating files: 100% (8086/8086), done. Traceback (most recent call last): File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/manifest.py", line 1296, in init validate(source_data) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/manifest.py", line 474, in validate raise ManifestVersionError(min_version_str) west.manifest.ManifestVersionError: ('0.13', None)

The above exception was the direct cause of the following exception:

Traceback (most recent call last): File "/opt/nordic/ncs/toolchains/20d68df7e5/bin/west", line 8, in <module> sys.exit(main()) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/main.py", line 781, in main app.run(argv or sys.argv[1:]) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/main.py", line 106, in run self.run_command(argv) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/main.py", line 336, in run_command cmd.run(args, unknown, self.topdir, manifest=self.manifest) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/commands.py", line 140, in run self.do_run(args, unknown) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/project.py", line 198, in do_run topdir = self.bootstrap(args) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/app/project.py", line 286, in bootstrap projects = Manifest.from_file(temp_manifest, File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/manifest.py", line 1153, in from_file return Manifest(**kwargs) File "/Users/myAccount/Library/Python/3.9/lib/python/site-packages/west/manifest.py", line 1298, in init raise ManifestVersionError(mv.version, file=source_file) from mv west.manifest.ManifestVersionError: ('0.13', PosixPath('/opt/nordic/ncs/v2.5.1/.west/manifest-tmp/west.yml')) Error: Launched process exited with non-zero status: 1

Close

LogFile_2024-01-08_21-51.txt

Thanks in advance

Regards

JRSN

[Charlie]

Hi JRSN,

Thanks for the information. I am still looking for the cause for "Failed to clone the repositories: Error: Cloning into '/opt/nordic/ncs/v2.5.1/.west/manifest-tmp'" error.

Just wondering if you have tested on another network environment like home if you only tested in the office or vice versa?

Another worth trying might be simply testing on a Windows PC to see if the issue also exists.

Best regards,

Charlie

[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