Searched refs:repeated (Results 1 – 25 of 32) sorted by relevance
12
| /Zephyr-latest/samples/boards/st/uart/single_wire/ |
| D | README.rst | 34 but the following message repeated every 2s:
|
| /Zephyr-latest/samples/sensor/ina219/ |
| D | README.rst | 36 you should get a similar output as below, repeated every 2 seconds:
|
| /Zephyr-latest/samples/subsys/task_wdt/ |
| D | README.rst | 35 The following output is printed and continuously repeated (after each
|
| /Zephyr-latest/drivers/entropy/ |
| D | Kconfig.cc13xx_cc26xx | 35 int "Threshold for detected repeated patterns"
|
| /Zephyr-latest/tests/subsys/zbus/unittests/src/ |
| D | main.c | 313 struct action_msg repeated = {.status = false}; in ZTEST() local
315 zbus_chan_pub(&aux3_on_change_chan, &repeated, K_NO_WAIT); in ZTEST()
319 zbus_chan_pub(&aux3_on_change_chan, &repeated, K_NO_WAIT); in ZTEST()
323 zassert_equal(0, zbus_chan_pub(&go_busy_chan, &repeated, K_NO_WAIT), in ZTEST()
|
| /Zephyr-latest/drivers/i2c/ |
| D | Kconfig.it8xxx2 | 12 This driver supports repeated start.
|
| /Zephyr-latest/samples/drivers/adc/adc_dt/ |
| D | README.rst | 55 You should get a similar output as below, repeated every second:
|
| /Zephyr-latest/samples/drivers/adc/adc_sequence/ |
| D | README.rst | 48 You should get a similar output as below, repeated every second:
|
| /Zephyr-latest/cmake/modules/ |
| D | FindGnuLd.cmake | 28 # GNULD_LINKER exists on repeated builds or defined manually...
|
| /Zephyr-latest/tests/subsys/ipc/ipc_sessions/interoperability/ |
| D | Kconfig.icmsg_v1 | 30 notification is repeated.
|
| /Zephyr-latest/tests/benchmarks/sys_kernel/ |
| D | README.txt | 15 Each test below is repeated 10 times;
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob.rst | 77 resends them. This is repeated until all BLOB Transfer Servers have received all chunks, or the BLOB
164 is repeated until the BLOB Transfer Server has received all chunks in a block. Then, the BLOB
|
| D | provisioning.rst | 142 sequence should be repeated after a delay of three seconds or more.
|
| /Zephyr-latest/scripts/ci/ |
| D | pylintrc | 143 repeated-keyword,
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icmsg.rst | 85 has been written. Sending the signal to the other domain or CPU is repeated
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 147 instances can be reused, but the previous steps must be repeated. So it is
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 324 cause of repeated failures, try restarting the scripts and / or power cycling
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 280 definition location, it does not need to be repeated here. Only giving the
|
| /Zephyr-latest/doc/build/cmake/ |
| D | index.rst | 297 The link from the previous stage is repeated, this time with the missing
|
| /Zephyr-latest/doc/services/llext/ |
| D | debug.rst | 66 Steps 4-6 can be repeated for every extension that is loaded by the
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.ll_sw_split | 1072 would happen in the next connection event instead of repeated retries
1307 to avoid repeated skipping of overlapping events as next_has_priority
1310 incremented by 1. This repeated skip happens when all the time
|
| /Zephyr-latest/doc/develop/test/ |
| D | ztest.rst | 68 Test fixtures can be used to help simplify repeated test setup operations. In many cases, tests in
|
| /Zephyr-latest/doc/services/storage/zms/ |
| D | zms.rst | 30 This behavior is repeated until it reaches the end of the partition. Then it starts again from
|
| /Zephyr-latest/doc/security/ |
| D | vulnerabilities.rst | 774 Assertion reachable with repeated LL_CONNECTION_PARAM_REQ.
793 BT: Assertion failure on repeated LL_FEATURE_REQ
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 861 repeated in each image's ``CMakeLists.txt`` file.
|
12
