eaw/esp-idf
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

ble_mesh: Fix typos

Browse Source
This commit is contained in:
lly
2020-05-12 15:31:26 +08:00
parent bd920d22b0
commit 6b9c0dda08
25 changed files with 66 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_server/tutorial/BLE_Mesh_Node_OnOff_Server_Example_Walkthrough.md
View File

@@ -17,7 +17,7 @@ This demo has only one element, in which the following two models are implemente
## 2. Code Analysis
### 2.1 Foler Structure
### 2.1 Folder Structure
The folder `ble_mesh_node` contains the following files and subfolders:
@@ -261,7 +261,7 @@ The block above shows a specific implementation of the model structure. Although
- `pub`: structure that needs to be defined if the Model structure supports the Publish function.
- `user_data`: optional variable for storing the application layer data.
The other structures and variables (keys, group, element) get their values through the BLE Mesh stack during the initialization or configuration stages. You are not reqiured to initialize them.
The other structures and variables (keys, group, element) get their values through the BLE Mesh stack during the initialization or configuration stages. You are not required to initialize them.
The next code block presents the definition of the model structure, and the `root_models[]` array. This array is used for indicating the number of the existing model structures. A model is implemented by using a macro.
@@ -274,7 +274,7 @@ static esp_ble_mesh_model_t root_models[] = {
};
```
Different models require different macros. The exisitng types of models and their respective macros needed for implementation are given in the table below.
Different models require different macros. The existing types of models and their respective macros needed for implementation are given in the table below.
| | Model Name | Macro Required for its Definition |
| --------------- | ---- | ----------------------------- |
@@ -385,9 +385,9 @@ The list of configuration options in BLE Mesh menuconfig is stored in `Component
```
—— Bluetooth Mesh support
[*] Suppoft for BLE Mesh Node
[ ] Support for BLE lqesh Provisioner
[*] Provisiosing support using the advertising bearer (PB-ADV)
[*] Support for BLE Mesh Node
[ ] Support for BLE Mesh Provisioner
[*] Provisioning support using the advertising bearer (PB-ADV)
[*] net buffer pool usage
[*] Provisioning support using GATT (PB-GATT)
[*] GATT Proxy Service

2
examples/bluetooth/esp_ble_mesh/ble_mesh_vendor_model/vendor_server/main/ble_mesh_demo_main.c
View File

@@ -161,7 +161,7 @@ static void example_ble_mesh_custom_model_cb(esp_ble_mesh_model_cb_event_t event
param->model_operation.ctx, ESP_BLE_MESH_VND_MODEL_OP_STATUS,
sizeof(tid), (uint8_t *)&tid);
if (err) {
ESP_LOGE(TAG, "Faild to send message 0x%06x", ESP_BLE_MESH_VND_MODEL_OP_STATUS);
ESP_LOGE(TAG, "Failed to send message 0x%06x", ESP_BLE_MESH_VND_MODEL_OP_STATUS);
}
}
break;

2
examples/bluetooth/esp_ble_mesh/ble_mesh_wifi_coexist/main/ble_mesh_demo_main.c
View File

@@ -518,7 +518,7 @@ static void example_ble_mesh_custom_model_cb(esp_ble_mesh_model_cb_event_t event
param->client_send_timeout.model,
param->client_send_timeout.ctx);
if (err != ESP_OK) {
ESP_LOGE(TAG, "%s: Faield to resend fast prov client message", __func__);
ESP_LOGE(TAG, "%s: Failed to resend fast prov client message", __func__);
return;
}
break;

6
examples/bluetooth/esp_ble_mesh/ble_mesh_wifi_coexist/tutorial/BLE_Mesh_WiFi_Coexist_Example_Walkthrough.md
View File

@@ -13,7 +13,7 @@ This demo demonstrates the Wi-Fi and Bluetooth (BLE/BR/EDR) coexistence feature
Download and flash the `ble_mesh_wifi_coexist` project to your ESP32 development board and then use the following commands to get started with this demo.
1. Connect your development board to the Wi-Fi network by entering the `sta ssid password` command in your serial port tool.
- For example, you should enter `sta tset_wifi 12345678` if you want to connect your board to a network with a SSID of `tset_wifi` and a password of `12345678`.
- For example, you should enter `sta test_wifi 12345678` if you want to connect your board to a network with a SSID of `test_wifi` and a password of `12345678`.
2. Start a TCP server by entering the `iperf -s -i 3 -t 1000` command in your serial port tool, which prints the current transfer rate of the Wi-Fi network the board connects to.
@@ -48,7 +48,7 @@ $ tree examples/bluetooth/esp_ble_mesh/ble_mesh/ble_mesh_wifi_coexist
The `main` folder mainly implements the BLE Mesh feature. Details can be seen in `ble_mesh_fast_prov_server`.
The `components` folder mainly implements the Wi-Fi feature, which allows some basic commands and `iperf-relared` test commands.
The `components` folder mainly implements the Wi-Fi feature, which allows some basic commands and `iperf-related` test commands.
> Note:
>
@@ -205,7 +205,7 @@ static esp_err_t ble_mesh_init(void)
return ESP_OK;
}
```
2. Rregister the provisioning callback function in the BLE Mesh stack with `esp_ble_mesh_register_prov_callback(esp_ble_mesh_prov_cb)`, among which `esp_ble_mesh_prov_cb` is used to handle events thrown by protocol stations. This requires the user to implement it himself, and also needs to know the meaning of the event and how to trigger it. For example: The `ESP_BLE_MESH_PROVISIONER_PROV_LINK_OPEN_EVT` event is triggered when the provisioner starts provisioning unprovisioned device, and is handled in the `example_ble_mesh_provisioning_cb` function. Note that you need to register this function with the BLE Mesh protocol stack by calling the `esp_ble_mesh_register_prov_callback` API.
2. Register the provisioning callback function in the BLE Mesh stack with `esp_ble_mesh_register_prov_callback(esp_ble_mesh_prov_cb)`, among which `esp_ble_mesh_prov_cb` is used to handle events thrown by protocol stations. This requires the user to implement it himself, and also needs to know the meaning of the event and how to trigger it. For example: The `ESP_BLE_MESH_PROVISIONER_PROV_LINK_OPEN_EVT` event is triggered when the provisioner starts provisioning unprovisioned device, and is handled in the `example_ble_mesh_provisioning_cb` function. Note that you need to register this function with the BLE Mesh protocol stack by calling the `esp_ble_mesh_register_prov_callback` API.
```c
ESP_BLE_MESH_PROVISIONER_PROV_LINK_OPEN_EVT, /*!< Provisioner establish a BLE Mesh link event */