mirror of
https://github.com/espressif/esp-idf.git
synced 2025-08-11 21:10:20 +00:00
db3fa3a100
1. Store node name in nvs when Provisioner sets node name 2. Add an API to store node composition data 3. Update lightness last when lightness actual is changed 4. Add ble mesh english/chinese documents 5. Update ble mesh tx/rx test example 6. Add params to provisioner bind appkey comp event 7. Fix node ignoring relay messages issue 8. Fix PreviousAddress endianess in Friend Request 9. Support using a specific partition for ble mesh 10. Fix compile warning when proxy related macros are disabled 11. Not using internal macros in esp_ble_mesh_defs.h 12. No device address needed when PB-ADV is used
33 lines
2.1 KiB
ReStructuredText
33 lines
2.1 KiB
ReStructuredText
Bluetooth API
|
|
*************
|
|
|
|
.. toctree::
|
|
:maxdepth: 2
|
|
|
|
Bluetooth Controller && VHCI <controller_vhci>
|
|
Bluetooth Common <bt_common>
|
|
Bluetooth LE <bt_le>
|
|
Bluetooth Classic <classic_bt>
|
|
NimBLE <nimble/index>
|
|
ESP-BLE-MESH <esp-ble-mesh>
|
|
|
|
ESP-IDF currently supports two host stacks. The Bluedroid based stack (default) supports classic Bluetooth as well as BLE. On the other hand, Apache NimBLE based stack is BLE only. For users to make a
|
|
* For usecases involving classic Bluetooth as well as BLE, Bluedroid should be used.
|
|
* For BLE-only usecases, using NimBLE is recommended. It is less demanding in terms of code footprint and runtime memory, making it suitable for such scenarios.
|
|
|
|
To see the overview of the ESP32 Bluetooth stack architecture, follow links below:
|
|
|
|
* `ESP32 Bluetooth Architecture (PDF) [English] <http://espressif.com/sites/default/files/documentation/esp32_bluetooth_architecture_en.pdf>`_
|
|
* `ESP32 Bluetooth Architecture (PDF) [中文] <http://espressif.com/sites/default/files/documentation/esp32_bluetooth_architecture_cn.pdf>`_
|
|
|
|
Example code for this API section is provided in :example:`bluetooth` directory of ESP-IDF examples.
|
|
|
|
Several examples contain detailed description. To see them please follow links below:
|
|
|
|
* :example_file:`GATT Client Example Walkthrough <bluetooth/gatt_client/tutorial/Gatt_Client_Example_Walkthrough.md>`
|
|
* :example_file:`GATT Server Service Table Example Walkthrough <bluetooth/gatt_server_service_table/tutorial/Gatt_Server_Service_Table_Example_Walkthrough.md>`
|
|
* :example_file:`GATT Server Example Walkthrough <bluetooth/gatt_server/tutorial/Gatt_Server_Example_Walkthrough.md>`
|
|
* :example_file:`GATT Security Client Example Walkthrough <bluetooth/gatt_security_client/tutorial/Gatt_Security_Client_Example_Walkthrough.md>`
|
|
* :example_file:`GATT Security Server Example Walkthrough <bluetooth/gatt_security_server/tutorial/Gatt_Security_Server_Example_Walkthrough.md>`
|
|
* :example_file:`GATT Client Multi-connection Example Walkthrough <bluetooth/gattc_multi_connect/tutorial/Gatt_Client_Multi_Connection_Example_Walkthrough.md>`
|