Merge branch 'bugfix/fix_bluedroid_read_multi_v6.0' into 'release/v6.0'

fix(ble/bluedroid): fix GATT Read Multiple response handling (6.0) See merge request espressif/esp-idf!50709
2026-10-02 11:10:54 +03:00 · 2026-07-15 15:38:50 +08:00
parent 1dc74d56a2 7020f17b59
commit 2dc3285e57
26 changed files with 174 additions and 145 deletions
@@ -22,7 +22,7 @@ There are some important points for this demo:
   `esp_ble_gap_security_rsp` should be used to send security response to the peer device when `ESP_GAP_BLE_SEC_REQ_EVT` is received.
 3. The `gatt_security_client_demo` will receive a `ESP_GAP_BLE_AUTH_CMPL_EVT` once the encryption procedure has completed.

-Please, check this [tutorial](tutorial/ble50_security_client_Example_Walkthrough.md) for more information about this example.
+Please check this [tutorial](tutorial/ble50_security_client_Example_Walkthrough.md) for more information about this example.

 ### Hardware Required

@@ -7,9 +7,9 @@
 * The peripheral device is normally a GATT Server that exposes Services and Characteristics. The peripheral replies with a *Aux Connect Pairing Response* followed by authentication and exchange of keys. If the bonding process is also executed, the Long Term Keys are stored for subsequent connections. Finally an encrypted channel is established which can support protection against Man-In-The-Middle (MITM) attacks depending on the security configuration. 
 * The code is implemented using an Application Profile that upon registration, allows to set the local privacy configuration as events are triggered during the life time of the program. 

-This document only includes a description of the security aspects of the BLE5.0 Security GATT Client implementation, for the more info about extended scan , periodic scan please refer to [Periodic_Sync_Example Walkthrough] (../../periodic_sync/tutorial/Periodic_Sync_Example_Walkthrough.md).
+This document only includes a description of the security aspects of the BLE5.0 Security GATT Client implementation. For more information about extended scan and periodic scan, please refer to [Periodic Sync Example Walkthrough](../../periodic_sync/tutorial/Periodic_Sync_Example_Walkthrough.md).

-##include
+## Includes

 ```c
 #include <stdint.h>
@@ -27,7 +27,7 @@ This document only includes a description of the security aspects of the BLE5.0
 #include "esp_log.h"
 #include "freertos/FreeRTOS.h"
 ```
-These `includes` are required for the FreeRTOS and underlying system components to run, including the logging functionality and a library to store data in non-volatile flash memory. We are interested in `“bt.h”`, `“esp_bt_main.h”`, `"esp_gap_ble_api.h"` and `“esp_gattc_api.h”`, which expose the BLE APIs required to implement this example.
+These `includes` are required for the FreeRTOS and underlying system components to run, including the logging functionality and a library to store data in non-volatile flash memory. We are interested in `"bt.h"`, `"esp_bt_main.h"`, `"esp_gap_ble_api.h"` and `"esp_gattc_api.h"`, which expose the BLE APIs required to implement this example.

 * `bt.h`: configures the BT controller and VHCI from the host side.
 * `esp_bt_main.h`: initializes and enables the Bluedroid stack.
@@ -7,7 +7,7 @@ This example shows how to use the APIs to connect in secure manner with peer dev

 To test this example, you can run [ble50_security_client_demo](../ble50_security_client), which starts scanning, connects to and starts encryption with `ble50_sec_gattc_demo` automatically.

-Please, check this [tutorial](tutorial/ble50_security_server_Example_Walkthrough.md) for more information about this example.
+Please check this [tutorial](tutorial/ble50_security_server_Example_Walkthrough.md) for more information about this example.

 ## How to Use Example

@@ -1,11 +1,11 @@
 | Supported Targets | ESP32-C2 | ESP32-C3 | ESP32-C5 | ESP32-C6 | ESP32-C61 | ESP32-H2 | ESP32-S3 |
 | ----------------- | -------- | -------- | -------- | -------- | --------- | -------- | -------- |

-#ESP-IDF Multi Adv Example
+# ESP-IDF Multi Adv Example

-This example support legacy as well as extended advertisement for all phy.
+This example supports legacy as well as extended advertisement for all phy.

