pioduino/esp-idf
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch 'bugfix/fix_bluetooth_cap_define_and_doc' into 'master'

Browse Source 
Bugfix/fix bluetooth cap define and doc

Closes BC-1298 and BC-1297

See merge request espressif/esp-idf!19149
This commit is contained in:
Island
2022-08-11 16:51:08 +08:00
parent 236d910be8 f070ac4da8
commit fd8101498b
20 changed files with 104 additions and 47 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/en/api-reference/bluetooth/index.rst
+1 -1
View File
@@ -8,7 +8,7 @@ Bluetooth API
bt_common
bt_le
:SOC_CLASSIC_BT_SUPPORTED: classic_bt
:SOC_BT_CLASSIC_SUPPORTED: classic_bt
controller_vhci
esp-ble-mesh
nimble/index
docs/en/api-reference/bluetooth/nimble/index.rst
+1 -2
View File
@@ -30,8 +30,7 @@ To begin with, make sure that the NimBLE stack is enabled from menuconfig :ref:`
Typical programming sequence with NimBLE stack consists of the following steps:
* Initialize NVS flash using :cpp:func:`nvs_flash_init` API. This is because ESP controller uses NVS during initialization.
* Call :cpp:func:`esp_nimble_hci_and_controller_init` to initialize ESP controller as well as transport layer. This will also link the host and controller modules together. Alternatively, if ESP controller is already initialized, then :cpp:func:`esp_nimble_hci_init` can be called for the remaining initialization.
* Initialize the host stack using ``nimble_port_init``.
* Initialize the host and controller stack using ``nimble_port_init``.
* Initialize the required NimBLE host configuration parameters and callbacks
* Perform application specific tasks/initialization
* Run the thread for host stack using ``nimble_port_freertos_init``