Searched full:etr (Results 1 – 13 of 13) sorted by relevance
| /Zephyr-latest/drivers/misc/coresight/ |
| D | Kconfig | 7 bool "Coresight ETR handler (with Nordic TBM)"
13 Module handles data stored in the ETR circular buffer (e.g. STM logging
20 bool "Decode ETR content"
48 int "ETR thread stack size"
62 When thread triggers flushing of ETR data, it periodically checks if
63 there is still a pending ETR data. This option specifies how often
72 To help find the synchronization when decoding the ETR content
|
| D | nrf_etr.c | 37 /* Since ETR debug is a part of logging infrastructure, logging cannot be used
454 * It is a non-wrapping 32 bit write index. To get actual index in the ETR buffer
455 * result must be masked by ETR buffer size mask.
473 /** @brief Get amount of pending data in ETR buffer. */
481 * Read index is not exact index in the ETR buffer. It does not wrap (32 bit word).
482 * So ETR read index is derived by masking the value by the ETR buffer size mask.
543 /** @brief Attempt to process data pending in the ETR circular buffer.
|
| /Zephyr-latest/doc/services/logging/ |
| D | cs_stm.rst | 24 TPIU (Trace Port Interface Unit) or saved in the RAM Circular Buffer which is called ETR (Embedded
27 When ETR is used then one core in the system is responsible for processing that data, for example
30 ARM Coresight Embedded Trace Router (ETR)
33 ETR is a circular RAM buffer to which tracing data is saved. Since it may contain data from
40 Data from ETR is handled on the device. It can be forwarded as-is to the host (e.g. using UART),
43 Nordic Semiconductor NRF54H20 implementation instead of using ETR peripheral for getting
56 STMESP cannot be used before STM or ETR/TPIU is setup. In order to support early logging,
83 There is less data written so there is less chance of data overflow in ETR buffer.
96 If ETR RAM buffer is used then buffer owner core (``proxy``) is responsible for handling that data.
110 If the data goes to the ETR buffer, the proxy core's responsibility is to dump this data.
[all …]
|
| /Zephyr-latest/snippets/nordic-log-stm/ |
| D | README.rst | 10 stimulus ports. Data is collected in ETR buffer. Data from ETR buffer is
|
| /Zephyr-latest/subsys/logging/frontends/ |
| D | Kconfig | 57 that any buffered data goes to TPIU/ETR.
63 Frontend cannot write to STM if it is used with ETR buffer unless ETR is
96 performed (e.g. ETR buffer is full).
|
| D | log_frontend_stmesp.c | 44 /* Buffer for storing frontend data before STM/ETR is ready for usage.
45 * When notification about ETR readiness is received content of this buffer is
54 /* Flag indicating that STM/ETR is ready for use. */
|
| /Zephyr-latest/snippets/nordic-log-stm-dict/ |
| D | README.rst | 10 the Coresight STM stimulus ports. Data is collected in ETR buffer. Data from ETR
|
| /Zephyr-latest/dts/bindings/arm/ |
| D | nordic,nrf-tddconf.yaml | 29 Bitmask of enabled sources for the ETR sink. Valid values can be found in
43 description: phandle to the memory region used for the ETR buffer
|
| /Zephyr-latest/samples/boards/nordic/coresight_stm/ |
| D | README.rst | 23 Application, Radio, PPR and FLPR cores send logs to an ETR buffer.
24 Proxy (Application core) gets logs from the ETR buffer, decodes STPv2 data
30 Application, Radio, PPR and FLPR cores send logs to the ETR buffer.
31 Proxy (Application core) forwards data from the ETR to the host using UART.
|
| /Zephyr-latest/include/zephyr/drivers/misc/coresight/ |
| D | nrf_etr.h | 13 /** @brief Flush data from the ETR buffer. */
|
| /Zephyr-latest/doc/services/debugging/ |
| D | cs_trace_defmt.rst | 8 data. It is used, for example, by ETR (Embedded Trace Router) which is a circular RAM
|
| /Zephyr-latest/include/zephyr/logging/ |
| D | log_frontend_stmesp.h | 19 /** @brief Notify frontend that ETR/STM is ready.
24 * @note Function is applicable only for the domain that performs initial ETR/STM setup.
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 433 Trace Formatter, e.g. when data is put into ETR (Embedded Trace Router).
|
