Migrating development over to MacOS

[mchartier]

It would be great if I could move my project over to the Mac and use one less computer.  But I wonder how well the tools work on MacOS platform. Are there any major limitations using Nordic tools (and Segger tools) on the Mac?

My project was developed on Windows and requires many tools from Nordic and Segger daily including:

• SES
• nrfjprog
• nrfutil
• mergehex
• nrfConnect: power profiler, programmer
• python 2.7

Other tools are required less often. I could probably keep these tools on the Windows system but prefer to move them all to MacOS as well:

• uECC library for generating public/private keys (for DFU)
• gnu toolchain for building uECC
• nRF BLE sniffer

Reading through the documentation on Nordic website it seems all of the tools are supported on the Mac except nrfutil, however the GitHub page for nrfutil seems to indicate nrfutil can be installed on the Mac. Thanks for any insights you have.

[mchartier]

Update #2:  After using the tools a couple days it has become clear to me that SES on Mac is not as mature as the Windows version. Some examples:

• While debugging SES will crash about 1-in-10 times when tapping the stop button.
• No keyboard shortcut for code formatting.
• Right click does not give a pop-up menu. 
• Can't get the build to use multiple cores

None of these are showstoppers for me but just noting this here in case others are interested.

[Mojo]

Have you tried CrossWorks ? SES is a stripped down version of CrossWorks.  May be CrossWorks would be better.

[mchartier]

Thanks for pointing out CrossWorks. It looks like SES is about 1 year behind CrossWorks releases. I searched DevZone for CrossWorks and it seems like few people are trying this approach. I wonder if anyone has a good experience using CrossWorks together with Nordic SDK and Segger JLINK tools. I don't have the time or energy to blaze a new trail here. 

[Nguyen Hoan Hoang]

You can use CrossWorks in place of SES.  The only thing is that it is not free but it allows you to use any JTag while SES is only with JLink.  CrossWorks (SES) uses the latest GCC but with C++ tripped out so if you need to compile C++ it is not fully operational.  However CrossWorks can be easily configured to use with external FULL GCC compiler.