Getting started with EWARM 6.7 and nRF51822

RE: Getting started with EWARM 6.7 and nRF51822

Vidar Berg — Wed, 14 Jan 2015 11:26:52 GMT

PCA10028 is the board name for the new nRF51 DK kit, and PCA10031 is the board name for the nRF51 dongle you're using.

The above boards are pretty much identical besides the form factor. Both have an on-board Segger j-link lite programmer. Thus, not requiring any external programmer, just plug it in an USB port and start programming.

I see you prefer to use something else than Keil, but I would just like to mention that you can use the free 32K code limited license which is sufficient for running our SDK examples. The softdevice is not affected by this limitation as it's provided as a pre-compiled binary.

I don't have much experience with IAR myself, but I see there's at least one IAR example in this path: ..SDK_v6_1_0\nrf51822\Board\nrf6310\s110\ble_app_hrs\iar. I guess this can be used as a template for your own project.

For GCC and GDB you may want to have a look at this blog post

RE: Getting started with EWARM 6.7 and nRF51822

Matt Barr — Fri, 12 Dec 2014 19:00:56 GMT

Hopefully someone from Nordic will help you with the 6.1.0 SDK, it seems a reasonable request given the absence of IAR support in the new 7.x.x SDKs. In general things can be made to work with IAR but direct support is sparse, Keil definitely seems to be the preferred platform. After getting IAR projects set up initially, it really hasn't been difficult or time consuming to keep up with the SDK updates.

RE: Getting started with EWARM 6.7 and nRF51822

Steven Grunza — Fri, 12 Dec 2014 15:40:43 GMT

Are there any plans to actually support IAR in SDK 7 and later? If not, could you please make the full SDK 6.latest available? I've spent almost 20 hours trying to get to the point where I can use a modern IDE to build code and debug. The closest I've come is a DOS command line make and text-mode gdb. The Eclipse instructions in the app note don't work because they were written for the structure of pre-SDK 7. There are no IAR projects in SDK 7 and I don't have the Keil tools.

The hardware of the nRF51822 is ideal for my project but I don't know if this state of churn with the software tools will be acceptable.

RE: Getting started with EWARM 6.7 and nRF51822

Matt Barr — Fri, 12 Dec 2014 00:55:36 GMT

Here you'll find a link to ble_app_hrs.zip from the 6.1.0 SDK with a working IAR project and some other IAR-related info. I still find the earlier SDK downloads available associated with older nrf51422/822 DK product keys, but I don't think you really need this. Using the 7.1.0 SDK you should be able to point to the app and SDK source files, and make appropriate changes to compiler include paths and definitions. Basically add the iar/ project to examples/ble_peripheral/ble_app_hrs/pca10031/s110 in the 7.1.0 SDK, get it set up like the arm project. You can see the project setup in plain text in the Keil project file, or you could install the Keil MDK and use that to browse the project setup. Depending on the softdevice version used, you may have to change the .icf file. Hope this helps.

RE: Getting started with EWARM 6.7 and nRF51822

Steven Grunza — Thu, 11 Dec 2014 21:42:56 GMT

How can I get the 6.1.0 IAR example project setups? I've been looking all any SDK before the SDK_7 changes and haven't found anything yet.

RE: Getting started with EWARM 6.7 and nRF51822

Matt Barr — Thu, 11 Dec 2014 21:29:57 GMT

PCA10028 is the relatively new nRF51-DK board that uses NRF51422-QFAC with 32k RAM. It is supported by the new 7.1.0 SDK. This SDK does not contain example IAR projects, but between the 6.1.0 IAR example project setups and 7.1.0 example project source code it didn't require too much effort to get IAR working with the new DK, SDK and softdevices. I've not used the smart beacon kit, hopefully the situation is the same.

Here is an IAR project for examples/ble_peripheral/ble_app_hrs/pca10031/s110 in the 7.1.0 SDK. I do not have PCA10031, this was tested with PCA10028 by changing the compiler board type definition. See the included README.txt file for other details. Again, I hope this helps.