| /hal_espressif-3.6.0/components/hal/include/hal/ |
| D | readme.md | 3 The HAL layer is designed to be used by the drivers. We don't guarantee the stability and back-comp…
4 versions. The HAL layer may update very frequently with the driver. Please don't use them in the ap…
7 The HAL layer consists of two layers: HAL (upper) and Lowlevel(bottom). The HAL layer defines the s…
8 required by the peripheral. The lowlevel is a translation layer converting general conceptions to r…
12 This layer should be all static inline. The first argument of LL functions is usually a pointer to …
13 of the peripheral register. Each chip should have its own LL layer. The functions in this layer sho…
14 independent from each other so that the upper layer can change/perform one of the options/operation…
19 This layer should depend on the operating system as little as possible. It's a wrapping of LL funct…
20 layer can combine basic steps into different working ways (polling, non-polling, interrupt, etc.). …
21 queues/locks/delay/loop/etc., this layer can be easily port to other os or simulation systems.
[all …]
|
| /hal_espressif-3.6.0/components/bt/host/bluedroid/ |
| D | Kconfig.in | 244 prompt "HCI layer"
248 Define BT trace level for HCI layer
279 prompt "BTM layer"
283 Define BT trace level for BTM layer
314 prompt "L2CAP layer"
318 Define BT trace level for L2CAP layer
349 prompt "RFCOMM layer"
353 Define BT trace level for RFCOMM layer
384 prompt "SDP layer"
388 Define BT trace level for SDP layer
[all …]
|
| /hal_espressif-3.6.0/examples/mesh/manual_networking/ |
| D | README.md | 9 …layer devices are. The pink reprents root; the yellow reprents layer 2; the red reprents layer 3; …
|
| /hal_espressif-3.6.0/examples/mesh/internal_communication/ |
| D | README.md | 21 …example on ESP-WROVER-KIT boards, the RGB light indicator will show you on which layer devices are.
22 …he yellow reprents layer 2; the red reprents layer 3; the blue reprents layer 4; the green reprent…
|
| /hal_espressif-3.6.0/docs/en/api-reference/storage/ |
| D | sdmmc.rst | 27 …The SDMMC protocol layer described in this document handles the specifics of the SD protocol, such…
29 …The protocol layer works with the host via the :cpp:class:`sdmmc_host_t` structure. This structure…
39 Protocol layer API
42 …layer is given the :cpp:class:`sdmmc_host_t` structure. This structure describes the SD/MMC host d…
57 …From the protocol layer's perspective, eMMC memory chips behave exactly like SD memory cards. Even…
111 …layer only in one task. For this reason, the protocol layer does not implement any kind of locking…
|
| /hal_espressif-3.6.0/docs/en/api-guides/esp-ble-mesh/ |
| D | ble-mesh-architecture.rst | 48 …layer is crucial to ESP-BLE-MESH protocol stack which is built on Bluetooth Low-Energy technology,…
70 …Networking`` functions is based on hierarchy structure. Functions of each layer are shown in Table…
81 …ypts, decrypts, and authenticates application data to and from the access layer; it also handles s…
97 …ovisioning`` functions is based on hierarchy structure. Functions of each layer are shown in Table…
108 … transmitted to an unprovisioned device using a Generic Provisioning layer or Proxy protocol layer.
112 … are established such that the transactions from the generic provisioning layer can be delivered t…
126 Functions of each layer are shown in Table 1.3:
166 ``Bearers`` can be taken as a carrier layer based on Bluetooth Low Energy Core, which implements th…
184 Interaction between application layer（``Applications``）and ``API / Event``
186 - Application layer calls API
[all …]
|
| /hal_espressif-3.6.0/examples/mesh/manual_networking/main/ |
| D | mesh_main.c | 49 mesh_assoc_t parent_assoc = { .layer = CONFIG_MESH_MAX_LAYER, .rssi = -120 }; in mesh_scan_done_handler()
64 i, record.ssid, assoc.layer, assoc.layer_cap, assoc.assoc, in mesh_scan_done_handler()
71 … if (assoc.layer < parent_assoc.layer || assoc.layer2_cap < parent_assoc.layer2_cap) { in mesh_scan_done_handler()
80 my_layer = parent_assoc.layer + 1; in mesh_scan_done_handler()
127 parent_record.ssid, parent_assoc.layer, in mesh_scan_done_handler()
|
| D | mesh_light.c | 137 void mesh_connected_indicator(int layer) in mesh_connected_indicator() argument
139 switch (layer) { in mesh_connected_indicator()
|
| /hal_espressif-3.6.0/docs/en/api-guides/ |
| D | esp-wifi-mesh.rst | 115 … nodes. Provided that a path exists between any two nodes on the physical layer (via one or more w…
132 …layer, it will be assigned as a leaf node. This prevents the node from forming any downstream conn…
144 - Current layer of Node
163 …Nodes technically still receive all beacon frames on the MAC layer. The RSSI threshold is an ESP-W…
170 - Which layer the parent node candidate is situated on
173 …layer of the network (including the root node). This helps minimize the total number of layers in …
175 …layer, the parent node candidate with the least child nodes will be preferred. This criteria has t…
184 … shallowest layer are preferred, hence nodes B/C are prioritized since they are second layer nodes…
228 … involves selecting a root node, then forming downstream connections layer by layer until all node…
243 …layer of the network. Once connected, the second layer nodes become intermediate parent nodes (ass…
[all …]
|
| D | hardware-abstraction.rst | 9 2. :ref:`hw-abstraction-ll-layer`
10 3. :ref:`hw-abstraction-hal-layer`
29 …AL are entirely contained within the ``hal`` component. Each layer is dependent on the layer below…
70 …layer is the highest level of ESP-IDF's hardware abstraction. Driver layer API are meant to be cal…
73 .. _hw-abstraction-ll-layer:
104 - LL functions are not thread safe, it is the responsibility of the upper layers (driver layer) to …
107 .. _hw-abstraction-hal-layer:
112 The HAL layer models the operational process of a peripheral as a set of general steps, where each …
|
| /hal_espressif-3.6.0/tools/test_idf_monitor/tests/ |
| D | in2.txt | 165 …ow_sysinfo_timercb, 73]:parent: 00:00:00:00:00:00, mac:30:ae:a4:00:43:84, layer: -1, free heap: 87…
170 I (50551) mesh: [DONE]connect to router:esp-cjq, rssi:-36, 20:a6:80:98:dc:b4[layer:1], rc[30:ae:a4:…
171 …ow_sysinfo_timercb, 73]:parent: 20:a6:80:98:dc:b4, mac:30:ae:a4:00:43:84, layer: 1, free heap: 884…
220 …ow_sysinfo_timercb, 73]:parent: 20:a6:80:98:dc:b4, mac:30:ae:a4:00:43:84, layer: 1, free heap: 717…
311 …ow_sysinfo_timercb, 73]:parent: 20:a6:80:98:dc:b4, mac:30:ae:a4:00:43:84, layer: 1, free heap: 717…
404 …ow_sysinfo_timercb, 73]:parent: 20:a6:80:98:dc:b4, mac:30:ae:a4:00:43:84, layer: 1, free heap: 716…
505 …ow_sysinfo_timercb, 73]:parent: 20:a6:80:98:dc:b4, mac:30:ae:a4:00:43:84, layer: 1, free heap: 716…
596 …ow_sysinfo_timercb, 73]:parent: 20:a6:80:98:dc:b4, mac:30:ae:a4:00:43:84, layer: 1, free heap: 716…
691 …ow_sysinfo_timercb, 73]:parent: 20:a6:80:98:dc:b4, mac:30:ae:a4:00:43:84, layer: 1, free heap: 716…
792 …ow_sysinfo_timercb, 73]:parent: 20:a6:80:98:dc:b4, mac:30:ae:a4:00:43:84, layer: 1, free heap: 716…
[all …]
|
| /hal_espressif-3.6.0/components/esp_wifi/include/ |
| D | esp_mesh_internal.h | 76 uint8_t layer; /**< current layer */ member
102 uint16_t layer; member
|
| /hal_espressif-3.6.0/examples/bluetooth/hci/ |
| D | README.md | 7 This directory includes examples to demonstrate controller interactions by virtual HCI layer and UA…
23 Demonstrates interaction with controller though virtual HCI layer. In this example, simple BLE adve…
|
| /hal_espressif-3.6.0/components/esp_wifi/ |
| D | Kconfig | 46 … it to the high layer TCP/IP stack. The dynamic RX buffer is freed after the higher layer has
66 of each data frame sent by the TCP/IP layer.
93 … For each transmitted data frame from the higher layer TCP/IP stack, the WiFi driver makes a
95 … layer can deliver frames faster than WiFi layer can transmit. In these cases, we may run out
120 … For each transmitted frame from the higher layer TCP/IP stack, the WiFi driver makes a copy
121 … of it in a TX buffer. For some applications, especially UDP applications, the upper layer
122 … can deliver frames faster than WiFi layer can transmit. In these cases, we may run out of TX
|
| /hal_espressif-3.6.0/docs/en/api-reference/bluetooth/nimble/ |
| D | index.rst | 6 …atures of NimBLE including BLE Mesh are supported by ESP-IDF. The porting layer is kept cleaner by…
11 …ESP controller has been added. This is depicted in the figure below. This layer is responsible for…
33 …ci_and_controller_init` to initialize ESP controller as well as transport layer. This will also li…
|
| /hal_espressif-3.6.0/docs/en/api-reference/network/ |
| D | index.rst | 66 Documentation for Application layer network protocols (above the IP Network layer) are provided in …
|
| /hal_espressif-3.6.0/examples/mesh/internal_communication/main/ |
| D | mesh_light.c | 134 void mesh_connected_indicator(int layer) in mesh_connected_indicator() argument
136 switch (layer) { in mesh_connected_indicator()
|
| /hal_espressif-3.6.0/components/hal/ |
| D | README.md | 9 It contains an abstraction layer for ineracting with/driving the hardware found in the SoC such as …
19 …arget-specific HAL headers have the same name and include the abstraction layer HAL header via `in…
|
| /hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_server/tutorial/ |
| D | BLE_Mesh_Node_OnOff_Server_Example_Walkthrough.md | 124 …t allows the BLE Mesh stack to generate events and notify the application layer about important ne…
127 …OSE_EVT`: Generated to notify the application layer that a link has been broken after BLE Mesh bot…
128 …- `ESP_BLE_MESH_NODE_PROV_OUTPUT_NUMBER_EVT`: Received by the application layer if during the conf…
129 …- `ESP_BLE_MESH_NODE_PROV_OUTPUT_STRING_EVT`: Received by the application layer if during the conf…
130 …- `ESP_BLE_MESH_NODE_PROV_INPUT_EVT`: Received by the application layer if during the configuratio…
131 …- `ESP_BLE_MESH_NODE_PROV_COMPLETE_EVT`: Received by the application layer when the provisioning i…
132 …- `ESP_BLE_MESH_NODE_PROV_RESET_EVT`: Received by the application layer when the network reset is …
262 - `user_data`: optional variable for storing the application layer data.
319 …_mesh_cb_t param_cb; /* The callback is only used for the BLE Mesh stack, not for the app layer. */
452 - **Maximum incoming Upper Transport Access PDU length**: Indicates that the access layer can recei…
|
| /hal_espressif-3.6.0/docs/en/api-reference/provisioning/ |
| D | protocomm.rst | 6 …framework for multiple transports. The application can also use protocomm layer directly to have a…
14 … own security (even without using protobuf). One can even use protocomm without any security layer.
145 /* Start protocomm layer on top of BLE */
|
| /hal_espressif-3.6.0/components/esp_eth/test_apps/ |
| D | README.md | 5 This test app is used to test MAC layer behavior with different PHY chips:
|
| /hal_espressif-3.6.0/examples/mesh/manual_networking/main/include/ |
| D | mesh_light.h | 54 void mesh_connected_indicator(int layer);
|
| /hal_espressif-3.6.0/examples/mesh/internal_communication/main/include/ |
| D | mesh_light.h | 54 void mesh_connected_indicator(int layer);
|
| /hal_espressif-3.6.0/examples/bluetooth/hci/ble_adv_scan_combined/ |
| D | CMakeLists.txt | 5 # This example uses an extra component for common functions for Bluetooth HCI layer.
|
| /hal_espressif-3.6.0/examples/bluetooth/hci/controller_vhci_ble_adv/ |
| D | CMakeLists.txt | 5 # This example uses an extra component for common functions for Bluetooth HCI layer.
|
