simple_beacon

name	simple_beacon
boards	da14531 da14585
keywords	Beacon Non Connectable Advertising
description	The main purpose of this Software Εxample is to demonstrate creating a Non-Connectable Advertising application example

DA1453x and DA1458x Simple Beacon Example

Example description

The main purpose of this Software Εxample is to demonstrate creating a Non-Connectable Advertising application example. To make Non-Connectable advertising more efficient the flag type field of an advertising packet is optional (please check Core Specification Supplement v6 by Bluetooth SIG). If flag type is not used, it can free up to 3 bytes of space which can then be used for sending more advertising data.

• Devices naming:
  • DA1453x is refering to DA14531-00, DA14531-01, DA14530 and DA14535.
  • DA1458x is refering to DA14585 and DA14586.
  • The DA14531-00 is the main DA14531 device. The -00 is just a new naming to introduce the variant DA14531-01. The DA14531-01 is a ROM variant of the main DA14531-00.
  • The DA14535 is a DA14531 upgrade.
  • The DA14533 is optimized for automotive and industrial applications at higher temperatures, and it is rated as operating up to 105 ºC and compliant with the AEC-Q100 (Grade 2) standard.

What is a Beacon?

Beacons are battery-powered devices that advertise a particular Bluetooth Low Energy payload with identifying information.

This Software Example is just to demonstrate creating a Simple Beacon project with Non-Connectable Advertising. However, it can be customized for more advanced use cases, such as:

• Adaptive modification of advertising data

• Choosing from various beacon formats

• Interleaving connectable advertising events

• Software Updates Over The Air (SUOTA)

Non-Connectable Advertising

Non-connectable advertising allows users to advertise data with the lowest power consumption.

The SDK includes a non-connectable advertising application example. The project is in the SDK directory:

​ <sdk_root_directory>/projects/target_apps/misc

The Keil v5 project file is:

​ <sdk_root_directory>/projects/target_apps/misc/ble_app_noncon/Keil_5/ble_app_noncon.uvprojx

The main difference between Simple Beacon SW Example and Non-Connectable example of the SDK is that in current implementation, user can define the data which will be appended within the Advertising or Scan Response packet. In the SDK Example, this possibility does not exist, as data stored in the adverting or Scan response packet is fixed (default value : 0xA5). To do so, Beacons will advertise a particular Bluetooth Low Energy payload with identifying information selected by the user.

The available APIs used are listed below :

• app_easy_gap_non_connectable_advertise_get_active() : Get non connectable advertising message with filled parameters.

• app_easy_gap_non_connectable_advertise_start() : Start advertising for non-connectable peripheral.

For getting more information about the BLE Advertising, please refer to Advertising Tutorial.

Hardware & Software Configuration

This example runs on DA1453x and DA14585/586 Bluetooth Smart SoC devices.

• Connect the DA145xx Pro Development Kit to the host computer via the USB connector.

• Please find below the appropriate hardware configurations.

DA14585/586 Hardware Configuration

In case of DA14585/586, DA145xx Pro Development Kit is required with default jumper configuration. Please see illustration below:

The Example can also run on DA14585 Basic Development Kit with default jumper configuration, as demonstrated below:

DA14531 Hardware Configuration

In case of DA14531, the DA14531 Pro Development Kit is also required for this Software Example with default jumper configuration. Please see the illustrations below:

Jumpers are placed in default configurations. Refer to UM-B-117.

Software Configuration

