The existing Bluetooth examples are split as: 1. examples/bluetooth/bluedroid - Bluedroid Host (BT + BLE) examples a. examples/bluetooth/bluedroid/classic_bt - Classic BT examples b. examples/bluetooth/bluedroid/ble - BLE examples c. examples/bluetooth/bluedroid/coex - Classic BT and BLE coex examples d. examples/bluetooth/bluedroid/hci - VHCI and HCI UART examples i. Rename ble_adv to controller_vhci_ble_adv and move it in hci folder 2. examples/bluetooth/nimble - NimBLE BLE Host + NimBLE Mesh examples 3. examples/bluetooth/esp_ble_mesh - ESP BLE Mesh examples 4. Update documentation references
27 lines
1.2 KiB
Text
27 lines
1.2 KiB
Text
menu "Example 'GATT SERVER THROUGHPUT' Config"
|
|
|
|
config EXAMPLE_SET_RAW_ADV_DATA
|
|
bool "Use raw data for advertising packets and scan response data"
|
|
help
|
|
If this config item is set, raw binary data will be used to generate advertising & scan response data.
|
|
This option uses the esp_ble_gap_config_adv_data_raw() and esp_ble_gap_config_scan_rsp_data_raw()
|
|
functions.
|
|
|
|
If this config item is unset, advertising & scan response data is provided via a higher-level
|
|
esp_ble_adv_data_t structure. The lower layer will generate the BLE packets. This option has higher
|
|
overhead at runtime.
|
|
|
|
config EXAMPLE_GATTS_NOTIFY_THROUGHPUT
|
|
bool "test the gatts notify throughput"
|
|
help
|
|
If this config item is set, then the 'EXAMPLE_GATTC_WRITE_THROUGHPUT' config should be close, it can't test
|
|
both write or notify at the same time at this demo
|
|
|
|
config EXAMPLE_GATTC_WRITE_THROUGHPUT
|
|
bool "test the gattc write throughput"
|
|
help
|
|
If this config item is set, then the 'EXAMPLE_GATTS_NOTIFY_THROUGHPUT' config should be close, it can't
|
|
test both write or notify at the same time at this demo
|
|
endmenu
|
|
|
|
|