Extended BLE Custom Feature Bitmap#

SL_SI91X_BLE_NUM_CONN_EVENTS#

#define SL_SI91X_BLE_NUM_CONN_EVENTS

(num_conn_events)

BLE number of connection events.

Describes the number of buffers that need to be allocated for BLE on the opermode.

• By default, each role (central/peripheral) will be allocated with 1 buffer for the notify/write command.

• Increasing the buffer capacity for the notify/write commands helps achieve the best throughput.

• See rsi_ble_set_wo_resp_notify_buf_info() to set more buffers for the notify/write commands.

Note

• Bits 0 - 4 are used to set NUM_CONN_EVENTS.

SL_SI91X_BLE_NUM_REC_BYTES#

#define SL_SI91X_BLE_NUM_REC_BYTES

(num_rec_bytes)

BLE number of record size in bytes.

Specifies the number of record bytes in multiples of 16.

• n*16 : (n=60, Default 1024 bytes (1K)).

Note

• Bits 5 - 12 are used to set NUM_REC_BYTES.

SL_SI91X_BLE_GATT_INIT#

#define SL_SI91X_BLE_GATT_INIT

BIT(13)

GATT initialization mode.

Specifies whether the GATT is initialized in firmware or by the host.

• 0: GATT Init in Firmware. Both the GAP service and GATT service will be maintained by the firmware.

• 1: GATT Init in Host. The GAP service and GATT service should be created by the APP/Host/User, and the ATT transactions like read, write, notify, and indicate shall be handled by the APP/Host/User.

• Default: GATT Init in Firmware.

SL_SI91X_BLE_INDICATE_CONFIRMATION_FROM_HOST#

#define SL_SI91X_BLE_INDICATE_CONFIRMATION_FROM_HOST

BIT(14)

Acknowlegment of the indication from the client.

As per the ATT protocol, every indication received from the server should be acknowledged (indication response) by the client.

• If this bit is disabled, the firmware will send the acknowledgment (indication response).

• If this bit is enabled, the APP/Host/User needs to send the acknowledgment (indication response).

SL_SI91X_BLE_MTU_EXCHANGE_FROM_HOST#

#define SL_SI91X_BLE_MTU_EXCHANGE_FROM_HOST

BIT(15)

MTU exchange request initiation from APP.

• If this bit is disabled, the firmware will initiate the MTU request to the remote device on a successful connection.

  • If the peer initiates an MTU exchange request, the firmware will send an Exchange MTU Response in reply to the received Exchange MTU Request.

• If this bit is enabled, the APP/Host/User needs to initiate the MTU request using the rsi_ble_mtu_exchange_event API.

  • If the peer initiates an MTU exchange request, the APP/Host/User shall send an Exchange MTU Response using the rsi_ble_mtu_exchange_resp API.

SL_SI91X_BLE_SET_SCAN_RESP_DATA_FROM_HOST#

#define SL_SI91X_BLE_SET_SCAN_RESP_DATA_FROM_HOST

BIT(16)

Set scan response data from host.

The device will maintain some default scan response data to be used in the scan_response controller frame.

• Enabling this bit will make the default data Null (empty).

SL_SI91X_BLE_DISABLE_CODED_PHY_FROM_HOST#

#define SL_SI91X_BLE_DISABLE_CODED_PHY_FROM_HOST

BIT(17)

Disable coded PHY from APP.

The device supports the LE-coded PHY feature (i.e., LR - 125kbps and 500kbps) by default.

• If this bit is enabled, the device will not support the LE-coded PHY rates.

SL_SI91X_BLE_ENABLE_ADV_EXTN#

#define SL_SI91X_BLE_ENABLE_ADV_EXTN

BIT(19)

Enable advertising extensions.

Enables or disables advertising extensions.

Note

• Bit 19 is used for enabling advertising extensions.

SL_SI91X_BLE_AE_MAX_ADV_SETS#

#define SL_SI91X_BLE_AE_MAX_ADV_SETS

(num_adv_sets)

Maximum number of AE advertising sets.

Configures the maximum number of AE advertising sets.

• Maximum number of AE advertising sets is 2.

Note

• Bits 20 - 23 are used to set the number of AE advertising sets.