- [SDK6 latest version](https://www.renesas.com/sdk6_latest)
- Install SEGGER’s J-Link tools.

If using e² studio with LLVM instead of Keil, ensure your project settings are adjusted accordingly (instructions below).

Using e² studio with LLVM

Setup for e² studio #. Switching to e² studio: Instead of using Keil, you can use e² studio with LLVM as the compiler toolchain. Make sure your project is configured for LLVM by selecting the appropriate toolchain in e² studio.

#. Compile and Build: Open your project in e² studio and compile using LLVM. Ensure your environment variables and paths are properly set for the Renesas toolchain.

#. Run and Debug: Connect your device, set the proper debug configuration in e² studio, and start debugging using J-Link.

By switching to e² studio and LLVM, you can take advantage of advanced debugging tools and an open-source toolchain, while maintaining full compatibility with Renesas DA145xx devices.

For detailed steps on using e² studio, refer to the Renesas e² studio User Guide available on the Renesas website.

• Download the SDK6 latest version

• SEGGER’s J-Link tools should be downloaded and installed.

• A smartphone with a BLE scanning app (for example BLE scanner on Android or Lightblue on IOS).

• A BLE Sniffing tool is also useful; though not mandatory .

How to run the example

Initial Setup

For the initial setup of the project that involves linking the SDK to this SW example, please follow this: https://github.com/renesas/ble-sdk6-examples/blob/main/Readme.md.

- For the DA14531 getting started guide you can refer to [UM-B-117](https://lpccs-docs.renesas.com/UM-B-117-DA14531-Getting-Started-With-The-Pro-Development-Kit/index.html)

- For the DA14535 getting started guide you can refer to this [UM-B-165](https://lpccs-docs.renesas.com/DA14535/UM-B-165-DA14531-Getting-Started-With-The-Pro-Development-Kit/index.html#device-family-getting-started-with-the-pro-development-kits)

- For the DA14531 Module getting started guide you can refer to this [UM-B-139](https://lpccs-docs.renesas.com/UM-B-139-Getting-Started-with-DA14531-TINY-Module/index.html)

- For the DA14533 getting started guide you can refer to this [R19US0026EE0100](https://lpccs-docs.renesas.com/da14533_getting_started_guide/index.html)

Compile & Run

• Navigate to project_environment folder and open the Keil project.

• Compile and then launch the demonstration example. You can download the firmware either into System-RAM or SPI Flash. To download the firmware into SPI Flash, the SPI Flash programmer from SmartSnippets Toolbox should be used.

• Define the data that is to append into Adverting or Scan Response data packet by configuring the USER_DATA macro in user_simple_beacon.h. By default, USER_DATA is defined as follow :

#define USER_DATA  ("DA14585/586 & DA1453x Simple Beacon Software Example")

Note:

USER_DATA are stored in the uninitialized section of the Retention-RAM

uint8_t user_store_data[USER_DATA_LEN]    __attribute__((section("retention_mem_area_uninit") , zero_init));  //@RETENTION MEMORY

and copied into the user_store_data[] array:

memcpy(user_store_data, USER_DATA ,USER_DATA_LEN );

• Initially, the device initiates non-connectable advertising (ADV_NONCONN_IND) and then proceeds with sending an advertising scan indication (ADV_SCAN_IND). Finally, the device is switched back to non-connectable advertising mode. This is a full loop and is repeated all the time.

• Initially, the code checks if user_store_data[] is not empty.

• Every time the SW timer elapses, the adv_data_update_timer_cb() callback routine is triggered and each element of user_store_data[] is stored in the Advertising Data or Scan Response data packet.

• The firmware checks whether the advertising data are full or not. If not, the next item from user_store_data[] will be appended into them.

• Once the Advertising data packet is full and given that more data are present in ``user_store_data[]` , the next user data will be stored into the Scan Response data packet (SCAN_RESP).

To verify please take a look at the BLE sniffer log data

1. Initially only the the Device Name is placed into Adverising Data.

2. Advertising Data are now full.

3. Switching from ADV_NONCONN_IND to ADV_SCAN_IND.

4. Central sends a scan request (SCAN_REQ) in order to receive a scan response (SCAN_RESP) from the advertiser.

5. Full Scan Response Data.

Note

This example can be built by e2studio and LLVM compiler instead of using Keil.

Further reading

• Wireless Connectivity Forum

Known Limitations

• There are no known limitations for this example. But you can check and refer to the following application note for SDK6 known limitations

Feedback and support ?

If you have any comments or suggestions about this document, you can contact us through:

• Wireless Connectivity Forum

• Contact Technical Support

• Contact a Sales Representative