Home
last modified time | relevance | path

Searched refs:repeated (Results 1 – 25 of 30) sorted by relevance

12

/Zephyr-Core-3.7.0/samples/boards/stm32/uart/single_wire/
DREADME.rst30 but the following message repeated every 2s:
/Zephyr-Core-3.7.0/samples/sensor/ina219/
DREADME.rst35 you should get a similar output as below, repeated every 2 seconds:
/Zephyr-Core-3.7.0/samples/subsys/task_wdt/
DREADME.rst35 The following output is printed and continuously repeated (after each
/Zephyr-Core-3.7.0/drivers/entropy/
DKconfig.cc13xx_cc26xx35 int "Threshold for detected repeated patterns"
/Zephyr-Core-3.7.0/tests/subsys/zbus/unittests/src/
Dmain.c313 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-Core-3.7.0/drivers/i2c/
DKconfig.it8xxx211 This driver supports repeated start.
/Zephyr-Core-3.7.0/samples/drivers/adc/adc_dt/
DREADME.rst55 You should get a similar output as below, repeated every second:
/Zephyr-Core-3.7.0/samples/drivers/adc/adc_sequence/
DREADME.rst48 You should get a similar output as below, repeated every second:
/Zephyr-Core-3.7.0/cmake/modules/
DFindGnuLd.cmake28 # GNULD_LINKER exists on repeated builds or defined manually...
/Zephyr-Core-3.7.0/doc/services/ipc/ipc_service/backends/
Dipc_service_icmsg.rst75 has been written. Sending the signal to the other domain or CPU is repeated
/Zephyr-Core-3.7.0/subsys/ipc/ipc_service/lib/
DKconfig.icmsg30 notification is repeated.
/Zephyr-Core-3.7.0/tests/benchmarks/sys_kernel/
DREADME.txt15 Each test below is repeated 10 times;
/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/mesh/
Dblob.rst77 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
Dprovisioning.rst142 sequence should be repeated after a delay of three seconds or more.
/Zephyr-Core-3.7.0/scripts/ci/
Dpylintrc144 repeated-keyword,
/Zephyr-Core-3.7.0/doc/connectivity/usb/device_next/
Dusb_device.rst170 instances can be reused, but the previous steps must be repeated. So it is
/Zephyr-Core-3.7.0/doc/build/cmake/
Dindex.rst294 The link from the previous stage is repeated, this time with the missing
/Zephyr-Core-3.7.0/subsys/bluetooth/controller/
DKconfig.ll_sw_split944 would happen in the next connection event instead of repeated retries
1156 to avoid repeated skipping of overlapping events as next_has_priority
1159 incremented by 1. This repeated skip happens when all the time
/Zephyr-Core-3.7.0/boards/intel/adsp/doc/
Dintel_adsp_generic.rst324 cause of repeated failures, try restarting the scripts and / or power cycling
/Zephyr-Core-3.7.0/doc/build/kconfig/
Dsetting.rst287 definition location, it does not need to be repeated here. Only giving the
/Zephyr-Core-3.7.0/boards/native/doc/
Darch_soc.rst383 and raising an interrupt which wake the CPU again is repeated until the end
/Zephyr-Core-3.7.0/doc/develop/test/
Dztest.rst65 Test fixtures can be used to help simplify repeated test setup operations. In many cases, tests in
/Zephyr-Core-3.7.0/doc/security/
Dvulnerabilities.rst848 Assertion reachable with repeated LL_CONNECTION_PARAM_REQ.
869 BT: Assertion failure on repeated LL_FEATURE_REQ
/Zephyr-Core-3.7.0/subsys/bluetooth/mesh/
DKconfig1309 How many times Solicitation PDU advertisements will be repeated. 0 means that there will be
/Zephyr-Core-3.7.0/doc/releases/
Drelease-notes-3.3.rst2917 * :github:`54414` - stm32u5 dma driver does not support repeated start-stop
3112 * :github:`53103` - Zephyr shell on litex : number higher than 10 are printed as repeated hex
3592 * :github:`48018` - ztest: static threads are not re-launched for repeated test suite execution.

12