Home
last modified time | relevance | path

Searched refs:every (Results 101 – 125 of 318) sorted by relevance

12345678910>>...13

/Zephyr-latest/samples/sensor/lps22hh_i3c/
DREADME.rst93 <repeats endlessly every second>
/Zephyr-latest/samples/boards/st/steval_stwinbx1/sensors/
DREADME.rst82 <repeats endlessly every 2s>
/Zephyr-latest/samples/boards/st/sensortile_box/
DREADME.rst80 <repeats endlessly every 2s>
/Zephyr-latest/tests/kernel/timer/timer_behavior/
DKconfig50 Toggles a GPIO pin, on every period, that can be used by an external
/Zephyr-latest/samples/shields/x_nucleo_iks02a1/sensorhub/
DREADME.rst74 <updated endlessly every 2 seconds>
/Zephyr-latest/doc/kernel/services/timing/
Dclocks.rst208 * The driver can ignore calls to :c:func:`sys_clock_set_timeout`, as every
211 * The driver can return zero for every call to :c:func:`sys_clock_elapsed`
226 have every timer interrupt handled on a single processor. Existing
243 :c:func:`sys_clock_set_timeout` is done identically for every CPU.
244 So by default, every CPU will see simultaneous timer interrupts for
245 every event, even though by definition only one of them should see a
/Zephyr-latest/boards/
DKconfig71 execute one instruction every 2^N ns of virtual time. This will
78 The virtual CPU will execute one instruction every 2^N nanoseconds
/Zephyr-latest/doc/develop/languages/c/
Dpicolibc.rst53 versions of Picolibc for every target architecture, along with
60 For every release of Zephyr, the toolchain-bundled Picolibc and the
/Zephyr-latest/doc/services/debugging/
Ddebugmon.rst24 every time the program enters a breakpoint.
/Zephyr-latest/samples/shields/x_nucleo_iks01a3/sensorhub/
DREADME.rst81 <updated endlessly every 2 seconds>
/Zephyr-latest/samples/boards/nordic/battery/
DREADME.rst61 displaying the battery status every five seconds.
/Zephyr-latest/samples/boards/nordic/clock_skew/
DREADME.rst48 Timer wraps every 268 s
/Zephyr-latest/tests/drivers/build_all/sensor/
Dapp.overlay101 /* one entry for every devices at spi.dtsi */
/Zephyr-latest/samples/boards/nordic/nrfx_prs/
DREADME.rst25 When no button is pressed, every 5 seconds a background transfer using SPIM1
/Zephyr-latest/samples/shields/x_nucleo_iks01a3/standard/
DREADME.rst91 <updated endlessly every 2 seconds>
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Daccess.rst105 on every retransmission. This can, for example, be used by models that make
106 use of a Delay parameter, which can be adjusted for every retransmission.
152 When model data changes frequently, storing it on every change may lead to
158 callback for every model that has requested storing of data. The model can
/Zephyr-latest/boards/others/stm32f103_mini/doc/
Dindex.rst104 You will see the LED blinking every second.
/Zephyr-latest/boards/vcc-gnd/yd_stm32h750vb/doc/
Dindex.rst75 You will see the LED blinking every second.
/Zephyr-latest/samples/subsys/display/lvgl/
DREADME.rst11 and a counter at the bottom which increments every second.
/Zephyr-latest/modules/hal_rpi_pico/
DCMakeLists.txt56 # Pico sources and headers necessary for every build.
/Zephyr-latest/samples/boards/espressif/deep_sleep/
DREADME.rst19 a preset time. This example will trigger a wake up every 20 seconds.
/Zephyr-latest/doc/services/storage/nvs/
Dnvs.rst84 Suppose we use a 4 bytes state variable that is changed every minute and
94 writes, with two sectors writing every 171 minutes, the device should last
/Zephyr-latest/boards/st/nucleo_c031c6/doc/
Dindex.rst97 You will see the LED blinking every second.
/Zephyr-latest/boards/st/stm32g0316_disco/doc/
Dindex.rst84 You should see the LED blinking every second.
/Zephyr-latest/drivers/ieee802154/
DKconfig108 Enable support for selectively setting TX channel for every timed transmission request.

12345678910>>...13