3. Running The Demonstration Example

This section describes the steps required to prepare the Pro DevKit and other tools to successfully run the example code. A Pro DevKit as well as a smartphone are required for testing and verifying the code.

3.1. Verifying with a Scanner App

  1. Establish a connection between the target device and your PC through the USB2(DBG) port of the motherboard. This port is used both for powering and communicating to the DA1468x SoC. For this tutorial a Pro DevKit is used.
'DA1468x Pro DevKit'

Fig. 12 DA1468x Pro DevKit

  1. Import and then make a copy of the ble_peripheral sample code found in the SDK of the DA1468x family of devices.


It is essential to import the folder named scripts to perform various operations (including building, debugging, and downloading)

  1. In the target application, add/modify all the required code blocks as illustrated in the Code Overview section.


It is possible for the defined macros not to be taken into consideration instantly. Thus, resulting in errors during compile time. If this is the case, the easiest way to deal with the issue is to: right-click on the application folder, select Index > Rebuild and then Index > Freshen All Files.

  1. Build the project in either Debug_QSPI or Release_QSPI mode and burn the generated image to the chip (either via the serial or jtag port).
  2. Press the K2 button on Pro DevKit to start the chip executing its firmware.
  3. When the project starts running, the DA1468x module should be visible by any Bluetooth scanner application. For this demonstration the BLE Scanner application was used.
'Verifying the Bluetooth Low Energy Device Output Using a Scanner App'

Fig. 13 Verifying the Bluetooth Low Energy Device Output Using a Scanner App

'Exploring the Services after Connecting to a Remote Peer'

Fig. 14 Exploring the Services after Connecting to a Remote Peer

  1. Verify the custom 128-bit UUID as well as the properties of the characteristic. Depending on the assigned properties, the scanner App will draw the corresponding symbols, for example R for reading, W for writing and N for enabling notifications.

    The descriptor with UUID equal to 0x2902 indicates whether notifications/indications are enabled or not. By default, notifications should be disabled. The descriptor with UUID equal to 0x2901 describes the role of the characteristic.

'Verify the Service Characteristics'

Fig. 15 Verify the Service Characteristics

  1. Verify the behavior of the characteristic This characteristic consists of 1-byte value. User can read as well as modify that value. If the attribute value is equal to 0x01, then the LED D2 on the Pro DevKit is turned on. For all other cases, the LED D2 is turned off.
'Verify the Characteristic Behavior (Write Operation)'

Fig. 16 Verify the Characteristic Behavior (Write Operation)