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.

Note

• Describes the number of buffers 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 We increase the buffer capacity for the notify/write cmds to achieve the best throughput. See rsi_ble_set_wo_resp_notify_buf_info() to set more buffers for the notify/write commands

• 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 (n)

Note

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

• Bits 5 - 12 are used to set NUM_REC_BYTES

SL_SI91X_BLE_GATT_INIT#

#define SL_SI91X_BLE_GATT_INIT

BIT(13)

GATT INIT.

Note

• 0 - GATT Init in Firmware i.e both the GAP service and GATT service will be maintained by Firmware 1 - GATT Init in Host i.e 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)

Indication response from APP.

Note

• As per ATT protocol for every indication received from the server should be acknowledged (indication response) by the Client. If this bit is disabled then firmware will send the acknowledgment(indication response) and if the bit is enabled then 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.

Note

• If this bit is disabled, the firmware will initiate the MTU request to the remote device on the successful connection. And if Peer initiates MTU exchange Request then firmware will send Exchange MTU Response in reply to a received Exchange MTU Request. If this bit enabled then APP/Host/User need to initiate the MTU request by using the rsi_ble_mtu_exchange_event API. And if Peer initiates MTU exchange Request then APP/Host/User shall send Exchange MTU Response in reply to a received Exchange MTU Request using 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 Resp Data from APP.

Note

• Device will maintain some default scan response data and will be used in the scan_response controller frame. By enabling this bit we can make the default data as 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.

Note

• Device will support the LE-coded phy feature (i.e LR - 125kbps and 500kbps) by default. If this bit is enabled, the device will not the support of the LE-coded phy rates.

SL_SI91X_BLE_ENABLE_ADV_EXTN#

#define SL_SI91X_BLE_ENABLE_ADV_EXTN

BIT(19)

SL_SI91X_BLE_AE_MAX_ADV_SETS#

#define SL_SI91X_BLE_AE_MAX_ADV_SETS

(num_adv_sets)