Incomplete installation on MacOS, file permission issue ?

RE: Incomplete installation on MacOS, file permission issue ?

Øyvind — Tue, 05 Mar 2024 09:19:01 GMT

[quote user="JRSN"]

Thanks for your help and the one of Charlie too.

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

[/quote]

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

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Sat, 24 Feb 2024 10:12:02 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

Øyvind — Thu, 22 Feb 2024 10:16:41 GMT

[quote user="JRSN"] once the installation process has failed, only the "Install" button remains visible (no "First steps" and no "Open VS Code" buttons)[/quote]

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.

[quote user="JRSN"]Thanks for reminding me that the "git version" command should be issued from nRF Connect for Desktop's terminal.[/quote]

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

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Wed, 21 Feb 2024 21:01:40 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

Øyvind — Wed, 21 Feb 2024 09:07:53 GMT

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?

[quote user="JRSN"]git version 2.39.3 (Apple Git-145)[/quote]

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.

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Tue, 20 Feb 2024 18:49:36 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

Øyvind — Tue, 20 Feb 2024 08:41:07 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Thu, 15 Feb 2024 06:29:38 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

Charlie — Tue, 23 Jan 2024 08:31:21 GMT

Hi JRSN

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

Best regards,

Charlie

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Sat, 20 Jan 2024 09:34:18 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

Charlie — Mon, 15 Jan 2024 10:01:05 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Thu, 11 Jan 2024 18:38:52 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

Charlie — Thu, 11 Jan 2024 08:54:44 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Wed, 10 Jan 2024 20:43:31 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

Charlie — Tue, 09 Jan 2024 09:22:09 GMT

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

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Mon, 08 Jan 2024 20:55:54 GMT

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

devzone.nordicsemi.com/.../ErrorPanel_5F00_2024_2D00_01_2D00_08_2D00_21_2D00_49.txt devzone.nordicsemi.com/.../LogFile_5F00_2024_2D00_01_2D00_08_5F00_21_2D00_51.txt

Thanks in advance

Regards

JRSN

RE: Incomplete installation on MacOS, file permission issue ?

Charlie — Mon, 08 Jan 2024 10:41:38 GMT

Hi Rgds,

Sorry to hear the problem still exists. Let's collect a bit more information from your setup and installation process.

From the above page, you can click "create system report" to generate a report about your system and share it here.

I assume you have turned on the "VERBOSE LOGGING" switch. You can rerun installing nRF Connect SDK v2.5.1, then click "OPEN LOG FILE", a detailed log file will open and you can share it here.

Best regards,

Charlie

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Sat, 06 Jan 2024 20:07:17 GMT

Hi Charlie,

I have posted an update. Would it be useful to better understand the issue and solve it ?

TIA for any help

Rgds

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Sat, 06 Jan 2024 16:30:29 GMT

Hi all,

I had put my development on hold, hoping a new release would solve this issue.

But since I cannot wait any longer I tried again.

It seems Nrf Connect for desktop is more verbose and I got the following error messages.

I have tried to reinstall everything from scratch with Admin rights attached to my account, no way to have it work, again :-(

Is it of any helps to solve my issues .

Again, any support for this nice community would be much appreciated

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

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: 50% (4054/8086) Updating files: 51% (4124/8086) Updating files: 52% (4205/8086) Updating files: 53% (4286/8086) Updating files: 54% (4367/8086) Updating files: 55% (4448/8086) Updating files: 56% (4529/8086) Updating files: 57% (4610/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'.

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

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

RE: Incomplete installation on MacOS, file permission issue ?

Charlie — Thu, 07 Dec 2023 11:42:01 GMT

Ok, I also run out of idea now.

Do you have any chance to test on another Mac?

Maybe this will help to do some comparison.

Best regards,

Charlie

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Wed, 06 Dec 2023 21:02:31 GMT

Hi Charlie,

I really value your continuous interest in this issue. Thanks !

I have tried "pip3 install west" under my, admin enabled, account, then deletion of the nordic nordic directory together with the nRF Connect for Desktop.

However, the reinstallation from the nRF Connect for Desktop still yields in an empty v2.5.0 directory.

And from within the VS Studio Code nRF extension, the toolchain installation seems to succeed but the SDK installation stil fails.

I am hintless !

RE: Incomplete installation on MacOS, file permission issue ?

Charlie — Wed, 06 Dec 2023 09:24:26 GMT

Ok, could you try the following command to update to the latest version of west?

pip3 install west

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Tue, 05 Dec 2023 21:06:58 GMT

Hi again,

I might have made one good move

I have deleted the Nordic directory and then, from within VS Studio code, I have tried to install the toolchain and then the SDK

But when trying to install the SDK, I get an error ("SDK installation failed"), the v2.5.0 directory remains empty and I get these error messages :

...

Updating files: 100% (8223/8223), 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.99-dev1/.west/manifest-tmp/west.yml'))

Is this of any helps for someone ?

RE: Incomplete installation on MacOS, file permission issue ?

JRSN — Tue, 05 Dec 2023 20:46:12 GMT

Hi Charlie,

Yes, this is what I can see when logged in the root account after the "root installation" but when under my account and after the installation from my account, the "copy a sample" is missing

So, still at pain on this subject

Thank you In Advance

JRSN

RE: Incomplete installation on MacOS, file permission issue ?

Charlie — Tue, 05 Dec 2023 12:27:40 GMT

Hi TIA,

I have installed the NCS under opt/ncs folder.

I can see and click on "Copy a sample". Do you have any screenshots or error reminders that can show?

Best regards,

Charlie