Lines Matching refs:trace

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
188 For example, if you set a breakpoint in an error handler, a snapshot trace can show the sequence
221 To view the trace data, the easiest way is to start your debugger (west debug) and run the
224     dump binary value trace.bin *RecorderDataPtr
232 Tracealyzer has built-in support for SEGGER RTT to receive trace data using a J-Link probe.
307 with tracing and try out streaming trace without needing a fast debug probe. The data is streamed
329 By default, the resulting trace file is found in :file:`./trace.psf` in the root of the build folde…
350 output the trace data and (optionally) how to read start/stop commands from Tracealyzer.
352 Tracealyzer can receive trace streams over various interfaces, including files, sockets,
429 - generating/outputting trace data in a non-standard or proprietary format that can
480 You can then run the resulting binary with the option ``-trace-file`` to generate
485     ./build/zephyr/zephyr.exe -trace-file=data/channel0_0
488 by pointing the tool to the ``data`` directory with the metadata and trace files.
494 enough RAM to collect trace data, the ram backend can be enabled with configuration