• State Verified Answer
  • Replies 5 replies
  • Subscribers 62 subscribers
  • Views 2158 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 115011
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Is the getting started guide for nRF52 DK not for Rev 0.9.0?

Morten

When i follow the Getting Started guide for the nRF52 DK at point 5 the led (led 1) does not start pulsating and I do not get contact with my phone. I tried to upload the HRM from the optional demos but it look like this demo is not functioning either.

The dev kit shows up as JLINK in windows file explorer. When I try the optional demos the hex loads, then the JLINK unmounts and mounts again but the hex file has dissapared, and the led 1 ligth does not light up as described in the readme file.

I am wondering if this is because I have Rev 0.9.0 of the dev kit or if there is something wrong with my board?

Edit: After lots of truble, trial and error and crashing nRF go Studio I managed to program the Dev Kit using SDK 11. Still unknown reason for why the demo did not work out of the box.

Edit2: Clearified the Dev Kit Revision and SDK version.

  • 0

    Hi,

    The latest SDK can be found at developer.nordicsemi.com/, I recommend using nRF5 SDK 11. In SDK 11 we merged the SDKs for nRF51 and nRF52, under the new name nRF5 SDK. However if you look at developer.nordisemi.com you will see the old nRF52 SDK on the front page, I get that this can be a little confusing and will forward this to see if we can improve clarity. However your issue is not related to SDK, as the files you mention are precompiled.

    The files are intended to be dragged and dropped into the J-Link drive that is automatically mounted when you connect the board, nRFGo studio and nrfjprog should not be needed.

    I also recommend using the command line tools, in particular nrfjprog to flash your board, as I find it to be a lot more rugged. Nrfjprog can also be called directly from Keil, meaning fewer programs on your taskbar, setup of nrfjprog and integration is shown in this blogpost.

    The next thing that is prone to fail is the J-Link driver, these are found in the software and documentation pack and can be downloaded from SEGGER, the latest stable version usually works. Most users that experience trouble with this have installed other IDEs and programming tools for other microcontroller environments, for example Atmel Studio and Simplicity Studio. Upgrading the J-Link firmware might in rare cases cause issues in these programs.

    Best regards,

    Øyvind

  • 0 in reply to Øyvind Karlsen

    Thanks for a quick reply, i have updated my question with revision number for the Dev kit and SDK version, However your answer does not explain why the Getting started guide does not work out of the box. Do you know if rev 0.9.0 of the dev kit does not ship with the code or somthing similar?

  • 0 in reply to Øyvind Karlsen

    Were you trying to program the hex file using nRFGo studio?

  • 0 in reply to Øyvind Karlsen

    No, I was trying point 5 of the getting started guide, no need for any programming according to the guide. Then I tried compiling and programming using keil uVision/nRFgo and that is working for the examples. nRFgo was used to flash a softDevice/check for softDevice present on the dev kit.

  • 0

    This is working as intended for V1.1.0 and V1.0.1, however 0.9 does not contain any firmware and will not work out of the box like the getting started page indicates. The link to the guide is not supplied with the 0.9 version but I see how users could get confused. I will look into updating the documentation.

Related