OPEN FOLDER IN SEGGER EMBEDDED STUDIO FOR FREE
OPEN FOLDER IN SEGGER EMBEDDED STUDIO SERIES
OPEN FOLDER IN SEGGER EMBEDDED STUDIO WINDOWS

OPEN FOLDER IN SEGGER EMBEDDED STUDIO WINDOWS

These instructions are for a typical installation into the C drive on Windows 10, so may need slight modification for other circumstances - SES is cross platform. Otherwise follow the instructions below Working with SDK v12.3.0 in SES by Importing Keil Projects If you are happy with the other development tools - Keil and IAR are also well respected - then you can work with nRF51 or nRF52 devices.If you want to use Segger SES, stick to the nRF52 devices, not nRF51, for fully supported development.

OPEN FOLDER IN SEGGER EMBEDDED STUDIO SERIES

Suggestions for anyone else contemplating Nordic nRF series development: But really Nordic should release a 12.4 of their SDK with SES support or add nRF51 projects to their latest SDK with SES projects ready for use if they want to keep developers onboard. I've now successfully built and linked the blinky and ble_app_hrs projects in the examples_segger folder of the github project. He had posted what he claims is the correct set of instructions for conversion from Keil projects to Segger, but more importantly had done the work for several projects and put it all on github. Down at the bottom of the comments was one from a user called secondbest, who claimed there was a solution in another thread. Eventually found a blog post 'Segger Embedded Studio - A Cross Platform IDE' by Hung Bui from Oct 2016 that was supposed to help but didn't. Plenty of similar problems but no real solutions. Linking before BlinkingД«ack to the forums. Now I was down to the classic getting LEDs to blink on a micro, and still having linking errors.

So I started again with blinky but without the Softdevice (the protocol stack, including Bluetooth, which is provided as precompiled hex for each situation), and is a source of complication for the linker because you have to combine two hex files. So I started again with blinky, and failed to get it to link. I started with the example from the video, 'ble_app_hrs' (third mistake) and failed to get it to link. Nordic bounce you around between the Getting Started Guide, the infocenter, the dev kit user guide, videos on SES, their discussion forumsВ and other Segger's own pages. I'm used to a bit of pain when it comes to bringing up a new board, it's expected even in a dev kit which should be tested and have good instructions. Lots of people in their forums and comments on Nordic's own blog posts have been having basic linker problems over the last three years, and most of these do not have satisfactory solutions.

Worse, sometimes they don't match up with the current version of Segger (even though they say the best version is the latest one) and just don't work. These instructions are long and complicated, and in some areas vague. Instead, Nordic provide instructions for converting Keil projects to Segger ones. And since Segger has only been the preferred IDE since nRF5 SDK v14.1, Nordic's examples do not include Segger projects for v12.3 and therefore there are no example nRF51 examples with Segger projects provided. The latest nRF5 SDK is version 16, but it doesn't support nRF51, you have to go back to version 12.3 to get nRF51 support. Setting upДЄs soon as you start working through Nordic's instructions, it becomes apparent that they have left the nRF51 behind and are only really interested in the nRF52.

Since the nRF51-DK comes with a Segger J-Link debugger chip built inВ and I had previously noted that Segger seemed to be one of the premium brands for ARM Cortex IDEs and debuggers, with matching costs, Segger SES seemed to be the right choice of IDE.

OPEN FOLDER IN SEGGER EMBEDDED STUDIO FOR FREE

While they also provide support for Keil, IAR, and GNU/GCC, the agreement with Segger is that they will licence it for free for use with Nordic chips. Nordic's Getting Started Guide v1.3, which covers the nRF51 DK, recommends Segger SES as the preferred development enviroment and is supported by Nordic. I decided I didn't need the feature of the nRF52/Cortex M4, which was my first mistake.

In comparison, the later nRF52 series are M4 based, more capable but more expensive. It uses the nRF51422 which is Cortex M0 based, so I thought it would be a good way to do some M0 development work. The Development Kit comes in a handy sized board which only needs micro USB for power and data, and has a built in SEGGER JLink debug chip, as well as 4 user buttons and LEDs, and all the usual ports. The nRF51 is recent enough to be supported by a mature development environment and to have lots of others try it out before me.

Open folder in segger embedded studio