Home
last modified time | relevance | path

Searched refs:minutes (Results 1 – 25 of 29) sorted by relevance

12

/Zephyr-Core-3.5.0/doc/services/storage/nvs/
Dnvs.rst79 first sector will be full after 1024/12 = 85.33 minutes. After another 85.33
80 minutes, the second sector is full. When this happens, because we're using
82 after 171 minutes of system time. With the expected device life of 20,000
83 writes, with two sectors writing every 171 minutes, the device should last
84 about 171 * 20,000 minutes, or about 6.5 years.
93 the expected device life (in minutes) can be calculated as::
95 SECTOR_COUNT * SECTOR_SIZE * PAGE_ERASES / (NS * (DS+8)) minutes
/Zephyr-Core-3.5.0/samples/boards/litex/i2s/
DREADME.rst34 It seems that after a few minutes some music delay occurs, this is because the sound driver is not …
/Zephyr-Core-3.5.0/tests/kernel/fpu_sharing/generic/
DCMakeLists.txt8 # output being in the range of every few seconds to every few minutes. To
DREADME.txt45 every few seconds to every few minutes. The speed of the test can be controlled
/Zephyr-Core-3.5.0/subsys/mgmt/hawkbit/
DKconfig28 int "Time to poll interval (in minutes)"
33 This time interval is zero and 43200 minutes(30 days).
/Zephyr-Core-3.5.0/subsys/shell/modules/
Dkernel_service.c59 int64_t minutes; in cmd_kernel_uptime() local
77 minutes = milliseconds / MINUTES_FACTOR; in cmd_kernel_uptime()
84 days, hours, minutes, seconds, milliseconds); in cmd_kernel_uptime()
/Zephyr-Core-3.5.0/doc/connectivity/networking/api/
Dnet_timeout.rst15 32-bit unsigned values. The 32-bit value rolls over at 49 days 17 hours 2 minutes
22 number (``INT32_MAX``), which overflows at 24 days 20 hours 31 minutes 23.648
/Zephyr-Core-3.5.0/tests/kernel/timer/starve/
DREADME.txt12 minutes, hours, or days to fail, depending on the hardware clock rate
/Zephyr-Core-3.5.0/subsys/mgmt/updatehub/
DKconfig30 int "Time to poll interval (in minutes)"
35 This time interval is zero and 43200 minutes(30 days).
/Zephyr-Core-3.5.0/samples/modules/tflite-micro/hello_world/train/
DREADME.md35 *Estimated Training Time: 10 minutes.*
/Zephyr-Core-3.5.0/samples/modules/tflite-micro/magic_wand/train/
Dtrain_magic_wand_model.ipynb60 …Change runtime type** and selecting **GPU**. Training will take around 5 minutes on a GPU runtime."
193 …lowing cell will begin the training process. Training will take around 5 minutes on a GPU runtime.…
/Zephyr-Core-3.5.0/include/zephyr/bluetooth/services/
Dots.h511 uint8_t minutes; member
/Zephyr-Core-3.5.0/doc/kernel/
Dtimeutil.rst50 * Calendar time as a year, month, day, hour, minutes, and seconds relative to
193 inaccurate, with drifts as much as three minutes per hour (assuming an RC
/Zephyr-Core-3.5.0/samples/subsys/mgmt/updatehub/
DREADME.rst151 preference, remembering that the limit is between 0 and 43200 minutes
152 (30 days). The default value is 1440 minutes (24h).
410 :kconfig:option:`CONFIG_UPDATEHUB_POLL_INTERVAL` minutes. The ``updatehub run`` can
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/
Dblob.rst19 BLOB to be transferred in 10-15 minutes. However, network conditions, transfer capabilities and
Dshell.rst758 * ``0x03``: The Step Resolution is 10 minutes
783 * ``0x03``: The Step Resolution is 10 minutes
/Zephyr-Core-3.5.0/doc/contribute/documentation/
Dgeneration.rst220 Depending on your development system, it will take up to 15 minutes to
/Zephyr-Core-3.5.0/subsys/net/ip/
DKconfig401 suggests to use MSL of 2 minutes, but notes "This is an
441 retransmit for up to 1:42 minutes. This is as close as possible
442 to the minimum value recommended by RFC1122 (1:40 minutes).
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-1.7.rst306 * ``ZEP-1421`` - BMI160 gyroscope driver stops reporting after 1-5 minutes
372 * ``ZEP-1581`` - [nRF52832] Blinky hangs after some minutes
Drelease-notes-1.8.rst316 * ``ZEP-2080`` - No reply from RPL node after 20-30 minutes.
/Zephyr-Core-3.5.0/doc/contribute/
Dcontributor_expectations.rst14 to set aside a few minutes to review smaller changes several times than it is
/Zephyr-Core-3.5.0/boards/posix/doc/
Darch_soc.rst184 - Run tests fast: several minutes of simulated time per wall time second.
/Zephyr-Core-3.5.0/boards/xtensa/intel_adsp_cavs25/doc/
Dchromebooks_adsp.rst40 about 15 minutes to completely write the stateful partition. On
/Zephyr-Core-3.5.0/subsys/bluetooth/services/ots/
Dots_client.c260 p_date_time->minutes = net_buf_simple_pull_u8(buf); in date_time_decode()
/Zephyr-Core-3.5.0/doc/security/
Dsensor-threat.rst94 requires the time to be accurate within 5-10 minutes.

12