| /hal_espressif-2.7.6/components/bt/esp_ble_mesh/mesh_models/server/ |
| D | sensor_server.c | 53 state = &srv->states[i]; in send_sensor_descriptor_status()
71 state = &srv->states[i]; in send_sensor_descriptor_status()
120 state = &srv->states[i]; in send_sensor_data_status()
148 state = &srv->states[i]; in send_sensor_data_status()
201 state = &srv->states[i]; in send_sensor_cadence_status()
312 state = &srv->states[i]; in send_sensor_settings_status()
349 state = &srv->states[i]; in find_sensor_setting()
446 state = &srv->states[i]; in send_sensor_column_status()
521 state = &srv->states[i]; in send_sensor_series_status()
602 if (srv->state_count == 0U || srv->states == NULL) { in sensor_get()
[all …]
|
| /hal_espressif-2.7.6/components/esp_timer/test/ |
| D | test_esp_timer.c | 497 test_state_t states[portNUM_PROCESSORS] = {0}; variable
500 states[i].done = done;
501 xTaskCreatePinnedToCore(&timer_test_task, "test", 4096, &states[i], 6, NULL, i);
507 i, states[i].pass ? "PASS" : "FAIL",
508 states[i].test_cnt, states[i].error_cnt,
509 (int) states[i].avg_diff, (int) states[i].max_error);
517 TEST_ASSERT(states[i].pass);
|
| /hal_espressif-2.7.6/components/bt/esp_ble_mesh/mesh_models/server/include/ |
| D | sensor_server.h | 180 struct bt_mesh_sensor_state *states; member
187 struct bt_mesh_sensor_state *states; member
|
| /hal_espressif-2.7.6/components/bt/esp_ble_mesh/mesh_core/include/ |
| D | mesh_hci.h | 49 uint64_t states; member
|
| /hal_espressif-2.7.6/examples/bluetooth/esp_ble_mesh/ble_mesh_sensor_model/sensor_client/ |
| D | README.md | 11 Sensor Server model is model which is used to expose a series of sensor states. When Sensor Server …
52 The sensor server model supports two instances of Sensor states, the first one (Sensor Property ID …
54 Currently only the Sensor Descriptor state, Sensor Data state are supported by the Sensor states. T…
|
| /hal_espressif-2.7.6/components/bt/esp_ble_mesh/api/models/include/ |
| D | esp_ble_mesh_sensor_model_api.h | 536 esp_ble_mesh_sensor_state_t *states; /*!< Parameters of the Sensor states */ member
544 esp_ble_mesh_sensor_state_t *states; /*!< Parameters of the Sensor states */ member
|
| /hal_espressif-2.7.6/examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_client/ |
| D | README.md | 12 4. The Generic OnOff Client will start to get and set Generic OnOff states periodically.
|
| /hal_espressif-2.7.6/docs/en/api-reference/peripherals/ |
| D | sd_pullup_requirements.rst | 4 …cts are designed for multiple use cases which may require different pull states on pins. For this …
16 …rview of compatibility`_ between the default pull states on pins of Espressif's products and the s…
282 …D and DATA pins. The table below shows the default pull-up and pull-down states of the CMD and DAT…
290 .. list-table:: Default pull-up and pull-down states of the CMD and DATA pins
|
| D | pcnt.rst | 18 * :ref:`pcnt-api-using-interrupts` - presents how to trigger interrupts on specific states of the c…
|
| D | twai.rst | 263 …ct states and strict rules regarding the functions or conditions that trigger a state transition. …
458 //Reconfigure alerts to detect Error Passive and Bus-Off error states
|
| D | uart.rst | 241 There are many interrupts that can be generated following specific UART states or detected errors. …
|
| /hal_espressif-2.7.6/docs/en/api-guides/esp-ble-mesh/ |
| D | ble-mesh-terminology.rst | 49 …ESH network has an independent set of state values that indicate certain states of the device, lik…
52 …nes basic functionalities of nodes, like the states needed by the nodes, the messages controlling …
190 … Model, which is responsible for maintaining configuration-related states. The states that Configu…
196 …er Model is primarily used by devices to check their states and see if there is an error. The stat…
|
| D | ble-mesh-faq.rst | 33 1.2 If a Provisioner wants to change states of a node, what requirements should be met for a Provis…
383 …- Model has two types, client model and server model. Client model can get and set the states of s…
|
| /hal_espressif-2.7.6/components/wear_levelling/doc/ |
| D | wl_sw_structure.rst | 63 …n about the WLC state. The States region contains two copies of the WLC states. It is implemented…
64 during operation when the device stores the states. If one of copies is wrong, the WLC can recover …
|
| /hal_espressif-2.7.6/examples/bluetooth/esp_ble_mesh/ble_mesh_sensor_model/sensor_server/main/ |
| D | main.c | 119 .states = sensor_states,
127 .states = sensor_states,
|
| /hal_espressif-2.7.6/docs/en/api-reference/system/ |
| D | ota.rst | 75 …boot` are optional, and ``ESP_OTA_IMG_NEW`` and ``ESP_OTA_IMG_PENDING_VERIFY`` states are not used.
114 Where the states are set
117 A brief description of where the states are set:
|
| D | efuse.rst | 227 There are some eFuse APIs useful to work with states of keys.
|
| /hal_espressif-2.7.6/docs/en/api-guides/ |
| D | deep-sleep-stub.rst | 13 * As the SoC has freshly woken from sleep, most of the peripherals are in reset states. The SPI fla…
|
| D | core_dump.rst | 21 …bug session with this file. User can examine memory, variables and tasks states manually. Note tha…
|
| D | startup.rst | 30 … the boot mode by checking ``GPIO_STRAP_REG`` register for bootstrap pin states. Depending on the …
|
| /hal_espressif-2.7.6/examples/bluetooth/esp_ble_mesh/ble_mesh_fast_provision/fast_prov_server/tutorial/ |
| D | BLE_Mesh_Fast_Prov_Server_Example_Walkthrough.md | 67 In the struct, there are three variables that are related to roles and states, which are described …
185 The `fast_prov_server` struct represents the Vendor server's states. The `CID_ESP` and `ESP_BLE_MES…
|
| /hal_espressif-2.7.6/examples/bluetooth/esp_ble_mesh/ble_mesh_node/onoff_server/tutorial/ |
| D | BLE_Mesh_Node_OnOff_Server_Example_Walkthrough.md | 302 - Consists of one or multiple states that can exist across different elements
342 It presents the opcodes, corresponding to the three states, defined in this demo: OnOff Get, OnOff …
344 …nOff Server Model is to be implemented in this demo, the following three states requested by the G…
|
| /hal_espressif-2.7.6/components/nvs_flash/ |
| D | README.rst | 75 …bers correspond to pages which were created later. Each page can be in one of the following states:
99 | Full +---> | Full +---> | Active | | Empty | <- states
146 Each entry can be in one of the following three states represented with two bits in the entry state…
|
| /hal_espressif-2.7.6/components/esptool_py/ |
| D | project_include.cmake | 236 # its name states, it marks whether the image should be flashed as plain text or
|
| /hal_espressif-2.7.6/tools/windows/tool_setup/ |
| D | system_check_page.iss.inc | 4 { SystemCheck states }
|
