nRF Connect Installation on macOS (Automatic Installation)

[alwalker]

I have not been able to create a stable development environment in macOS Monterey using the automatic installation process. 

In order to better understand and document the issues, I am going to do four separate installations for comparison.

MacBook Pro 1:  Manual Installation            

https://devzone.nordicsemi.com/f/nordic-q-a/88500/nrf-connect-installation-on-macos-manual-installation

MacBook Pro 2:  Automatic installation

Linux Ubuntu:     Manual Installation

Windows 11:       Automatic installation

This thread will cover the second case, the automatic installation on macOS. I will create separate support tickets for the other cases and provide links.

[PieterJericho]

Hi I have had the exact same experience on every point. Waited hours for memfault to finish to no avail. I could see the git fetch command actually running, but not performing any CPU usage.

I still have the Shell initialization conflicts nRF Connect terminal profile issue. Also performed the automatic install (followed by update SDK and update toolchain). I did not put any environment variables anywhere, in fact opening a shell the environment is pristine with nothing related to zephyr or nordic.

[PieterJericho]

I actually managed to get everything working. I still get the warning about the terminal profile, though it seems to be benign.

The only thing not working is KConfig which gives the error "Unable to find Kconfig information to display. Please select a Kconfig file first.", although guiconfig and menuconfig works.

[alwalker]

Yes, I've had KConfig errors with previous attempts at doing the automatic installation process on macOS, as well as CMake errors. So far the macOS manual installation and Win 11 automatic installation appear to be ok. Still have Linux to try.

[Marte Myrvold]

Hi,

We have had some other reports about the memfault issue as well, and the developers have been notified of it.

Regarding the shell initialization issue the developers have been unable to reproduce this so far. MacOS use zsh as the standard shell, so it is possible that the instructions to look for bashrc or bash_profile on macOS will not catch the issue, as it is not set there. However, regardless of what the inherited environment variables were, the extension will set the variables that fit with the active toolchain and SDK. Issues might only raise within the integrated when the "nRF Connect" terminal profile is used. You can check the variables by typing env and see if something looks incorrect there. However, if you rarely use the integrated terminal to invoke west or cmake then the error message can just be ignored.

Did you build the project successfully before the Kconfig error? This error could be given if the build is broken or incomplete. The Kconfig extension is not installed in the support information, so it is not possible to get information that might help with this error from that. If you are still seeing the error, please generate new support information.

Best regards,

Marte

[alwalker]

Hi Marte,

Thanks very much, this is the result from executing env when opening Terminal from the nRF Connect SDK:

220610 macOS Bash Environment.rtf

(Computer and user names anonymised for security reasons)

Is there anything that you wouldn't expect to see please?

I had problems with Kconfig previously using the zsh shell, so I don't think this is related to which terminal shell I'm using.Please see existing open ticket:

https://devzone.nordicsemi.com/f/nordic-q-a/85101/implementing-developing-bluetooth-low-energy-products-using-nrf-connect-video-on-nrf5340-dk

My current project is the LE Audio demo on the nRF5340 Audio DK board, which I'm executing from Windows Command Prompt/Bash using the supplied Python script. I am focussed on getting this demo up and running (so far only achieved on Windows 11, but with glitching audio transmission/reception) before I go back to developing in VS Code.

Kind regards,

Al

[Marte Myrvold]

Hi,

Are you able to build the project successfully? Because if not, that might explain the Kconfig error.

Best regard,

Marte

[PieterJericho]

Hi alwalker Yes I can build and run successfully.

In fact the guiconfig/menuconfig works fine as well. I do get that issue below, which might be related.

The file definitely exists and changes to it and doing pristine build definitely take effect.

It is only KConfig itself (the Nrf provided built-in editor) not working on M1 Mac.