nRF Connect Installation on macOS (Automatic Installation)

I have followed the automatic installation process using the above link, issues encountered:

On first installation of nRF Connect SDK v2.0.0, the installation hung on updating the memfault repository:

Log file ('xxxxxxxx' is user name):

Subsequently updating both the SDK and toolchain seems to fix the issue as the installations complete.

I have installed the universal version of the J-Link software as advised in the manual installation thread. I note that the v2.0.0 SDK does not have the button for opening the SEGGER J-Link that I've seen for previous SDK versions, is this expected please?

Launching VS Code and selected V2.0.0 for both nRF Select SDK and nRF Connect Toolchain, I get an error saying Shell initialization conflicts nRF Connect terminal profile with a link to the following information:

This issue may occur when opening the internal terminal with the nRF Connect profile, which sets the shell environment for the configured SDK and toolchain, but the shell initialization script (e.g. .bashrc) overrides the environment. This can happen if the ZEPHYR_BASE environment variable is set in .bashrc. If there is no need for external terminals to use this variable, we suggest removing this from .bashrc, otherwise it can be moved to .bash_profile or an equivalent script that is only loaded by login shells.

https://nrfconnect.github.io/vscode-nrf-connect/connect/troubleshooting.html#shell-initialization-conflicts-nrf-connect-terminal-profile

I can't find files (with hidden files enabled) called either .bashrc or .bashprofile, what should I be looking for please? I have Bash enabled as the shell in macOS Terminal.

Update: This issue did not occur with the manual installation process.

Kind regards,

Al

I'm just doing the nRF Connect install for the manual installation process, I also had the same issue with the v2.2.0 install hanging on the memfault registry stage.

I notice this line in the nRF Connect log file when updating the toolchain after restarting Toolchain Manager:

2022-06-03T09:55:41.967Z INFO Installed JLink version does not match the provided version (V7.58b)

As with the automatic installation, I installed universal version of the J-Link software which is v7.66b. Is this the reason why the Open SEGGER J-Link button is not shown for the nRF Connect SDK v2.2.0 release please?

Kind regards,

Al

Hi Al,

alwalker said:

I note that the v2.0.0 SDK does not have the button for opening the SEGGER J-Link that I've seen for previous SDK versions, is this expected please?

Yes, as of v2.0.0 SEGGER Embedded Studio has been discontinued, v2.0.0 Release Notes.

alwalker said:

I can't find files (with hidden files enabled) called either .bashrc or .bashprofile, what should I be looking for please?

On macOS .bashrc and .bash_profile should be in your home directory, ~/.

Best regards,

Marte

Hi Marte,

Thanks very much, the only similarly named file I have in my Home directory is .bash_history

It includes several of these pairs of statements, but no indication of when they were executed:

echo ${ZEPHYR_BASE}
exit

Any suggestions please?

Kind regards,

Al

Hi Al,

Have you set the ZEPHYR_BASE environment variable somewhere yourself?

Can you generate support information and upload it here? Open command palette in VS Code and write nRF Connect: Generate Support Information. When you select this the information will be generated in the output terminal. Copy that and upload it here using Insert > Code.

Best regards,

Marte