Home
last modified time | relevance | path

Searched refs:timestamps (Results 1 – 15 of 15) sorted by relevance

/Zephyr-Core-3.5.0/samples/boards/nrf/nrf53_sync_rtc/
DREADME.rst18 that before synchronization procedure is completed, timestamps differ significantly
19 and once procedure is completed timestamps are synchronized. Network core timestamp
73 Observe that initially logging timestamps for the corresponding events on both cores
74 do not match. Same with local and remote timestamps reported on network core. After
/Zephyr-Core-3.5.0/soc/arm/nordic_nrf/nrf53/
Dsoc.c103 static uint32_t timestamps[5]; in nrf53_anomaly_160_check() local
106 uint8_t oldest = (current + 1) % ARRAY_SIZE(timestamps); in nrf53_anomaly_160_check()
111 (now - timestamps[oldest]) < (window_cycles + 1)) { in nrf53_anomaly_160_check()
132 timestamps[current] = k_cycle_get_32(); in nrf53_anomaly_160_check()
/Zephyr-Core-3.5.0/scripts/pylib/twister/twisterlib/
Dtwister_main.py27 def setup_logging(outdir, log_file, verbose, timestamps): argument
45 if timestamps:
106 setup_logging(options.outdir, options.log_file, VERBOSE, options.timestamps)
/Zephyr-Core-3.5.0/drivers/can/
DKconfig64 bool "Receiving timestamps"
68 is initialized. Not all CAN controllers support timestamps.
/Zephyr-Core-3.5.0/soc/
DKconfig63 timestamps and cycle count.
/Zephyr-Core-3.5.0/subsys/logging/
DKconfig.mode36 but not runtime filtering. There are no timestamps, prefixes,
DKconfig.formatting174 which timestamps are printed as fixed point values with seconds on the
/Zephyr-Core-3.5.0/boards/
DKconfig122 timestamps and cycle count.
/Zephyr-Core-3.5.0/subsys/bluetooth/
DKconfig.iso105 HCI ISO Data packet with a size of 255, without utilizing timestamps.
/Zephyr-Core-3.5.0/doc/kernel/
Dtimeutil.rst61 Sub-second timestamps like ``struct timespec`` can also use this to produce
218 between their timestamps.
/Zephyr-Core-3.5.0/samples/net/gptp/
DREADME.rst32 timestamps for sent and received Ethernet frames.
/Zephyr-Core-3.5.0/subsys/net/l2/ethernet/gptp/
DKconfig10 and handles network packet timestamps.
/Zephyr-Core-3.5.0/doc/services/logging/
Dindex.rst619 Logging does not provide any mechanism for synchronizing timestamps across multiple
625 recalculates timestamps, there are 2 options:
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-3.5.rst857 * Time and timestamps in the network subsystem, PTP and IEEE 802.15.4
859 Fields for timed TX and TX/RX timestamps have been consolidated. See
Drelease-notes-1.14.rst2178 * :github:`9043` - New logging subsystem's timestamps wrap a little before the 3-minute mark