| /Zephyr-latest/doc/services/debugging/ |
| D | cs_trace_defmt.rst | 6 Formatter is a method of wrapping multiple trace streams (specified by 7 bit ID) into a
9 buffer where data from various trace streams can be saved. Typically tracing data is
|
| D | mipi_stp_decoder.rst | 7 be shared by multiple application-specific trace protocols. It serves as a wrapper protocol
8 that merges disparate streams that typically contain different trace protocols from different
9 trace sources. Stream consists of opcode (shortest is 4 bit long) followed by optional data and
|
| D | symtab.rst | 10 Currently, this is being used to look up the function names during a stack trace in supported archi…
|
| /Zephyr-latest/samples/subsys/tracing/ |
| D | README.rst | 40 After the application has run for a while, check the trace output file.
101 After the application has run for a while, check the trace output file.
115 After the application has run for a while, check the trace output file.
129 After the application has run for a while, check the trace output file.
143 After the application has run for a while, check the trace output file.
|
| /Zephyr-latest/doc/services/profiling/ |
| D | perf.rst | 15 structure before calling the interrupt handler. Thus, the perf trace function makes stack traces by
19 in the stack trace to function names using symbols from the ELF file, and to prints them in the
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.adsp | 9 Enable backend for the host trace protocol of the Intel ADSP
|
| /Zephyr-latest/subsys/profiling/perf/ |
| D | Kconfig | 19 Size of buffer used by perf to save stack trace samples.
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 13 Every system has application-specific events to trace out. Historically,
43 Users can generate a custom trace event by calling
56 Common Trace Format, CTF, is an open format and language to describe trace
117 Zephyr includes support for `Percepio Tracealyzer`_ that offers trace visualization for
118 simplified analysis, report generation and other analysis features. Tracealyzer allows for trace
154 is to select the right "stream port". This specifies how to output the trace data.
157 * **Ring Buffer**: The trace data is kept in a circular RAM buffer.
160 * **Semihost**: For tracing on QEMU. Streams the trace data to a host file.
183 The "Ring Buffer" stream port keeps the trace data in a RAM buffer on the device.
185 This is used to dump "snapshots" of the trace data, e.g. by using the debugger. This usually only
[all …]
|
| /Zephyr-latest/drivers/spi/ |
| D | Kconfig.ambiq | 61 bool "Ambiq SPI-BLEIF timing trace"
67 trace purpose.
|
| /Zephyr-latest/tests/ztest/error_hook/ |
| D | README.txt | 117 E: call trace:
131 E: call trace:
143 E: call trace:
154 E: call trace:
165 E: call trace:
185 E: call trace:
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig.kw41z | 25 trace of events without going to debug logging to avoid timing impact
|
| /Zephyr-latest/tests/drivers/regulator/voltage/boards/ |
| D | rpi_pico.overlay | 9 * DVDD are directly connected, and no available exposed trace on the board.
|
| /Zephyr-latest/boards/segger/trb_stm32f407/doc/ |
| D | index.rst | 124 https://www.segger.com/products/debug-probes/j-trace/accessories/trace-reference-boards/overview/
|
| /Zephyr-latest/modules/canopennode/ |
| D | Kconfig | 30 int "CANopen trace buffer size"
33 Size of the CANopen trace buffer in bytes.
|
| /Zephyr-latest/scripts/tracing/ |
| D | parse_ctf.py | 46 msg_it = bt2.TraceCollectionMessageIterator(args.trace)
|
| /Zephyr-latest/doc/_extensions/zephyr/ |
| D | link-roles.py | 77 trace = f"at '{source}:{line}'"
|
| /Zephyr-latest/doc/services/logging/ |
| D | cs_stm.rst | 7 trace functionality within a system. The STM (System Trace Macrocell) is a trace source that
8 is integrated into a CoreSight system, designed primarily for high-bandwidth trace of
65 …too slow (even though it is very fast). For cases like that a dedicated ``trace point`` API is add…
73 It takes less than 100 ns to log a single trace point on NRF54H20 and it is approx. 7 times faster …
138 …Use the ``nrfutil trace stm`` command to start capturing logs from the device, specifying the data…
140 …nrfutil trace stm --database-config 34:build/zephyr/log_dictionary.json,35:build_rad/zephyr/log_di…
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 22 main interface to trace implementation back to documented features. This is done
48 and trace back to them from requirements.
|
| /Zephyr-latest/soc/microchip/mec/mec172x/ |
| D | Kconfig | 48 prompt "MEC172X debug interface trace configuration"
|
| /Zephyr-latest/scripts/pylib/twister/twisterlib/ |
| D | harness.py | 71 def trace(self) -> bool: member in Harness
764 if self.trace:
775 if self.trace:
793 elif self.trace:
808 elif self.trace:
833 elif self.trace:
|
| /Zephyr-latest/soc/microchip/mec/mec15xx/ |
| D | Kconfig | 73 prompt "MEC1501 debug interface trace configuration"
|
| /Zephyr-latest/boards/toradex/verdin_imx8mp/doc/ |
| D | index.rst | 38 cores support both real-time trace through the ETM system and static debugging via JTAG.
39 Furthermore, the platform features support for real-time trace capabilities, achieved through ARM's
50 components including ETM and CTI, dedicated to facilitating debug and trace functions.
|
| /Zephyr-latest/subsys/logging/frontends/ |
| D | Kconfig | 145 Do not change this value as it is aligned with host decoder (nrfutil trace).
|
| /Zephyr-latest/samples/boards/nordic/coresight_stm/ |
| D | README.rst | 39 **sample.boards.nrf.coresight_stm.dict** requires host tool like ``nrfutil trace``
|
| /Zephyr-latest/boards/96boards/avenger96/doc/ |
| D | index.rst | 138 - Arm® CoreSight™ trace and debug: SWD and JTAG interfaces
139 - 8-Kbyte embedded trace buffer
|
