Searched refs:lost (Results 1 – 25 of 52) sorted by relevance
123
/Zephyr-latest/samples/bluetooth/iso_connected_benchmark/ |
D | README.rst | 76 …00:17.774,902] <inf> iso_connected: Overall : Received 100/100 (100.00%) - Total packets lost 0 77 …00:17.774,932] <inf> iso_connected: Current Conn: Received 100/100 (100.00%) - Total packets lost 0 78 …00:17.774,963] <inf> iso_connected: Latest 1000 : Received 100/100 (100.00%) - Total packets lost 0 81 …00:18.532,409] <inf> iso_connected: Overall : Received 200/200 (100.00%) - Total packets lost 0 82 …00:18.532,470] <inf> iso_connected: Current Conn: Received 200/200 (100.00%) - Total packets lost 0 83 …00:18.532,501] <inf> iso_connected: Latest 1000 : Received 200/200 (100.00%) - Total packets lost 0 111 …00:05.072,052] <inf> iso_connected: Overall : Received 100/100 (100.00%) - Total packets lost 0 112 …00:05.072,113] <inf> iso_connected: Current Conn: Received 100/100 (100.00%) - Total packets lost 0 113 …00:05.072,143] <inf> iso_connected: Latest 1000 : Received 100/100 (100.00%) - Total packets lost 0 116 …00:05.829,589] <inf> iso_connected: Overall : Received 200/200 (100.00%) - Total packets lost 0 [all …]
|
/Zephyr-latest/samples/bluetooth/iso_broadcast_benchmark/ |
D | README.rst | 82 …39,343] <inf> iso_broadcast_receiver: Overall : Received 99/100 (99.00%) - Total packets lost 1 83 …39,343] <inf> iso_broadcast_receiver: Current Sync: Received 99/100 (99.00%) - Total packets lost 1 84 …39,373] <inf> iso_broadcast_receiver: Latest 1000 : Received 99/100 (99.00%) - Total packets lost 1 85 …9,388] <inf> iso_broadcast_receiver: Overall : Received 199/200 (99.50%) - Total packets lost 1 86 …9,388] <inf> iso_broadcast_receiver: Current Sync: Received 199/200 (99.50%) - Total packets lost 1 87 …9,388] <inf> iso_broadcast_receiver: Latest 1000 : Received 199/200 (99.50%) - Total packets lost 1
|
/Zephyr-latest/scripts/coccinelle/ |
D | find_dev_usage.cocci | 9 // is not lost. 30 check if const qualifier is not lost".format(F, f, D)
|
/Zephyr-latest/drivers/retained_mem/ |
D | Kconfig | 8 device is powered (may be lost in low power states).
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | retained_mem.rst | 11 powered (data may be lost in low power modes).
|
/Zephyr-latest/samples/boards/bbc/microbit/pong/src/ |
D | ble.c | 117 uint8_t lost = BLE_LOST; in ble_send_lost() local 125 err = bt_gatt_notify(default_conn, local_attr, &lost, sizeof(lost)); in ble_send_lost()
|
/Zephyr-latest/doc/develop/ |
D | env_vars.rst | 36 will be lost forever. 102 The value will be lost if you close the window, etc.; run ``source 116 The value will be lost if you close the window, etc.; run
|
/Zephyr-latest/subsys/net/lib/mqtt_sn/ |
D | Kconfig | 91 int "Number of missed Advertise messages before considering GW lost"
|
/Zephyr-latest/samples/subsys/shell/fs/ |
D | README.rst | 90 If the buffer is too small then some data may be lost during transfer of large 119 (if the file is loaded in chunks greater than 64B the data is lost and isn't
|
/Zephyr-latest/subsys/logging/backends/ |
D | Kconfig.rtt | 79 case of heavy traffic data can be lost and it may be necessary to
|
/Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
D | main.rst | 19 …`network management <net_mgmt_interface>` events indicating when IP connectivity is gained or lost. 68 A ready iface ceases to be ready the moment any of the above conditions is lost. 108 LOG_INF("Network connectivity lost!"); 266 If connectivity is lost due to external factors, the connectivity implementation will mark the ifac…
|
/Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/ |
D | README.txt | 16 Since, coverage data is stored in the RAM, it is lost when watchdog fires.
|
/Zephyr-latest/drivers/serial/ |
D | Kconfig.nrfx_uart_instance | 62 that with higher speeds and/or high cpu load some data can be lost.
|
/Zephyr-latest/drivers/wifi/esp_at/ |
D | Kconfig.esp_at | 86 lost if the driver cannot empty the device buffer quickly enough.
|
/Zephyr-latest/subsys/net/ip/ |
D | Kconfig.tcp | 171 When a packet is lost, the receiver will keep acknowledging the 174 this can be deduced as that the packet afterwards must have been lost.
|
/Zephyr-latest/drivers/console/ |
D | Kconfig | 155 heavy traffic data can be lost and it may be necessary to increase 163 be lost and it may be necessary to increase delay or number of
|
/Zephyr-latest/doc/services/storage/disk/ |
D | access.rst | 49 corrupted if power is lost or if the card is removed without unmounting
|
/Zephyr-latest/scripts/ci/ |
D | pylintrc | 201 lost-exception,
|
/Zephyr-latest/cmake/linker/armlink/ |
D | scatter_script.cmake | 424 file(APPEND ${STEERING_C} " * AUTO-GENERATED - All changes will be lost\n") 442 file(APPEND ${STEERING_FILE} "; AUTO-GENERATED - All changes will be lost\n")
|
/Zephyr-latest/boards/snps/em_starterkit/doc/ |
D | index.rst | 275 If power is lost, the application will also lost due to power loss.
|
/Zephyr-latest/boards/snps/iotdk/doc/ |
D | index.rst | 166 power is removed, the application will be lost since it wasn't written to flash.
|
/Zephyr-latest/subsys/net/lib/dhcpv4/ |
D | Kconfig | 165 leases. As a result, all leases are lost on reboot, which can cause
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | dfu.rst | 320 The firmware distribution procedure only fails if *all* Target nodes are lost. It is up to the 322 attempts to update the lost Target nodes after the current attempt is finished.
|
/Zephyr-latest/boards/snps/emsdp/doc/ |
D | index.rst | 261 If power is removed, the application will be lost since it wasn't written to flash.
|
/Zephyr-latest/modules/hostap/ |
D | Kconfig | 78 # log messages can be lost. So, we set the log mode to immediate
|
123