BLE Data Length Extensions#

1. Purpose / Scope#

This application demonstrates how to configure the RS9116W EVK in central role and can be used to set data length extension with the connected remote device. Packet length extension refers to the increasing Packet Data Unit (PDU) size from 27 to 251 bytes during the data transfer during the connection events. Both the central and peripheral can initiate this procedure at any time after entering the Connection.

2. Prerequisites / Setup Requirements#

Before running the application, the user will need the following things to setup.

2.1 Hardware Requirements#

• Windows PC with Host interface(UART/ SPI/ SDIO).

• Silicon Labs RS9116 Wi-Fi Evaluation Kit

• Host MCU Eval Kit. This example has been tested with:

  • Silicon Labs WSTK + EFR32MG21

  • Silicon Labs WSTK + EFM32GG11

  • STM32F411 Nucleo

• BLE peripheral device which supports data length extension feature.

2.2 Software Requirements#

• WiSeConnect SDK

• Embedded Development Environment

  • For STM32, use licensed Keil IDE

  • For Silicon Labs EFx32, use the latest version of Simplicity Studio

• Download and install the Silicon Labs EFR Connect App in the android smart phones for testing BLE applications. Users can also use their choice of BLE apps available in Android/iOS smart phones.

3. Application Build Environment#

3.1 Platform#

The Application can be built and executed on below Host platforms

• STM32F411 Nucleo

• WSTK + EFR32MG21

• WSTK + EFM32GG11

3.2 Host Interface#

• By default, the application is configured to use the SPI bus for interfacing between Host platforms(STM32F411 Nucleo / EFR32MG21) and the RS9116W EVK.

• This application is also configured to use the SDIO bus for interfacing between Host platforms(EFM32GG11) and the RS9116W EVK.

3.3 Project Configuration#

The Application is provided with the project folder containing Keil and Simplicity Studio project files.

• Keil Project

  • The Keil project is used to evaluate the application on STM32.

  • Project path: <SDK>/examples/snippets/ble/ble_datalength/projects/ble_datalength-nucleo-f411re.uvprojx

• Simplicity Studio

  • The Simplicity Studio project is used to evaluate the application on EFR32MG21.

  • Project path:

    • If the Radio Board is BRD4180A or BRD4181A, then access the path <SDK>/examples/snippets/ble/ble_datalength/projects/ble_datalength-brd4180a-mg21.slsproj

    • If the Radio Board is BRD4180B or BRD4181B, then access the path <SDK>/examples/snippets/ble/ble_datalength/projects/ble_datalength-brd4180b-mg21.slsproj

    • User can find the Radio Board version as given below

• EFM32GG11 platform

  • The Simplicity Studio project is used to evaluate the application on EFM32GG11.

    • Project path:<SDK>/examples/snippets/ble/ble_datalength/projects/ble_datalength-brd2204a-gg11.slsproj

3.4 Bare Metal/RTOS Support#

This application supports bare metal and RTOS environment. By default, the application project files (Keil and Simplicity Studio) are provided with bare metal configuration.

4. Application Configuration Parameters#

The application can be configured to suit your requirements and development environment. Read through the following sections and make any changes needed.

4.1 Open rsi_ble_datalength.c file

4.1.1 User must update the below parameters

RSI_BLE_DEV_ADDR_TYPE refers address type of the remote device to connect.

#define RSI_BLE_DEV_ADDR_TYPE                           LE_PUBLIC_ADDRESS

Based on the address of the advertising device, Valid configurations are

LE_RANDOM_ADDRESS

LE_PUBLIC_ADDRESS

Note Depends on the remote device, address type will be changed.

RSI_BLE_DEV_ADDR refers address of the remote device to connect.

#define RSI_BLE_DEV_ADDR                                "00:23:A7:80:70:B9"

RSI_REMOTE_DEVICE_NAME refers the name of remote device to which Silicon Labs device has to connect

#define RSI_REMOTE_DEVICE_NAME                         "SILABS_DEV"

Note! Silicon Labs module can connect to remote device by referring either RSI_BLE_DEV_ADDR or RSI_REMOTE_DEVICE_NAME of the remote device.

Power save configuration

By default, The Application is configured without power save.

