cba69dd088
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
|
||
|---|---|---|
| .. | ||
| main | ||
| CMakeLists.txt | ||
| Makefile | ||
| README.md | ||
| sdkconfig.defaults | ||
ESP-IDF Gattc and Gatts Coexistence example
This example demonstrates the coexistence of gattc and gatts.
This example creates a GATT service and starts ADV. The ADV name is ESP_GATTS_DEMO, then waits to be connected. At the same time, a gatt client is created, the ADV name is ESP_GATTS_DEMO, the device is connected, and the data is exchanged. If the device is not found within 120 seconds, the example will stop scanning.
ESP-IDF also allows users to create a GATT service via an attribute table, rather than add attributes one by one. And it is recommended for users to use. For more information about this method, please refer to gatt_server_service_table_demo.
To test this example, you can run the gatt_client_demo, which can scan for and connect to this example automatically, and run gatt_server_demo, Waiting to be connected. They will start exchanging data once the GATT client has enabled the notification function of the GATT server.
Please check the tutorial for more information about the gatts part of this example. Please check the tutorial for more information about the gattc part of this example.