Home
last modified time | relevance | path

Searched full:trace (Results 1 – 25 of 190) sorted by relevance

12345678

/Zephyr-latest/include/zephyr/tracing/
Dtracing.h67 * @brief Trace creating a Thread
73 * @brief Trace Thread entering user mode
265 * @brief Trace implicit thread wakeup invocation by the scheduler
271 * @brief Trace implicit thread abort invocation by the scheduler
277 * @brief Trace implicit thread set priority invocation by the scheduler
284 * @brief Trace implicit thread ready invocation by the scheduler
290 * @brief Trace implicit thread pend invocation by the scheduler
296 * @brief Trace implicit thread resume invocation by the scheduler
302 * @brief Trace implicit thread suspend invocation by the scheduler
316 * @brief Trace initialisation of a Work structure
[all …]
Dtracing_syscall.h24 * @brief Trace syscall entry
32 * @brief Trace syscall exit
/Zephyr-latest/include/zephyr/debug/coresight/
Dcs_trace_defmt.h19 * @defgroup cs_trace_defmt Coresight Trace Deformatter
32 /** @brief Size of trace deformatter frame size in 32 bit words. */
35 /** @brief Size of trace deformatter frame size in bytes. */
38 /** @brief Initialize Coresight Trace Deformatter.
46 * Trace formatter puts data in the 16 byte long blocks.
/Zephyr-latest/doc/services/debugging/
Dcs_trace_defmt.rst3 ARM Coresight Trace Deformatter
6 Formatter is a method of wrapping multiple trace streams (specified by 7 bit ID) into a
8 data. It is used, for example, by ETR (Embedded Trace Router) which is a circular RAM
9 buffer where data from various trace streams can be saved. Typically tracing data is
Dmipi_stp_decoder.rst6 The MIPI System Trace Protocol (MIPI STP) was developed as a generic base protocol that can
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
14 One example where protocol is used is ARM Coresight STM (System Trace Macrocell) where data
/Zephyr-latest/include/zephyr/logging/
Dlog_frontend_stmesp.h44 /** @brief Trace point
46 * Write a trace point information using STM. Number of unique trace points is limited
49 * @param x Trace point ID.
65 /** @brief Trace point with 32 bit data.
67 * Write a trace point information using STM. Number of unique trace points is limited
70 * @param x Trace point ID.
/Zephyr-latest/tests/arch/common/stack_unwind/
Dtestcase.yaml18 - "E: call trace:"
30 - "E: call trace:"
44 - "E: call trace:"
57 - "E: call trace:"
/Zephyr-latest/doc/services/logging/
Dcs_stm.rst7 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
19 to STMESP register results in the user data being encoded into MIPI System Trace Protocol v2 (STPv2…
24 TPIU (Trace Port Interface Unit) or saved in the RAM Circular Buffer which is called ETR (Embedded
25 Trace Router). TPIU is a 5 pin interface (4 data pins and clock) and external tool is required to
26 capture the data (e.g. J-Trace PRO).
30 ARM Coresight Embedded Trace Router (ETR)
34 various sources additional wrapping protocol is used to multiplex them. ``Coresight Trace
44 buffer busyness is using own wrapper: Trace Buffer Monitor (TBM).
62 Trace points
[all …]
/Zephyr-latest/doc/services/tracing/
Dindex.rst13 Every system has application-specific events to trace out. Historically,
35 Named Trace Events
43 Users can generate a custom trace event by calling
53 Common Trace Format (CTF) Support
56 Common Trace Format, CTF, is an open format and language to describe trace
61 See `CTF - A Flexible, High-performance Binary Trace Format
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.
[all …]
/Zephyr-latest/samples/subsys/tracing/
DREADME.rst40 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/dts/bindings/arm/
Dnordic,nrf-tddconf.yaml5 Nordic TRACE and Debug Domain
7 Configuration for the Trace and Debug subsystem
/Zephyr-latest/subsys/profiling/perf/backends/
Dperf_x86_64.c24 * This function use frame pointers to unwind stack and get trace of return addresses.
26 * So we get function call trace
71 * and trace moves deeper into the stack in arch_perf_current_stack_trace()
Dperf_x86.c33 * This function use frame pointers to unwind stack and get trace of return addresses.
35 * So we get function call trace
85 * and trace moves deeper into the stack in arch_perf_current_stack_trace()
Dperf_riscv.c23 * This function use frame pointers to unwind stack and get trace of return addresses.
25 * So we get function call trace
97 * and trace moves deeper into the stack in arch_perf_current_stack_trace()
/Zephyr-latest/doc/_extensions/zephyr/
Dlink-roles.py77 trace = f"at '{source}:{line}'"
106 f"Role 'module_file' must take a module as an argument\n\t{trace}"
114 f"Configuration value `link_roles_manifest_baseurl` not set\n\t{trace}"
124 f"{link} not found in {config.link_roles_manifest_project} {trace}"
/Zephyr-latest/drivers/spi/
DKconfig.ambiq61 bool "Ambiq SPI-BLEIF timing trace"
67 trace purpose.
/Zephyr-latest/doc/services/profiling/
Dperf.rst15 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/drivers/sensor/st/vl53l1x/
Dvl53l1_platform_log.h37 * @param modules - Module or None or All to trace
46 * @param level - trace level
55 * @param functions - function level to trace;
117 * @brief Print trace module function.
/Zephyr-latest/tests/subsys/debug/cs_trace_defmt/
DREADME1 Test for decoder of frames encoded using Coresight Trace Formatter.
/Zephyr-latest/boards/segger/trb_stm32f407/doc/
Dindex.rst6 The Cortex-M Trace Reference Board V1.2 (SEGGER-TRB-STM32F407 for short)
8 ARM Cortex-M4 CPU, to test hardware tracing with the SEGGER Trace-Pro
95 Trace-Pro debuggers, so this example assumes a J-Trace or J-Link is used.
100 Connect the J-Trace/J-Link USB dongle to your host computer and to the JTAG
124 https://www.segger.com/products/debug-probes/j-trace/accessories/trace-reference-boards/overview/
/Zephyr-latest/boards/segger/trb_stm32f407/
Dboard.yml3 full_name: Cortex-M Trace Reference Board V1.2
/Zephyr-latest/dts/bindings/debug/
Darm,stmesp.yaml4 # Common fields for ARM instrumentation System Trace Macrocell Extended Stimulus Port (STMESP)
Darm,armv7m-itm.yaml5 ARMv7 instrumentation trace macrocell. Used for single wire output (SWO)
Darm,armv8m-itm.yaml5 ARMv8 instrumentation trace macrocell. Used for single wire output (SWO)
/Zephyr-latest/scripts/tracing/
Dparse_ctf.py10 Generate trace using samples/subsys/tracing for example:
35 parser.add_argument("-t", "--trace",
37 help="tracing data (directory with metadata and trace file)")
46 msg_it = bt2.TraceCollectionMessageIterator(args.trace)

12345678