mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00

History

Marius Vikhammer 0687daf2c8 kconfig: move remaining kconfig options out of target component The kconfig options are moved to the component where they are used, mostly esp_hw_support and esp_system.		2022-05-23 17:57:45 +08:00
..
main	components/bt: Update licenses	2021-12-08 10:59:06 +08:00
tutorial	Readme for the bluedroid ble50 example with tutorial of walkthrough example.	2021-11-19 12:04:47 +05:30
CMakeLists.txt	component/bt: add BLE v5.0 feature for bluedroid host	2021-01-15 17:55:12 +08:00
README.md	Readme for the bluedroid ble50 example with tutorial of walkthrough example.	2021-11-19 12:04:47 +05:30
sdkconfig.defaults	soc: moved kconfig options out of the target component.	2022-04-21 12:09:43 +08:00
sdkconfig.defaults.esp32c3	soc: moved kconfig options out of the target component.	2022-04-21 12:09:43 +08:00
sdkconfig.defaults.esp32s3	kconfig: move remaining kconfig options out of target component	2022-05-23 17:57:45 +08:00

README.md

Supported Targets	ESP32-C3	ESP32-S3

ESP-IDF Gatt Security Client Example

This example shows how to use the ESP BLE5.0 security APIs to connect in secure manner with peer device and use encryption for data exchange.

How to Use Example

Before project configuration and build, be sure to set the correct chip target using:

idf.py set-target <chip_name>

To test this demo, you can run the ble50_security_server_demo, which starts advertising and can be connected to this demo automatically.

There are some important points for this demo:

esp_ble_gap_set_security_param should be used to set the security parameters in the initial stage;
esp_ble_set_encryption should be used to start encryption with peer device. If the peer device initiates the encryption, 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.
The gatt_security_client_demo will receive a ESP_GAP_BLE_AUTH_CMPL_EVT once the encryption procedure has completed.

Please, check this tutorial for more information about this example.

Hardware Required

A development board with ESP32-C3 SoC, ESP32-S3 SoC and BT5.0 supported chip (e.g., ESP32-C3-DevKitC-1 etc.)
A USB cable for Power supply and programming

See Development Boards for more information about it.

Build and Flash

Run idf.py -p PORT flash monitor to build, flash and monitor the project.

(To exit the serial monitor, type Ctrl-].)

See the Getting Started Guide for full steps to configure and use ESP-IDF to build projects.

Example Output

I (364) BTDM_INIT: BT controller compile version [3e61eea]
I (374) coexist: coexist rom version 8459080
I (374) phy_init: phy_version 500,985899c,Apr 19 2021,16:05:08
I (494) system_api: Base MAC address is not set
I (494) system_api: read default base MAC address from EFUSE
I (494) BTDM_INIT: Bluetooth MAC: 7c:df:a1:40:01:dd

I (514) SEC_GATTC_DEMO: EVT 0, gattc if 3
I (514) SEC_GATTC_DEMO: REG_EVT
I (524) SEC_GATTC_DEMO: Scan start success
I (2654) SEC_GATTC_DEMO: legacy adv, adv type 0x13 data len 31
I (2654) SEC_GATTC_DEMO: legacy adv, adv type 0x1b data len 21
I (3624) SEC_GATTC_DEMO: legacy adv, adv type 0x13 data len 31
I (3624) SEC_GATTC_DEMO: legacy adv, adv type 0x1b data len 21
I (4594) SEC_GATTC_DEMO: legacy adv, adv type 0x13 data len 31
I (4594) SEC_GATTC_DEMO: legacy adv, adv type 0x1b data len 21
I (5514) SEC_GATTC_DEMO: legacy adv, adv type 0x13 data len 31
I (5524) SEC_GATTC_DEMO: legacy adv, adv type 0x1b data len 0
I (7494) SEC_GATTC_DEMO: legacy adv, adv type 0x13 data len 31
I (7494) SEC_GATTC_DEMO: legacy adv, adv type 0x1b data len 21
I (8614) SEC_GATTC_DEMO: legacy adv, adv type 0x13 data len 31
I (8614) SEC_GATTC_DEMO: legacy adv, adv type 0x1b data len 0

Troubleshooting

For any technical queries, please open an issue on GitHub. We will get back to you soon.