• State Verified Answer
  • +2 person also asked this people also asked this
  • Replies 7 replies
  • Subscribers 88 subscribers
  • Views 3855 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 228073
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

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

Parents
  • 0

    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

  • 0 in reply to pemar13

    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 ? 

     

  • 0 in reply to Sigurd

    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

  • 0 in reply to pemar13

    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.

Reply Children
  • +1 in reply to Sigurd

    Hi again!

    So I finally got around to try again. In the end, it turns out there was only one thing wrong…

    I basically followed the steps in your macOS guide, i.e., preparing for Zephyr, installing the GNU Arm Embedded toolchain, cloning ncs release v0.4.0, “installing” Segger Embedded Studio ARM v416 Nordic, and installing JLink_MacOSX_V644i.

    At this stage building and programming using Segger Embedded Studio works fine.

    After “installing” nRF-Command-Line-Tools_9_8_1_OSX and setting up a permanent path for bash to the folders nrfjprog, ninja flash fails as before whereas running nrfjprog -v results in the expected lines: ‘nrfjprog version: 9.8.1’ and ‘JLinkARM.dll version: 6.44i’.

    The reason for this must be that ninja doesn’t know the path to nrfjprog. Indeed, manual programming using ‘nrfjprog --program …/build/zephyr/zephyr.hex -f NRF91 --sectorerase' works fine.

    To solve the path issue, I created a symlink to nrfjprog in /usr/local/bin by executing ‘ln -s /path/to/nrfjprog/nrfjprog /usr/local/bin/nrfjprog’.

    Now things work.

    Best regards,

    Per

Related
Terms of service