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 DA1469x Pro DevKit, a BLE scanner APP as well as the SmartSnippets™ Toolbox are required for testing and verifying the code. If you are not familiar with the recommended process on how to clone a project read the Starting a Project tutorial.

There are two main methods to verify the correct behavior of the demonstrated code. The first method is to use a BLE scanner App on your smartphone and the second is to use the Power Profiler part of the SmartSnippets™ Toolbox. Both cases are demonstrated below.

3.1. Verifying with a BLE Scanner App

  1. Establish a connection between the target device and your PC through the USB1 port of the motherboard. This port is used both for powering and communicating to the DA1469x SoC. For this tutorial a Pro DevKit is used.

  2. Import and then make a copy of the ble_adv sample code found in the SDK of the DA1469x family of devices.

Note

It is essential to import the folder named python_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.

Note

It is possible for the defined macros not to be taken into consideration instantly. Hence, resulting in errors during compile time. If this is the case, the easiest way to proceed with 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.

  2. Press the RESET button on Pro DevKit to start the chip executing its firmware.

  3. When the project starts running, the DA1469x Bluetooth SoC should be visible by any Bluetooth scanner application. For this demonstration the BLE Scanner application was used.

'Output 1'

Figure 4 Verifying the Bluetooth Low Energy Device Output Using a Scanner App

'Output 2'

Figure 5 Exploring the Various Services after Connecting to a Remote Peer

3.2. Verifying with the SmartSnippets Toolbox

Another useful tool that can be used both for debugging and power measurements is the SmartSnippets™ Toolbox.

  1. To create a new session, in the SmartSnippets™ Welcome page click on SmartSnippets Toolbox. In the pop-up window displayed, do the following:

    1. Select New to create a new project (1). In the New Project window, enter a name for the project (2). This step is optional if a project has already been created.

    2. Choose the newly created or an available project (4).

    3. Choose a communication interface (3) and a port (5).

    4. Select the family of devices to use (in our use case this should be the DA1469x-00 option) (6).

    5. Open the selected project (7).

'Opening SmartSnippets Toolbox'

Figure 6 Opening a Project in the SmartSnippets Toolbox

  1. Switch to the Power Profiler window. At the bottom of the displayed window click Initialize and then Start

'SmartSnippets Toolbox - Power Profiler'

Figure 7 SmartSnippets Toolbox - Power Profiler

  1. Press the RESET button on Pro DevKit to start the chip executing its firmware.

  2. Verify that the advertising interval has been set to power-save mode (the default value of the FAST_ADV_INTERVAL macro is set to zero). In this case, the Dialog chip utilizes the maximum time interval (1500 ms). The alternative option would be for the Dialog chip to use the minimum time interval (1000 ms).

'Verifying the Advertising Interval'

Figure 8 Verifying the Advertising Interval

  1. Verify that advertising data are sent over the advertising channel #37 (instead of utilizing the default advertising channels #37, #38 and #39)

'Verifying Advertising Channel Map'

Figure 9 Verifying Advertising Channel Map

  1. Using the scanner App connect to the Bluetooth Dialog chip.

    1. Verify that connection parameters are being changed 5 seconds after a connection establishment.

'Output 5'

Figure 10 Verifying Connection Parameter Update

  1. Verify that connection parameters have been updated. In this case, the max interval value is used by the Dialog chip (750 ms). The alternative option would be the slow interval value (500 ms).

'Output 6'

Figure 11 Verifying Connection Parameter Update