-Please, check this [tutorial](tutorial/Mulit_Adv_Example_Walkthrough.md) for more information about this example.
+Please check this [tutorial](tutorial/Mulit_Adv_Example_Walkthrough.md) for more information about this example.

 ## How to Use Example

@@ -1,12 +1,12 @@
 # Multi Adv Example Walkthrough

-## introduction
+## Introduction

 In this document, we review the Multi Adv example code which implements a Bluetooth Low Energy (BLE5.0) Multi adv profile on the ESP32C3. This example is designed around two Application Profiles and a series of events that are handled in order to execute a sequence of configuration steps, such as defining extended advertising parameters with all phy 1M,2M and coded and Ext adv data.

 ## Includes

-First, let’s take a look at the include
+First, let's take a look at the include

 ```c
 #include <stdio.h>
@@ -163,7 +163,7 @@ shed to the application from the BLE stack.

 The register application event is the first one that is triggered during the lifetime of the program, this example uses the Profile A GATT event handle to configure the advertising parameters upon registration. This example has the option to use both standard Bluetooth Core Specification advertising parameters or a customized raw buffer. The option can be selected with the `CONFIG_SET_RAW_ADV_DATA` define. The raw advertising data can be used to implement iBeacons, Eddystone or other proprietary, and custom frame types such as the ones used for Indoor Location Services that are different from the standard specifications.

-The function is used to configure different types of extended advertisement types and legacy adv with 1M,2M and coded phy in esp_ble_gap_ext_adv_set_params , esp_ble_gap_ext_adv_set_rand_addr and esp_ble_gap_config_ext_adv_data_raw. Respective structure of each one of them mentioned below with one example:
+The function is used to configure different types of extended advertisement types and legacy adv with 1M,2M and coded phy in esp_ble_gap_ext_adv_set_params, esp_ble_gap_ext_adv_set_rand_addr and esp_ble_gap_config_ext_adv_data_raw. Respective structure of each one of them mentioned below with one example:

 ```c
 /**
@@ -269,7 +269,7 @@ rt.status);
 }

 ```
-## Default config
+## Default Config

 This example by default  configured with
 1M phy extend adv, Connectable advertising
@@ -1,15 +1,15 @@
 | Supported Targets | ESP32-C2 | ESP32-C3 | ESP32-C5 | ESP32-C6 | ESP32-C61 | ESP32-H2 | ESP32-S3 |
 | ----------------- | -------- | -------- | -------- | -------- | --------- | -------- | -------- |

-# ESP_IDF Periodic Adv Example
+# ESP-IDF Periodic Adv Example

-This example support for the periodic advertisement which allow the scanner to sync with the advertiser so that scanner and advertiser wake up same time. It support extended adv with 2M phy in connectable mode.
+This example supports the periodic advertisement which allow the scanner to sync with the advertiser so that scanner and advertiser wake up same time. It support extended adv with 2M phy in connectable mode.


 To test this demo, we can run the [periodic_sync_demo](../periodic_sync), which can do periodic scan and try to sync with periodic adv.


-Please, check this [tutorial](tutorial/Periodic_adv_Example_Walkthrough.md) for more information about this example.
+Please check this [tutorial](tutorial/Periodic_adv_Example_Walkthrough.md) for more information about this example.

 ## How to Use Example

@@ -1,11 +1,11 @@
 # Periodic Adv Example Walkthrough

-## introduction
+## Introduction

 In this document, We review the Periodic  Adv example code which implements a Bluetooth Low Energy (BLE5.0) Multi adv profile on the ESP32C3. This example is designed the periodic advertisement which allow the scanner to sync with the advertiser so that scanner and advertiser wake up same time.

-##include
-First, let’s take a look at the include
+## Includes
+First, let's take a look at the include

 ```c
 #include <stdio.h>
@@ -167,7 +167,7 @@ The functions  `gap_event_handler()` handle all the events that are pushed to th

 The register application event is the first one that is triggered during the lifetime of the program, this example uses the Profile A GATT event handle to configure the advertising parameters upon registration. This example has the option to use both standard Bluetooth Core Specification advertising parameters or a customized raw buffer. The option can be selected with the `CONFIG_SET_RAW_ADV_DATA` define. The raw advertising data can be used to implement iBeacons, Eddystone or other proprietaries, and custom frame types such as the ones used for Indoor Location Services that are different from the standard specifications.

-The function is used to configure different types of extended advertisement types and legacy adv with 1M,2M and coded phy is esp_ble_gap_ext_adv_set_params , esp_ble_gap_ext_adv_set_rand_addr and esp_ble_gap_config_ext_adv_data_raw. Respective structure of each one of them mentioned below with one example:
+The function is used to configure different types of extended advertisement types and legacy adv with 1M,2M and coded phy is esp_ble_gap_ext_adv_set_params, esp_ble_gap_ext_adv_set_rand_addr and esp_ble_gap_config_ext_adv_data_raw. Respective structure of each one of them mentioned below with one example:

 ```c
 /**
@@ -300,7 +300,7 @@ static void gap_event_handler(esp_gap_ble_cb_event_t event, esp_ble_gap_cb_param
    }
 }
 ```
-## Default config
+## Default Config
 2M phy with connectable mode of periodic adv.


@@ -7,7 +7,7 @@ This example supports the periodic extended scan to scan the extended advertisem

 To test this demo, we can run the [periodic_adv_demo](../periodic_adv), which can start extended advertisement with supported param.

-Please, check this [tutorial](tutorial/Periodic_Sync_Example_Walkthrough.md) for more information about this example.
+Please check this [tutorial](tutorial/Periodic_Sync_Example_Walkthrough.md) for more information about this example.

 ## How to Use Example

@@ -1,12 +1,12 @@
-#Periodic Sync Example Walkthrough
+# Periodic Sync Example Walkthrough

 ## Introduction
-In this tutorial, the Periodic sync example code for the ESP32C3 is reviewed. The code implement Bluetooth Low Energy (BLE5.0) periodic sync , which scans for nearby peripheral which can support legacy, extended and periodic advertisement. Periodic Sync allow the advertiser to sync with scanner so that scanner and advertiser wake up at same time.
+In this tutorial, the Periodic sync example code for the ESP32C3 is reviewed. The code implement Bluetooth Low Energy (BLE5.0) periodic sync, which scans for nearby peripheral which can support legacy, extended and periodic advertisement. Periodic Sync allow the advertiser to sync with scanner so that scanner and advertiser wake up at same time.

 * ADV_EXT_IND is over primary advertising channels
 * AUX_ADV_IND and AUX_SYNC_IND are over secondary advertising channels

-Little info about the EXT_ADV_IND , AUX_ADV_IND and AUX_SYNC_IND with scanner support of periodic sync.
+Little info about the EXT_ADV_IND, AUX_ADV_IND and AUX_SYNC_IND with scanner support of periodic sync.

 ADV_EXT_IND is over primary advertising channels and is used to indicate that an advertisement will be sent on a secondary advertisement channel. The information in ADV_EXT_IND will inform the scanner:

@@ -35,7 +35,7 @@ With this information, the scanner can synchronize with the advertiser and they
 #include <string.h>
 #include "freertos/FreeRTOS.h"
 #include "freertos/task.h"
-#include "freertos/event_groups.h
+#include "freertos/event_groups.h"
 #include "esp_system.h"
 #include "esp_log.h"
 #include "nvs_flash.h"
@@ -49,7 +49,7 @@ With this information, the scanner can synchronize with the advertiser and they
 #include "freertos/semphr.h"
 ```

-These `includes` are required for the FreeRTOS and underlying system components to run, including the logging functionality and a library to store data in non-volatile flash memory. We are interested in `“bt.h”`, `“esp_bt_main.h”`, `"esp_gap_ble_api.h"` and `“esp_gattc_api.h”`, which expose the BLE APIs required to implement this example.
+These `includes` are required for the FreeRTOS and underlying system components to run, including the logging functionality and a library to store data in non-volatile flash memory. We are interested in `"bt.h"`, `"esp_bt_main.h"`, `"esp_gap_ble_api.h"` and `"esp_gattc_api.h"`, which expose the BLE APIs required to implement this example.

 * `esp_bt.h`: configures the BT controller and VHCI from the host side.
 * `esp_bt_main.h`: initializes and enables the Bluedroid stack.