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
14 lines
662 B
Text
14 lines
662 B
Text
menu "Example 'GATT SERVER' Config"
|
|
|
|
config 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.
|
|
|
|
endmenu
|