This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

So we made a decision to buy the dev kit, but then what? ( mac)

FormerMember
FormerMember

I am spending the last 3 days trying to make sure somebody on this plant made it using a mac. Write a simple program and flash it to the DK. (before we make our own pcb)

I was able to find multiple questions about mac, without a single clear answer how exactly you do that. I find only promotions to this Segger software (that looks like something from 1980)

There was 1 guy who made it using command line, and his way seems like hell.

Do you have an official guide to somebody who pay for your product using a mac ?

  1. Where do I write my code? the actual code that I can compile for the chip ? can I use Xcode?
  2. I have the DK board, how do I flash it ?

Nordic, there are tens of millions mac users in this world, they really want to use your chip, but I found that all of them chose to give up because there is no clear way to do that.

Parents
  • Xcode is the IDE for Mac OS applications, not for embedded applications. The nRF does not run Mac OS.

    Segger Studio and Eclipse seem to be the most popular IDE's for that run on Mac OS. There is a discussion of the options here: devzone.nordicsemi.com/.../

    You should download the current SDK for your development board which will have all the necessary ARM support libraries, drivers, softdevices and numerous example applications you can try out. Most if not all have pre-compiled hex files you can just flash on the board as you get used to the environment.

    The most user friendly application for flashing the dev board is nRFgo Studio though it is a windows app, there is an example on github for running it on a mac. See here: github.com/.../Getting-Started-with-nRF-Studio-Go-on-OSX-and-Linux

    In addition there are a variety of command line utilities for Mac. See here: devzone.nordicsemi.com/.../

  • Xcode is clang these days, not GCC. And you can blame Apple for the fact it's now not possible to use it for embedded development and other languages easily. They used to support plugins, proper documented support, so people could extend it, that all disappeared around Xcode 3 when it became their closed product. People do add things for cross compilation, but they are hacks, they require reverse-engineering the Xcode support bundles and they break every time there's a new release of Xcode.

    It is a shame because it is quite a nice IDE and the toolchains are a separate part of it, but Apple stopped supporting 3rd party toolchains and so we don't get to use it.

Reply
  • Xcode is clang these days, not GCC. And you can blame Apple for the fact it's now not possible to use it for embedded development and other languages easily. They used to support plugins, proper documented support, so people could extend it, that all disappeared around Xcode 3 when it became their closed product. People do add things for cross compilation, but they are hacks, they require reverse-engineering the Xcode support bundles and they break every time there's a new release of Xcode.

    It is a shame because it is quite a nice IDE and the toolchains are a separate part of it, but Apple stopped supporting 3rd party toolchains and so we don't get to use it.

Children
No Data
Related