Home
last modified time | relevance | path

Searched refs:every (Results 76 – 100 of 318) sorted by relevance

12345678910>>...13

/Zephyr-latest/samples/modules/lvgl/accelerometer_chart/
DREADME.rst14 timer fetches the latest acceleration data from the sensor every 20 ms (default value) and updates
/Zephyr-latest/samples/sensor/lsm6dsl/
DREADME.rst77 <repeats endlessly every 2 seconds>
/Zephyr-latest/samples/sensor/lis2dh/
DREADME.rst76 <repeats endlessly every 2 seconds>
/Zephyr-latest/samples/drivers/stepper/generic/
DREADME.rst22 The sample also has a monitor thread that prints the actual position of the stepper motor every
/Zephyr-latest/samples/sensor/grove_temperature/
DREADME.rst11 console, in units of celsius, once every second. When the :kconfig:option:`CONFIG_GROVE_LCD_RGB`
/Zephyr-latest/samples/shields/x_nucleo_iks4a1/standard/
DREADME.rst66 <updated endlessly every 2 seconds>
/Zephyr-latest/subsys/logging/backends/
DKconfig.fs40 When disabled backend creates a new log file on every startup.
/Zephyr-latest/tests/bsim/bluetooth/host/misc/sample_test/
DCMakeLists.txt25 # List every source file in the test application. Do not use GLOB.
/Zephyr-latest/soc/mediatek/mt8xxx/
DCMakeLists.txt33 # should live in SOF where it doesn't have to be duplicated for every
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dheartbeat.rst40 The node publishes a new Heartbeat message every time a feature changes. The
/Zephyr-latest/samples/boards/st/sensortile_box_pro/sensors-on-board/
DREADME.rst75 <repeats endlessly every 2s>
/Zephyr-latest/samples/drivers/adc/adc_dt/
DREADME.rst55 You should get a similar output as below, repeated every second:
/Zephyr-latest/samples/drivers/adc/adc_sequence/
DREADME.rst48 You should get a similar output as below, repeated every second:
/Zephyr-latest/samples/subsys/nvs/
DREADME.rst12 a counter is incremented on every reboot and stored in flash,
/Zephyr-latest/samples/subsys/shell/devmem_load/
DREADME.md3 The `devmem load` command is supported by every transport the shell can run on.
/Zephyr-latest/samples/shields/x_nucleo_iks01a2/sensorhub/
DREADME.rst65 <updated endlessly every 2 seconds>
/Zephyr-latest/samples/shields/x_nucleo_iks01a2/standard/
DREADME.rst65 <updated endlessly every 2 seconds>
/Zephyr-latest/samples/shields/x_nucleo_iks02a1/standard/
DREADME.rst70 <updated endlessly every 2 seconds>
/Zephyr-latest/samples/bluetooth/pbp_public_broadcast_source/
DREADME.rst13 every 15 seconds.
/Zephyr-latest/doc/develop/test/
Dztest.rst25 * :c:type:`ztest_suite_before_t` - An optional before function which will run before every single
27 * :c:type:`ztest_suite_after_t` - An optional after function which will run after every single
154 Test rules are a way to run the same logic for every test and every suite. There are a lot of cases
155 where you might want to reset some state for every test in the binary (regardless of which suite is
399 The idea is that test reports show results for every test case
611 means every test suite is executed 3 times and every test case is executed 3 times. This can
/Zephyr-latest/kernel/
DKconfig.smp88 computation required at every scheduler operation by a value that is
123 will win the contention every time which will result
DKconfig.mem_domain23 embedded within every struct k_mem_domain. The architecture
/Zephyr-latest/boards/others/stm32f030_demo/doc/
Dindex.rst68 You will see the LED blinking every second.
/Zephyr-latest/tests/drivers/build_all/ethernet/
Dspi_devices.overlay34 /* one entry for every devices at spi.dtsi */
/Zephyr-latest/samples/bluetooth/bap_broadcast_source/
DREADME.rst15 The BAP Broadcast Source will reset every 30 seconds to show the full API.

12345678910>>...13