#define ENABLE_POWER_SAVE 0

If user wants to run the application in power save, modify the below configuration.

#define ENABLE_POWER_SAVE 1 

4.1.2 The desired parameters are provided below. User can also modify the parameters as per their needs and requirements.

Following are the non-configurable macros in the file. BT_GLOBAL_BUFF_LEN refers Number of bytes required by the application and the driver

#define BT_GLOBAL_BUFF_LEN                              15000 

Following are the event numbers for advertising, connection and Disconnection events,

#define RSI_APP_EVENT_ADV_REPORT                         0
#define RSI_APP_EVENT_CONNECTED                          1
#define RSI_APP_EVENT_DISCONNECTED                       2 
#define RSI_APP_EVENT_DATA_LENGTH_CHANGE                 3
#define RSI_BLE_MTU_EVENT                                4

Following are the macros for setting data length(TX length and TX time)

#define TX_LEN                                          0x001e
#define TX_TIME                                         0x01f4

4.2 Open rsi_ble_config.h file. User can also modify the below parameters as per their needs and requirements.

#define RSI_BLE_PWR_INX                                30
#define RSI_BLE_PWR_SAVE_OPTIONS                       BLE_DISABLE_DUTY_CYCLING

Opermode command parameters

#define RSI_FEATURE_BIT_MAP                             FEAT_SECURITY_OPEN
#define RSI_TCP_IP_BYPASS                               RSI_DISABLE
#define RSI_TCP_IP_FEATURE_BIT_MAP                      TCP_IP_FEAT_DHCPV4_CLIENT
#define RSI_CUSTOM_FEATURE_BIT_MAP                      FEAT_CUSTOM_FEAT_EXTENTION_VALID
#define RSI_EXT_CUSTOM_FEATURE_BIT_MAP                  EXT_FEAT_384K_MODE

Note! rsi_ble_config.h files are already set with desired configuration in respective example folders user need not change for each example.

5. Testing the Application#

User has to follow the below steps for the successful execution of the application.

5.1 Loading the RS9116W Firmware#

Refer Getting started with PC to load the firmware into RS9116W EVK. The firmware binary is located in <SDK>/firmware/

5.2 Building the Application on the Host Platform#

5.2.1 Using STM32#

Refer STM32 Getting Started

• Open the project <SDK>/examples/snippets/ble/ble_datalength/projects/ble_datalength-nucleo-f411re.uvprojx in Keil IDE.

• Build and Debug the project

• Check for the RESET pin:

  • If RESET pin is connected from STM32 to RS9116W EVK, then user need not press the RESET button on RS9116W EVK before free run.

  • If RESET pin is not connected from STM32 to RS9116W EVK, then user need to press the RESET button on RS9116W EVK before free run.

• Free run the project

• Then continue the common steps from Section 5.3

5.2.2 Using EFX32#

Refer EFx32 Getting Started, for settin-up EFR & EFM host platforms

• Import the EFR32/EFM32 project from <SDK>/examples/snippets/ble/ble_datalength/projects

  • Select the appropriate .slsproj as per Radio Board type mentioned in Section 3.3 for EFR32 board. (or)

  • Select the *.brd2204a-gg11.slsproj for EFM32GG11 board.

• Compile and flash the project in to Host MCU

• Debug the project

• Check for the RESET pin:

  • If RESET pin is connected from EFX32 to RS9116W EVK, then user need not press the RESET button on RS9116W EVK before free run

  • If RESET pin is not connected from EFX32 to RS9116W EVK, then user need to press the RESET button on RS9116W EVK before free run

• Free run the project

• Then continue the common steps from Section 5.3

5.3 Common Steps#

1. Configure the remote device in peripheral mode and put it in advertising mode.

2. After the program gets executed, Silicon Labs device tries to connect with the remote device specified in RSI_BLE_DEV_ADDR or RSI_REMOTE_DEVICE_NAME macro.

3. Observe that the connection is established between the desired device and Silicon Labs device.

4. After connection Silicon Labs device will set data length of the remote device.

5. Observe data length change event after setting data length.

6. After successful program execution the print in teraterm looks as shown below.

Compressed Debug Logging#

To enable the compressed debug logging feature please refer to Logging User Guide