Lines Matching +full:very +full:- +full:high +full:- +full:speed

3 Multi-domain logging using ARM Coresight STM
6 The Arm CoreSight SoC-400 is a comprehensive library of components for the creation of debug and
8 is integrated into a CoreSight system, designed primarily for high-bandwidth trace of
9 instrumentation embedded into software. This instrumentation is made up of memory-mapped writes to
26 capture the data (e.g. J-Trace PRO).
40 Data from ETR is handled on the device. It can be forwarded as-is to the host (e.g. using UART),
41 where a host tool is decoding the data or data can be decoded on-chip to output the data in human r…
65 There may be cases when logging is too slow (even though it is very fast). For cases like that a de…
68 * :c:func:`log_frontend_stmesp_tp` - It accepts single argument - index. Index is between
70 * :c:func:`log_frontend_stmesp_tp_d32` - It accepts two arguments - index and user data.
80 * Dictionary-based - assisted mode which is using dictionary-based logging. In this mode logging
82   is performed by the host tool. This mode takes less memory and is faster (2-3 times faster).
84 * Standalone - data is decoded on chip and human-readable strings are printed. This mode requires
87 Following figure presents multi-domain logging using ARM Coresight STM.
97 If dictionary-based logging is used then proxy just sends data as-is over UART.
102 Dictionary-based logging
105 Assisted multicore logging uses dictionary-based logging to send messages without redundant strings
111 The host PC, equipped with a decoder tool, translates these addresses back into human-readable text
116 …sages are not stored in the binary itself. Logging infrastructure is also very limited. On local d…
125 -------------
127 For Nordic SoC a dedicated snippet (:ref:`nordic-log-stm-dict`) shall be used to enable logging.
132 ----------------
134 To read the dictionary-based STM log output, do the following:
140 …--database-config 34:build/zephyr/log_dictionary.json,35:build_rad/zephyr/log_dictionary.json --in…
144 …ART port and use the provided dictionary databases to decode the logs into a human-readable format.
149    The file will contain timestamps and the log messages in a format that is human-readable.
156 Each log line contains a domain-related or core-related prefix between the log level and the module…
159 .. csv-table:: nRF54H20 log prefixes
170 Stand-alone logging
177 decode data and send human-readable data over UART. Nordic specific driver for ETR buffer is
179 :ref:`mipi_stp_decoder` and above-mentioned demultiplexer to decode messages.
181 Logging messages contains read-only format string used in the logging macros thus they cannot be
182 removed from the binary. This mode uses more read-only memory and has lower throughput because
183 messages are longer and processing is time consuming. Compared to the dictionary-based mode logging
184 is 2-3 slower.
187 -------------
189 For Nordic SoC a dedicated snippet (:ref:`nordic-log-stm`) shall be used to enable logging.
194 ----------------
200    For more details, see :ref:`devicetree-intro`.
220 Each log line contains a domain-related or core-related prefix between the log level and the module…
223 .. csv-table:: nRF54H20 log prefixes
238 …ic arguments, like ``LOG_INF("%d %c", (int)x, (char)y)``) to improve the size and speed of logging.