nRF Connect Installation on macOS (Manual Installation)

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

MacBook Pro 2:  Automatic installation

https://devzone.nordicsemi.com/f/nordic-q-a/88566/nrf-connect-installation-on-macos-automatic-installation/editpost?ContentTypeId=0

Linux Ubuntu:     Manual Installation

Windows 11:       Automatic installation

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

Parents
  • For the macOS manual installation process, 

    Get the nRF Connect SDK code

    It says create a folder called ncs to hold all nRF Connect SDK repositories, but doesn't specify a location to create this folder

    Where should this folder be created please?

  • Hi,

    Using the toolchain manager to install the nRF Connect SDK should work on macOS Monterey, and works well on my computer. Perhaps you can elaborate on what is not working? One important note though, is that for programming to work directly form VS Code you need to install the universal version of J-Link Software and Documentation Pack (with both Intel and ARM support in the same package).

    alwalker said:
    Where should this folder be created please?

    I do not believe there is any restrictions on that, as long as your user is allowed to read and write to/from the location that is being used.

  • Hi Al,

    alwalker said:
    After I executed west update I find that the nrf folder is empty:

    It looks like you missed a step. "west config manifest.group-filter +nrf5340_audio" is used to add audio suppor to a SDK you have already checked out. But based on what you wrote you made empty folders and never initialized them (note the command "west init -m github.com/.../sdk-nrf --mr v1.9.99-dev1" in my instructions). So what you saw is expected given this missing step.

    However, now that nRF Connect SDK 2.0.0 is out, you can do this completely differently, as there is no need to check out the 1.9.99-dev1 tag. Simply use the toolchain manger to get 2.0.0, open a terminal from the toolchain manager and that will open a terminal at the location where the SDK is installed (so you see folders like zephyr, nrf, etc). There simply type "west config manifest.group-filter +nrf5340_audio" and then "west update", and you will get the audio repositories downloaded. Note that you will be asked for credentials in order to download the LC3 codec. If you do not have access to it, simply enter dummy user name and password. If you cancel (by ctrl-C), you will abort the update and miss some repositories.

  • Thanks Einar, but I want to download the nRF5340_audio project to my workspace folder to keep al my projects organised. So I would select Open Terminal from nRF Connect SDK and then navigate to the specific folder location Home/workspace/ncs_audio/nrf/

    What should the syntax of the west init statement be in this case please? Something like this?

    west init -m github.com/nrfconnect/sdk-nrf -mr v2.0.0

    Kind regards,

    Al

  • Hi,

    If you want to check out a nRF Connect SDK release to a specific folder then go to that folder and type:

    west init -m https://github.com/nrfconnect/sdk-nrf --mr v2.0.0

    That will make a subfolder with the tag name and download all repos there. You can specify another folder if you like by adding the folder name at the end of the command. You can find details about this under Installing manually.

  • Hi Einar,

    I appear to have the workspace folder structure already initialised for West as I get fatal error messages:

    I then open a new terminal window from nRF Connect SDK and execute the west config and west update instructions there, whilst everything appears to execute ok, I still can't see any project files (see also private ticket for same issues on Windows installation):

    Kind regards,

    Al

  • Hi Al,

    The west configuration is in a hidden folder (.west), and if you have initialized once it you cannot do it again, so you would have to delete the .west folder in this case.

Reply Children
Related