Note: This post is outdated. Please go to the product page for nRF Connect for Desktop for updated information and downloads.
nRF Connect is the new official name of the Bluetooth Smart tool previously known as Yggdrasil. We have now reached Release Candidate stage for version 1.0 and it is available for download in this article.
*New nRF Connect logo*
*nRF Connect screenshot*
We are shipping the Release Candidate as a separate release before the production v1.0 release because we want to surface as many issues as possible before v1.0 production release. Please share with us if you find anything that seems like a bug. We will focus on bug fixing before the production release, but we are still happy to receive feature requests for future releases.
Please leave your feeback on devzone or send a PM.
On OSX there is a problem with making the Segger firmware working correctly due to USB packet sizes. There are two solutions to this problem: Correction: In this release, v1.0 RC, the only supported workaround is option 2 below:
Shortly after RC release we will start preparing the 1.0 production version.
At the same time of releasing the 1.0 production version we will also make the source code of nRF Connect available on GitHub, complete with build instructions.
Download the file for your system, install or unpack and run the application:
nRF Connect requires a connectivity firmware to be programmed to the development kit or dongle. Either use a tool like nrfjprog to program or simply drag and drop the file to the JLINK drive of the kit.
The hex files are available in the nRF Connect application hex folder, or click the link for direct download:
See description under known issues.
Hi, there will be support for showing text instead of hex. We have preconfigured well known text based characteristics to show as text, but it will also be possible to do this on custom UUIDs.
Will there be a setting to change the value display format from hex to text for example?
Hi, nRF Connect 1.0RC requires DAPLINK on OSX. pc-ble-driver-js can run on Segger J-Link as well.
Ok. Thanks for the quick response and clarification.
Just one more clarification :
Is the requirement for mbed DAPLINK firwmare that of nRF Connect tool or the underlying pc-ble-driver-js library that is used by this tool ?
I'm sorry but the instructions on what workarounds that can be applied are not totally correct. nRF Connect 1.0 RC only supports mbed DAPLINK firmware, not Segger JLink.
In the next release, which will be out within short time, we again support Segger JLink, though still with the requirement to disable MSD feature. Segger JLink will then be the preferred option as that will have firmware programming support in the application.