Tools for OS X Development

RE: Tools for OS X Development

FormerMember — Fri, 31 May 2019 12:58:19 GMT

Thank you, I find your article very useful, I will reffer to it when I will use this info at my job

RE: Tools for OS X Development

Torsten Robitzki — Wed, 28 Jan 2015 12:30:35 GMT

We using OS/X as development plattform too. Note, that you can use the JLinkExe tool provided by segger to flash devices. We use cmake and provide commands like make device_name.flash, that build the software and flash it to the device by creating a small script and execute that script by JLinkExe.

RE: Tools for OS X Development

Peter — Tue, 20 Jan 2015 17:18:22 GMT

Mike,

Actually, for the nRF51x22, use the Executable->Hello World ARM Cortex-M C/C++ Project->Cross ARM GCC project template.
Coupling in the SDK is the part I'm least sure about. I added the SDK as a source path and then excluded the files (components) I wasn't interested in. It's a little time consuming, and I'm not sure if it's the best way--I'm going to make a separate blog article on that.
I've always used 7.x just because it's the latest--but I'm sure someone from Nordic could help you with this question.
That's because I forgot (doh!) to include the toolchain in my list of tools. Install the GNU ARM toolchain according to the instructions from the GNU ARM Eclipse Plugins.

RE: Tools for OS X Development

RK — Tue, 20 Jan 2015 09:59:56 GMT

nrfjprog does work with the v7.x softdevice, and has since since last year's August release. However since around that time you have been required to tell it which softdevice you're using using the -S or --softdeviceversion switch as well as the file path to the hex file. The changes in the way the softdevice was packed (no CLENR0) mean it's no-longer possible to deduce the load addresses from the image.

nrfjprog -h

gives you current command-line arguments and

nrfjprog -V

as well as listing the version, gives you the softdevices versions supported for use with the -S switch.

RE: Tools for OS X Development

Jock Murphy — Sat, 17 Jan 2015 01:21:54 GMT

I am not sure I would describe Roland King's version of nrfjprog as being similar, as the command line arguments are radically different. Much better IMHO, but it is going to take more than simple tweak to use the two command line tools.

Unfortunately there is a bug in RK's version of nrfjprog that prevents it from working with the v7 S110 softdevice, nor does he provide the source to his tool. So your only recourse is to fall back to the RKNRFGO GUI tool instead.

RE: Tools for OS X Development

Mike Wirth — Thu, 15 Jan 2015 21:33:07 GMT

Peter,

Couple quick questions (Sorry if they're too basic)

When creating an nRF C project, I have a choice of using the "Cross" or Mac OS X GCC toolchains. Your recommendation?
Have the appropriate Nordic SDKs. (Have been doing Keil MDK development on the nRF51 for some time.) What's your "best practice" in terms of coupling one of them into a project? Just add their path into the project's Include properties?
While I'm on the subject of Nordic SDKs, can you (or anyone else) comment on the differences between the currently recommended version 6.2.1 on the Nordic site for "regular" development, and the 7.x version on Nordic mbed side.
Got a "/bin/sh: arm-none-eabi-gcc: command not found" error on building. OK, need to add the appropriate path to my bin path. What and where? (I know, I could find this out myself, but it would be useful to add it to your synopsis :-)

RE: Tools for OS X Development

Mike Wirth — Thu, 15 Jan 2015 05:19:11 GMT

Peter,

Installation process worked flawlessly on my Yosemite MacBook Core 2 Duo. Thanks. Look forward to trying this out (as an alternative to Keil MDK-Lite on Parallels with Win7 VM).

Mike

RE: Tools for OS X Development

David Edwin — Fri, 09 Jan 2015 15:10:18 GMT

Crossworks is also an option for OS X development. It is not a free option but it is a reasonable option.