nRF9160 development on MacOS

[pemar13]

Hi

Why is Mac OS no longer listed as a supported operating system for the nRF Connect SDK (see http://developer.nordicsemi.com/nRF_Connect_SDK/doc/0.3.0/nrf/gs_ins_os.html)?

The setup of a MacOS-based development system is described in the latest version v0.9.0 of the Getting Started Assistant in the latest version v2.6.2 of nRF Connect for MacOS.

Following this description it is possible to get development using Segger Embedded Studio for Nordic v 4.16 to work assuming one finds a suitable version of ncs; the recommendation of using tagged releases leaves you with v0.3.0 from December, which, besides being far behind, doesn't work well. I hope a new tagged release is due in the coming days (before the end of the month).

The problem I have is getting the command-line version of development using cmake and ninja to work (runs find under Windows). The command ninja flash gives the error "[Errno 2] No such file or directory: 'nrfjprog': 'nrfjprog'".

I have "installed" the latest version of the nRF5 Command Line Tools (https://www.nordicsemi.com/?sc_itemid=%7B56868165-9553-444D-AA57-15BDE1BF6B49%7D, made sure the path is accessible from the terminal window I run in, and installed the latest version of the J-Link software (https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack) but this is obviously not sufficient although it is for Windows.

What else should I do?

Best regards,

per

[Sigurd]

Hi,

pemar13 said:

Why is Mac OS no longer listed as a supported operating system for the nRF Connect SDK (see http://developer.nordicsemi.com/nRF_Connect_SDK/doc/0.3.0/nrf/gs_ins_os.html)?

Since we have macOS support for SES Nordic edition, and Zephyr project support macOS, I believe that nRF Connect SDK should also support macOS.  This would then be a documentation bug, but I will check internally to confirm it.

pemar13 said:

the recommendation of using tagged releases leaves you with v0.3.0 from December, which, besides being far behind, doesn't work well. I hope a new tagged release is due in the coming days (before the end of the month).

We are in the process of releasing v0.4.0. I recommend checking out the 0.4.0 when that comes, as for now, you should either use master branch or the v0.4.0-rc1 tag.

pemar13 said:

made sure the path is accessible from the terminal window I run in

Are you able to use nrfjprog in a normal terminal window? Try nrfjprog -v

[pemar13]

Hi!

Sorry for the delay in answering.

Thank you for checking about macOS support. Since it is one of your great advantages, I hope its just a temporary miss.

Yes, I can run nrfjprog in a normal terminal window. It reports 6.44g.

I could of course perform the installation all over again, but I would like to know that the listed steps I have taken should be sufficient. Is there a particular order in which things should be done?

Best regards,

Per

[Sigurd]

Hi,

pemar13 said:

Thank you for checking about macOS support. Since it is one of your great advantages, I hope its just a temporary miss.

Yes, it's just a matter of adding the installation instructions for the toolchain for macOS.

pemar13 said:

I could of course perform the installation all over again, but I would like to know that the listed steps I have taken should be sufficient. Is there a particular order in which things should be done?

I don't think the order of things should matter for this. Could you try with latest code(master) on the nRF Connect SDK ? 

 

[pemar13]

Hi Sigurd!

I'm sorry that my feedback to your comments are so late. I am currently mostly working from within Windows, so the MAC issue doesn't have the highest priority at the moment, but I will get back to you after reinstalling everything A.S.A.P.

Best regards,

Per

[Sigurd]

Hi,

Nothing to worry about. We have released v4.0.0 now, so I recommend using that tag.

cd ncs/nrf
git checkout master
git pull
git checkout v0.4.0
west update

We have also update the docs with support for macOS. See this link.