Migrating development over to MacOS

RE: Migrating development over to MacOS

rolandash — Wed, 25 Sep 2019 07:36:04 GMT

I do not want to interrupt this thread. I have a post here and you can check it out.

If you got any detailed questions you are welcome to comment there.

RE: Migrating development over to MacOS

Nguyen Hoan Hoang — Tue, 24 Sep 2019 16:44:43 GMT

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.

RE: Migrating development over to MacOS

mchartier — Tue, 24 Sep 2019 16:07:21 GMT

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.

RE: Migrating development over to MacOS

Mojo — Tue, 24 Sep 2019 14:56:59 GMT

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

RE: Migrating development over to MacOS

mchartier — Tue, 24 Sep 2019 14:46:39 GMT

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.

RE: Migrating development over to MacOS

Nguyen Hoan Hoang — Mon, 23 Sep 2019 16:32:09 GMT

Interesting, is there a blog or some info on how to achieved it? I am interested to know how.

RE: Migrating development over to MacOS

rolandash — Mon, 23 Sep 2019 16:20:13 GMT

Xcode can create projects with external build system, so yes it can compile nRF SDK, thought It actually does it through external gcc builder. Of course It is can not do real-time debugging, but then we have gdbserver from command line and you basically can do whatever you want.

RE: Migrating development over to MacOS

Nguyen Hoan Hoang — Mon, 23 Sep 2019 01:16:54 GMT

Can you cross compile the nRF SDK or nRFConnect SDK with XCode?

RE: Migrating development over to MacOS

rolandash — Sun, 22 Sep 2019 21:00:54 GMT

Congrats!

"The only minor issues I found so far is that SES on the Mac does not support the dark color theme, and I cannot open two projects at the same time like you can on Windows."

That's why I only use XCode :-)

RE: Migrating development over to MacOS

mchartier — Sun, 22 Sep 2019 18:56:03 GMT

Update: So I have all my 'daily' tools running on the Mac now. The installation went surprisingly well including nrfutil which was a surprise given the comments on the website. I moved my project files from PC to Mac by simply zipping the entire SDK folder on the PC and unzipping on the MAC. No changes were needed to any files to get the project loaded into SES and building. I was quite surprised actually. The only minor issues I found so far is that SES on the Mac does not support the dark color theme, and I cannot open two projects at the same time like you can on Windows.

RE: Migrating development over to MacOS

Mojo — Thu, 19 Sep 2019 19:05:19 GMT

All works on MAC but I prefer Eclipse over all. I work on exclusively and all ARM embedded firmware are done using Eclipse GCC (Nordic, NXP, STM32...). I use this library https://github.com/IOsonata/IOsonata.

RE: Migrating development over to MacOS

rolandash — Thu, 19 Sep 2019 16:13:20 GMT

I do not use SES, nrfjprog, and nrfconnect.

Others work perfect on MacOS.