Nordic nRF51-Dongle

The nRF51-Dongle is a development tool for making Bluetooth Smart, ANT and 2.4GHz applications using the nRF51 Series SoCs. It has a standard USB connector and can be plugged directly into a PC USB port. Additionally there is a user-programmable RGB LED and 6 solder pads for GPIO/interface connections.

The kit supports the standard Nordic Software Development Tool-chain using Keil, IAR and GCC. The kit also supports ARM mbed tool-chain for rapid prototyping and development using mbed’s cloud-based IDE and tool-chain with an extensive range of open-source software libraries. Program/Debug options on the kit are Segger J-Link Lite for standard tool-chain and CMSIS-DAP for mbed. The kit gives access to all I/O and interfaces via connectors and has 4 LEDs and 4 buttons which are user-programmable. A range of software examples are available from the nRF51 SDK to support Bluetooth Smart, ANT and 2.4GHz applications.

/media/uploads/gamnes/nrf51-dongle_v1.0.0_information_with_logo.png

Features

OTA-DFU

nRF51 series SoCs support an Over-The-Air Device Firmware Update (OTA-DFU) feature. This allows for wireless updates of application code and/or software stacks.

BLE stack

Nordic Semiconductor provides a wireless protocol stack called the SoftDevice. The SoftDevice is precompiled into a binary image and functionally verified according to the wireless protocol specification, so that all you have to think about is creating the application.

compiled binary size

For the default DK mbed target, any mbed build tools (online IDE, mbed CLI) will put the SoftDevice and the user application together into a binary file intended to program your development kit. Be aware of the SoftDevice size – it adds more than a hundred KB to any compiled binaries.

Further information about the type of Nordic’s target is available in github nRF5 ReadMe.

nRFSniffer

The Nordic nRFSniffer is an application for nRF51 Series Development tools for viewing Bluetooth® Smart communication. The nRFSniffer is a useful tool for learning about, and debugging Bluetooth Smart applications and allows for near real-time display of Bluetooth Smart packets and helps identification and fixing of issues by allowing developers to see what is happening on-air. Additionally, this application allows you to save nRF Sniffer capture files of your application’s Bluetooth Smart link which can be sent to Nordic Technical Support allowing for faster resolution of issues by the support engineers.

The nRF Sniffer application together with Wireshark, a free, opensource protocol analyzer provides a powerful and cost-effective means to analyze Bluetooth Smart communication traffic and events between Nordic devices during the development cycle.

nRF Sniffer and a range of demo apps are available from www.nordicsemi.com

Firmware Update

The latest mbed interface upgrade file for the nRF51822-mkit is:

Version 0218, Minor bug fixes. Added correct MSD content for specific platform.

Source: https://github.com/NordicSemiconductor/CMSIS-DAP/tree/V0218

To update the firmware:

  1. Unplug dongle from the usb.
  2. Press and hold down the reset button and connect to usb while doing so
  3. Dongle should now enumerate as an MSD named "BOOTLOADER"
  4. Copy the firmware binary to the BOOTLOADER drive.
  5. Wait until the drive dismounts and the mbed LED is flashing continuously
  6. Unplug the board and plug in again, and the board should enumerate as usual.

Other Resources

You can find detailed information about this platform on the nRF51 Dongle User Guide download page.

For any nRF51-Dongle related questions you can also search and post questions on NORDIC DEVELOPER ZONE

A team of summer interns at Nordic have recently developed a library for easier setup and prototyping of IoT devices for the nRF51822. This could be useful when developing applications for the nRF51-Dongle

Known issues

Impossible to debug or flash an application with IAR using CMSIS-DAP.

  • Description: It is not possible to flash or debug an application with IAR on the Nordic target. This issue is caused by a bad interaction between CMSIS-DAP IF present on the Nordic boards and IAR CMSIS-DAP debug driver.
  • Workaround: The best solution is to switch to the JLINK IF image and configure the IAR project to use it.
    • Download the JLINK IF and install it on the board.
    • Open the exported project in IAR then go to its options.
    • Go to the debugger section
      • In the setup tab choose J-link/J-trace as the debug driver.
      • In the Download tab disable the Use flash loader(s) option.
      • In the Extra options tabs, tick the Use command line options and add the following content: --drv_vector_table_base=0x0

 Buy Now


Please log in to start a discussion or ask a question.

Questions