Home
last modified time | relevance | path

Searched refs:attempt (Results 1 – 25 of 80) sorted by relevance

1234

/Zephyr-latest/samples/drivers/led/is31fl3733/
DKconfig11 wired up to your IS31FL3733 LED driver. The sample will only attempt
19 to your IS31FL3733 LED driver. The sample will only attempt to drive
/Zephyr-latest/subsys/modem/
Dmodem_ubx.c141 int ret, attempt; in modem_ubx_run_script() local
158 for (attempt = 0; attempt < script->retry_count; ++attempt) { in modem_ubx_run_script()
161 LOG_INF("Successfully executed script on attempt: %d.", attempt); in modem_ubx_run_script()
169 LOG_ERR("Failed to execute script successfully. Attempts: %d.", attempt); in modem_ubx_run_script()
/Zephyr-latest/samples/drivers/charger/
DREADME.rst15 - If power is provided to the charger, then the sample application will attempt to enable the charge
21 Note that this sample terminates once the charge cycle completes and does not attempt to "top-off"
/Zephyr-latest/doc/connectivity/networking/conn_mgr/
Dimplementation.rst222 In other words, the connectivity implementation should not give up on the connection attempt, even …
282 … implementations to have potentially unexpected behavior if applications attempt to directly contr…
284 …ntation to interpret this as an unexpected connection loss and immediately attempt to re-associate.
306 …ember:`conn_mgr_conn_api.connect` must eventually lead to an association attempt, even if called i…
381 Do not attempt to prevent the use of built-in features (such as :ref:`conn_mgr_control_persistence_…
384 Implementations must not attempt to force certain features to be always enabled or always disabled.
424 …for the iface, the connectivity implementation should immediately cancel this reconnection attempt.
425 …attempt times out on an iface whose underlying technology does not have a built-in timeout, the co…
443 Many underlying technologies do not usually associate in a single attempt.
447 … treat this series of back-to-back association sub-attempts as a single unified connection attempt.
[all …]
Dmain.rst268 … :ref:`persistence <conn_mgr_control_persistence>` is set, the iface may then attempt to reconnect.
278 A new connection attempt will not be initiated, regardless of whether persistence is enabled.
302 When :c:func:`conn_mgr_if_connect` is called on an iface, a connection attempt begins.
304 The connection attempt continues indefinitely until it succeeds, unless a timeout has been specifie…
306 In that case, the connection attempt will be abandoned if the timeout elapses before it succeeds.
318 If persistence is enabled, any unintentional connection loss will initiate a new connection attempt…
320 Otherwise, the iface will not attempt to reconnect.
323 Persistence not does affect connection attempt behavior.
326 …For instance, if a connection attempt on an iface times out, the iface will not attempt to reconne…
356 …when an :ref:`iface association <conn_mgr_control_operation_connecting>` attempt :ref:`times out <…
/Zephyr-latest/arch/arm/core/cortex_m/
Dvector_table_pad.ld9 * Zephyr image does not attempt to use the area which we reserve to
/Zephyr-latest/doc/hardware/arch/
Dxtensa.rst44 The behavior is undefined, if two or more threads attempt to use
45 the HiFi registers, as the kernel does not attempt to detect
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig28 int "Delay for notification sending retried attempt in 1.25 ms units"
/Zephyr-latest/doc/hardware/peripherals/
Ddma.rst28 attempt to wrap a channel with kernel synchronization primitives such as mutexes or semaphores. If
38 Drivers should not attempt to use heap allocations of any kind. If object pools are needed for
/Zephyr-latest/subsys/net/lib/lwm2m/
DREADME_lwm2m24 If the patch fails to apply, you can attempt to use the 3-way merge capabilities by committing the …
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Ddfd_srv.rst27 specific, and may contain data from other vendors. The application should never attempt to execute
/Zephyr-latest/doc/kernel/services/data_passing/
Dpipes.rst32 satisfied, then the operation will either fail immediately or attempt to send
39 will either fail immediately or attempt to receive as many bytes as possible
58 allows it to send/receive data to/from one provided it does not attempt
Dlifos.rst37 data queues. Any attempt to re-add a LIFO data item to a queue before
54 the ISR must not attempt to wait if the LIFO is empty.
Dfifos.rst37 data queues. Any attempt to re-add a FIFO data item to a queue before
54 the ISR must not attempt to wait if the FIFO is empty.
Dstacks.rst50 the ISR must not attempt to wait if the stack is empty.
/Zephyr-latest/subsys/mgmt/mcumgr/grp/settings_mgmt/
DKconfig66 settings read or write attempt is made.
/Zephyr-latest/subsys/net/l2/ieee802154/
DKconfig.radio54 The maximum number of backoffs the CSMA-CA algorithm will attempt
/Zephyr-latest/drivers/ieee802154/
DKconfig.cc13xx_cc26xx35 The maximum number of backoffs the CSMA-CA algorithm will attempt
/Zephyr-latest/drivers/misc/coresight/
DKconfig56 Determines how often attempt to dump the data is performed.
/Zephyr-latest/subsys/mgmt/mcumgr/transport/
DKconfig.bluetooth102 option specifies the time of the next update attempt.
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dfetch_and_get.rst24 a locking mechanism is undefined and most sensor drivers do not attempt to
/Zephyr-latest/cmake/modules/
DFindBabbleSim.cmake15 # If these are not set, as a fallback we attempt to find it through west, in case the user
/Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/
DREADME.rst79 Using the default config, the application will use DHCP to acquire an IP address and attempt
91 - The application will then attempt to connect to the public Mosquitto broker
/Zephyr-latest/doc/kernel/services/synchronization/
Dsemaphores.rst49 not attempt to wait if the semaphore is unavailable.
/Zephyr-latest/subsys/fs/
DKconfig.fatfs41 This option adds code that allows fs_mount to attempt to format
46 destroy your disk, if mount attempt fails. In case when your

1234