mirror of
https://github.com/espressif/esp-idf.git
synced 2024-10-05 20:47:46 -04:00
Merge branch 'feature/multiple_prs_from_github' into 'master'
Feature/multiple PRs from github Closes IDFGH-3877, IDFGH-4090, IDFGH-4641, IDFGH-4666, and IDFGH-4854 See merge request espressif/esp-idf!12858
This commit is contained in:
commit
b603a0bea0
@ -19,7 +19,7 @@
|
||||
#if (CONFIG_GATTS_ENABLE || CONFIG_GATTC_ENABLE)
|
||||
#include "esp_gatt_defs.h"
|
||||
#endif
|
||||
const char *TAG = "hid_parser";
|
||||
static const char *TAG = "hid_parser";
|
||||
|
||||
typedef struct {
|
||||
uint16_t appearance;
|
||||
|
@ -14,6 +14,10 @@
|
||||
|
||||
#pragma once
|
||||
|
||||
#ifdef __cplusplus
|
||||
extern "C" {
|
||||
#endif
|
||||
|
||||
#include "esp_err.h"
|
||||
|
||||
/**
|
||||
@ -31,3 +35,7 @@ esp_err_t esp_tusb_init_console(int cdc_intf);
|
||||
* @return esp_err_t
|
||||
*/
|
||||
esp_err_t esp_tusb_deinit_console(int cdc_intf);
|
||||
|
||||
#ifdef __cplusplus
|
||||
}
|
||||
#endif
|
||||
|
@ -29,7 +29,7 @@ Example to tune the stack size of the pthread:
|
||||
cfg.stack_size = (4 * 1024);
|
||||
esp_pthread_set_cfg(&cfg);
|
||||
|
||||
pthread_create(&t1, NULL, thread_func);
|
||||
pthread_create(&t1, NULL, thread_func, NULL);
|
||||
}
|
||||
|
||||
The API can also be used for inheriting the settings across threads. For example:
|
||||
@ -48,7 +48,7 @@ The API can also be used for inheriting the settings across threads. For example
|
||||
{
|
||||
printf("In my_thread1\n");
|
||||
pthread_t t2;
|
||||
pthread_create(&t2, NULL, my_thread2);
|
||||
pthread_create(&t2, NULL, my_thread2, NULL);
|
||||
|
||||
return NULL;
|
||||
}
|
||||
@ -62,7 +62,7 @@ The API can also be used for inheriting the settings across threads. For example
|
||||
cfg.inherit_cfg = true;
|
||||
esp_pthread_set_cfg(&cfg);
|
||||
|
||||
pthread_create(&t1, NULL, my_thread1);
|
||||
pthread_create(&t1, NULL, my_thread1, NULL);
|
||||
}
|
||||
|
||||
API Reference
|
||||
|
@ -437,7 +437,7 @@ esp_log_buffer_hex(GATTC_TAG, gl_profile_tab[PROFILE_A_APP_ID].remote_bda,
|
||||
sizeof(esp_bd_addr_t));
|
||||
```
|
||||
|
||||
The typical MTU size for a Bluetooth 4.0 connection is 23 bytes. A client can change the size of MUT, using `esp_ble_gattc_send_mtu_req()` function, which takes the GATT interface and the connection ID. The size of the requested MTU is defined by `esp_ble_gatt_set_local_mtu()`. The server can then accept or reject the request. The ESP32 supports a MTU size of up to 517 bytes, which is defined by the `ESP_GATT_MAX_MTU_SIZE` in `esp_gattc_api.h`. In this example, the MTU size is set to 500 bytes. In case the configuration fails, the returned error is printed:
|
||||
The typical MTU size for a Bluetooth 4.0 connection is 23 bytes. A client can change the size of MTU, using `esp_ble_gattc_send_mtu_req()` function, which takes the GATT interface and the connection ID. The size of the requested MTU is defined by `esp_ble_gatt_set_local_mtu()`. The server can then accept or reject the request. The ESP32 supports a MTU size of up to 517 bytes, which is defined by the `ESP_GATT_MAX_MTU_SIZE` in `esp_gattc_api.h`. In this example, the MTU size is set to 500 bytes. In case the configuration fails, the returned error is printed:
|
||||
|
||||
```c
|
||||
esp_err_t mtu_ret = esp_ble_gattc_send_mtu_req (gattc_if, conn_id);
|
||||
|
@ -22,6 +22,8 @@ Right after provisioning is complete, BLE is turned off and disabled to free the
|
||||
|
||||
This example can be used, as it is, for adding a provisioning service to any application intended for IoT.
|
||||
|
||||
> Note: If you use this example code in your own project, in BLE mode, then remember to enable the BT stack and BTDM BLE control settings in your SDK configuration (e.g. by using the `sdkconfig.defaults` file from this project).
|
||||
|
||||
## How to use example
|
||||
|
||||
### Hardware Required
|
||||
|
@ -271,6 +271,10 @@ void app_main(void)
|
||||
0xb4, 0xdf, 0x5a, 0x1c, 0x3f, 0x6b, 0xf4, 0xbf,
|
||||
0xea, 0x4a, 0x82, 0x03, 0x04, 0x90, 0x1a, 0x02,
|
||||
};
|
||||
|
||||
/* If your build fails with linker errors at this point, then you may have
|
||||
* forgotten to enable the BT stack or BTDM BLE settings in the SDK (e.g. see
|
||||
* the sdkconfig.defaults in the example project) */
|
||||
wifi_prov_scheme_ble_set_service_uuid(custom_service_uuid);
|
||||
#endif /* CONFIG_EXAMPLE_PROV_TRANSPORT_BLE */
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user