8. Software Development Tools

8.1. SmartSnippets™ Introduction

Dialog SmartSnippets™ Studio is a royalty-free software development platform for Smartbond™ devices. It fully supports the DA14531 family of devices.

For the SmartSnippets™ Package you need only to install SmartSnippets™ Studio, which contains:

  • SmartSnippets™ Toolbox to cover all software development requirements, and includes:

    • programming and loading firmware into SRAM, OTP, EEPROM and Flash

    • power profiling

    • Terminal Scripting

  • SmartSnippets™ Toolbox documentation

The SmartSnippets™ IDE is enabled by an on-board J-Link debugger from SEGGER. This offers standard debug capabilities such as single stepping, setting breakpoints, software download and many more. For more details on the debugger capabilities, visit https://www.segger.com/.

8.2. SmartSnippets™ Installation

For further reading on the installation procedure of SmartSnippets™ Studio, see the UM-B-057 SmartSnippets Studio User Manual.


Registration is required to download the SmartSnippets™.


Please be aware that if you have antivirus software installed on your machine, it could slow down the SmartSnippets™ installation due to the scan.

A summary of the steps:

  1. Download the latest version of SmartSnippets™ Studio from Development Tools.

  2. Run the SmartSnippets™ Studio installer (.msi). Several of the required tools are automatically installed, others need to be manually downloaded and installed.

  3. Select to install the latest version of SEGGER J-Link GDB server and click Next.

  1. Select the destination folder for SmartSnippets™ Studio and click Next.


Figure 14 Select SmartSnippets™ Studio Install Directory

The SmartSnippets™ Studio is installed.


  • The default Windows installation folder for SmartSnippets™ Studio is C:\DiaSemi.

  • When Windows Defender is turned ON, that will prevent the file SmartSnippets™ Studio installer (.msi) from running automatically. When prompted, click Run Anyway.

  • Administrator access is required to install SmartSnippets Studio software components.

8.3. Keil Installation

For DA14531, the Keil® µVision® IDE must be used for compilation and debugging of this getting started guide. Download and install KEIL separately. Registration is required. Please know that we do provide one GCC project in the SDK: <sdk_root_directory>\projects\target_apps\ble_examples\prox_reporter\Eclipse

  1. Download and install the Keil tools from https://www.keil.com/demo/eval/arm.htm.


The Keil development tools can be run as a Lite/Evaluation version without a product license, see Figure 15 (File > License Management). This Lite/Evaluation version has a 32 kB of code (in ROM) limitation.


Figure 15 Keil Lite Version

  1. When the installation is complete, a list of packs is shown (Figure 16). If you do not see this list:

    1. Click the Packs Installer button (or select Project > Manage > Pack Installer).

    2. Click the Check for Updates button to show an updated list of packs.

  2. Click the Install or Update button next to the ARM::CMSIS package, if not up to date.


Figure 16 CMSIS Package Installation

  1. To install ARM compiler version 5:

  • Download the latest ARM Compiler 5 version from the Legacy ARM compilers download page.

  • Choose to install it into the ARM sub directory of the Keil MDK installation directory. If Keil is installed in the default directory, you should install the ARM compiler in C:\Keil_v5\ARM\ARM_Compiler_5.XXuX.

  • Register and add the installed Arm Compiler 5 release:

a/ Open the dialog Project - Manage - Project Items - Folders/Extensions:


Figure 17 Manage Arm Compiler Versions

b/ Click the button on the right side of Use ARM Compiler to open the dialog ARM Compiler Versions. The dialog shows the relative compiler installation path and the compiler version:


Figure 18 Add Arm Compiler new Version

c/ Click Add another Arm Compiler Version to List. This opens a Windows browse for folder dialog. Navigate to the folder that contains the Arm compiler version and click OK to register the compiler. The path to that folder and the Arm compiler version is shown in the screen above. With these steps you have registered an additional Arm compiler.


Figure 19 Browse to the new Compiler Version


Figure 20 new Compiler Version added