Bovendien werden al snel de regels van de App Store (App Store Review Guideline 3.1.2a) erbij gepakt, waaruit blijkt dat de wijziging van Notability überhaupt niet mag: Met name het idee dat bestaande gebruikers moesten gaan betalen voor functies waar ze al eerder voor hadden betaald, schoot bij veel gebruikers in het verkeerde keelgat. Deze aankopen zouden met de komst van dit abonnementsmodel komen te vervallen. The nRF51 is recent enough to be supported by a mature development environment and to have lots of others try it out before me.Deze wijziging is opvallend, omdat Notability voorheen een betaalde app was met enkele ingebouwde in-app aankopen voor extra functies. 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. It uses the nRF51422 which is Cortex M0 based, so I thought it would be a good way to do some M0 development work.
#Noteabilitypro tutorial series#
In comparison, the later nRF52 series are M4 based, more capable but more expensive. I decided I didn't need the feature of the nRF52/Cortex M4, which was my first mistake. 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.
#Noteabilitypro tutorial 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. 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. 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. 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. 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.
Instead, Nordic provide instructions for converting Keil projects to Segger ones. These instructions are long and complicated, and in some areas vague. 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. 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. 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. 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 started with the example from the video, 'ble_app_hrs' (third mistake) and failed to get it to link. So I started again with blinky, and failed to get it to link. 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.
Now I was down to the classic getting LEDs to blink on a micro, and still having linking errors.
Linking before Blinkingīack to the forums.
Plenty of similar problems but no real solutions. 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.
0 kommentar(er)
