Home
last modified time | relevance | path

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

12

/Zephyr-latest/subsys/shell/modules/kernel_service/
Duptime.c21 int64_t minutes; in cmd_kernel_uptime() local
39 minutes = milliseconds / MINUTES_FACTOR; in cmd_kernel_uptime()
46 days, hours, minutes, seconds, milliseconds); in cmd_kernel_uptime()
/Zephyr-latest/doc/services/storage/nvs/
Dnvs.rst90 first sector will be full after 1024/12 = 85.33 minutes. After another 85.33
91 minutes, the second sector is full. When this happens, because we're using
93 after 171 minutes of system time. With the expected device life of 20,000
94 writes, with two sectors writing every 171 minutes, the device should last
95 about 171 * 20,000 minutes, or about 6.5 years.
104 the expected device life (in minutes) can be calculated as::
106 SECTOR_COUNT * SECTOR_SIZE * PAGE_ERASES / (NS * (DS+8)) minutes
/Zephyr-latest/samples/boards/enjoydigital/litex/i2s/
DREADME.rst36 It seems that after a few minutes some music delay occurs, this is because the sound driver is not …
/Zephyr-latest/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-latest/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-latest/tests/kernel/timer/starve/
DREADME.txt12 minutes, hours, or days to fail, depending on the hardware clock rate
/Zephyr-latest/subsys/mgmt/updatehub/
DKconfig31 int "Time to poll interval (in minutes)"
36 This time interval is zero and 43200 minutes(30 days).
/Zephyr-latest/subsys/mgmt/hawkbit/
DKconfig30 int "Time to poll interval (in minutes)"
35 This time interval is zero and 43200 minutes(30 days). This will be overridden
/Zephyr-latest/samples/modules/tflite-micro/hello_world/train/
DREADME.md35 *Estimated Training Time: 10 minutes.*
/Zephyr-latest/subsys/net/ip/
DKconfig.ipv6264 int "Max lifetime for temporary address (in minutes)"
268 value. The value is in minutes. Default value is 1 day (24*60).
271 int "Max preferred lifetime for temporary address (in minutes)"
275 value. The value is in minutes. Default value is 23 hours (23*60).
DKconfig.tcp58 suggests to use MSL of 2 minutes, but notes "This is an
100 retransmit for up to 1:42 minutes. This is as close as possible
101 to the minimum value recommended by RFC1122 (1:40 minutes).
/Zephyr-latest/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-latest/doc/connectivity/networking/
Dnet_config_guide.rst162 suggests to use MSL of 2 minutes, but notes
185 retransmit for up to 1:42 minutes. This is as close as possible
187 `RFC 1122 <https://www.rfc-editor.org/rfc/rfc1122>`_ (1:40 minutes).
/Zephyr-latest/include/zephyr/bluetooth/services/
Dots.h511 uint8_t minutes; member
/Zephyr-latest/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).
374 :kconfig:option:`CONFIG_UPDATEHUB_POLL_INTERVAL` minutes. The ``updatehub run`` can
/Zephyr-latest/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-latest/doc/services/storage/zms/
Dzms.rst320 :math:`\frac{(944 \times 4)}{16} = 236 \text{ minutes}`.
327 4.720.000 minutes (~9 years).
337 The expected life of the device in minutes is computed as :
/Zephyr-latest/doc/contribute/documentation/
Dgeneration.rst220 Depending on your development system, it will take up to 15 minutes to
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dblob.rst19 BLOB to be transferred in 10-15 minutes. However, network conditions, transfer capabilities and
/Zephyr-latest/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-latest/doc/contribute/
Dcontributor_expectations.rst11 to set aside a few minutes to review smaller changes several times than it is
/Zephyr-latest/boards/intel/adsp/doc/
Dchromebooks_adsp.rst38 about 15 minutes to completely write the stateful partition. On
/Zephyr-latest/subsys/bluetooth/services/ots/
Dots_client.c261 p_date_time->minutes = net_buf_simple_pull_u8(buf); in date_time_decode()

12