Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

RE: Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

Carl Richard — Thu, 05 Aug 2021 10:44:08 GMT

Good to hear that it works for you now.

Best regards,
Carl Richard

RE: Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

Thomas — Wed, 04 Aug 2021 18:29:28 GMT

There is a typo when proceeding the first step (Install NCS v1.6.0). The link to download a dmg contains an unnecessary colon.

https://developer.nordicsemi.com/.pc-tools/toolchain/ncs-toolchain-v1.6.0-20210701-de414c8.dmg:

It threw this error

Error when reading https://developer.nordicsemi.com/.pc-tools/toolchain/ncs-toolchain-v1.6.0-20210701-de414c8.dmg: net::ERR_NETWORK_IO_SUSPENDED

After modifying the link

https://developer.nordicsemi.com/.pc-tools/toolchain/ncs-toolchain-v1.6.0-20210701-de414c8.dmg

we downloaded the dmg

we found the right directory and placed all the v1.6.0 toolchain elements from the dmg extract,

we used the v1.6.1 terminal and finished the rest of the download.

After restarting the toolchain Manager, we can use the IDE now.

Thanks Carl.

RE: Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

Carl Richard — Tue, 03 Aug 2021 11:56:39 GMT

Hello again!

Edit: this should be fixed now and there should not be any need to download 1.6.0 first. Please report back if the issue persists.

----------

Workaround for the issue is to install NCS v1.6.0 before installing NCS v1.6.1. If NCS v1.6.1 is already installed do the following:
- Install NCS v1.6.0
- Press the dropdown menu besides the 1.6.1 installation and press "Open Terminal"
- Call the following command and wait for it to finish: "./toolchain/ncsmgr/ncsmgr init-ncs"
- Restart the Toolchain Manager

The "Open IDE" button should now be visible for NCS v1.6.1.

Background: the Python symlinks in the NCS 1.6.1 toolchain points to binaries in the 1.6.0 toolchain. I've informed the developers, but due to issues with building the binaries for MacOS it will take some time before a fix is ready.

Best regards,
Carl Richard

RE: Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

Thomas — Tue, 03 Aug 2021 03:10:28 GMT

Reporting the same issue on an Apple M1 with Mac OS Big Sur 11.4
I suspect it's not due to the OS or HW but just in case to help this get resolved. Thanks for getting on this issue Carl!

RE: Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

Tor Kaufmann — Mon, 02 Aug 2021 13:40:29 GMT

Awesome! Looking forward to hearing from you.

RE: Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

Carl Richard — Mon, 02 Aug 2021 11:59:01 GMT

Hello, guys!

Thanks for reaching out. Just wanted to inform you that I just reproduced the issue here and that I'm investigating. Thank you for your patience!

Best regards,
Carl Richard

RE: Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

Tor Kaufmann — Mon, 02 Aug 2021 10:04:44 GMT

+1. Running into the same problem when using Toolchain Manager app from nrF Connect to install nrF Connect SDK v1.6.1

on macOS 10.15.7

Not getting a "Open IDE" button on versions above v1.4.2, however for version v1.4.2 I do

Trying the Update toolchain option from the drop down menu lead to the same error reported by liteyear

No luck trying this way either: similar but solved problem

Where do I go from here?

RE: Using Toolchain Manager on macos to install ncs 1.6.1 results in incomplete install.

liteyear — Fri, 30 Jul 2021 17:18:40 GMT

I tried "Install toolchain" and after an hour it reported an error:

Cannot copy '../../../Cellar/git/2.26.2/share/zsh/site-functions/git-completion.bash' to a subdirectory of itself, '../../../Cellar/git/2.26.2/share/zsh/site-functions/git-completion.bash'.

The log indicates that it completed anyway, but I see no changes in the toolchain directory. Certainly still no sign of ncs and Zephyr.

I guess my fears of this packaged approach are confirmed. Looks like I'm better off going back to the manual method where I end up with a well integrated solution and have a hope of resolving issues, instead of just waiting for hour long automated processes to fail mysteriously leaving GB of redundant files lying around...

Is my experience unusual?