Home
last modified time | relevance | path

Searched full:rtt (Results 1 – 25 of 186) sorted by relevance

12345678

/Zephyr-latest/modules/segger/
DKconfig10 Indicates that the platform supports SEGGER J-Link RTT.
13 bool "SEGGER RTT libraries."
17 Enable Segger J-Link RTT libraries for platforms that support it.
18 Selection of this option enables use of RTT for various subsystems.
19 Note that by enabling this option, RTT buffers consume more RAM.
45 int "Size of buffer for RTT printf to bulk-send chars via RTT"
73 prompt "Choose RTT data linker section"
77 bool "Place RTT data in the default linker section"
80 bool "Place RTT data in the DTCM linker section"
83 bool "Place RTT data in the CCM linker section"
[all …]
/Zephyr-latest/dts/bindings/serial/
Dsegger,rtt-uart.yaml4 description: Segger RTT UART
6 compatible: "segger,rtt-uart"
15 Size of the RTT up buffer for transmission
16 Not used for RTT channel 0 as channel 0 is initialized at compile time,
23 Size of the RTT down buffer for reception
24 Not used for RTT channel 0 as channel 0 is initialized at compile time,
/Zephyr-latest/drivers/serial/
DKconfig.rtt1 # Virtual UART RTT driver option
7 bool "UART RTT driver"
14 This option enables access RTT channel as UART device.
25 …Enable UART on (default) RTT channel 0. Default channel has to be configured in non-blocking skip …
33 Enable UART on RTT channel 1
41 Enable UART on RTT channel 2
49 Enable UART on RTT channel 3
/Zephyr-latest/snippets/rtt-tracing/
DREADME.rst1 .. _snippet-rtt-tracing:
3 SystemView RTT Tracing Snippet (rtt-tracing)
8 west build -S rtt-tracing [...]
13 This snippet enables SEGGER SystemView RTT support with the tracing subsystem.
Dsnippet.yml4 name: rtt-tracing
6 EXTRA_CONF_FILE: rtt-tracing.conf
/Zephyr-latest/subsys/logging/backends/
DKconfig.rtt5 bool "Segger J-Link RTT backend"
11 When enabled, backend will use RTT for logging. This backend works on a per
44 backend = RTT
45 backend-str = rtt
70 RTT session is inactive.
76 Sleep period between TX retry attempts. During RTT session, host pulls
78 increased if traffic on RTT increases (also from host to device). In
100 # Same buffer is used by RTT console. If printk would go through RTT console
101 # that will lead to corruption of RTT data which is not protected against being
/Zephyr-latest/boards/nxp/common/
Dsegger-ecc-systemview.rst5 Using Segger SystemView and RTT
8 Note that when using SEGGER SystemView or RTT with this SOC, the RTT control
9 block address must be set manually within SystemView or the RTT Viewer. The
14 The RTT control block address must be provided manually because this SOC
/Zephyr-latest/snippets/rtt-console/
DREADME.rst1 .. _snippet-rtt-console:
3 RTT Console Snippet (rtt-console)
9 This snippet enables console output to SEGGER RTT.
Dsnippet.yml1 name: rtt-console
3 EXTRA_CONF_FILE: rtt-console.conf
/Zephyr-latest/tests/drivers/uart/uart_async_api/boards/
Dsegger_rtt.overlay9 compatible = "segger,rtt-uart";
14 compatible = "segger,rtt-uart";
19 compatible = "segger,rtt-uart";
24 compatible = "segger,rtt-uart";
/Zephyr-latest/samples/bluetooth/hci_uart_async/
Ddebug.mixin.conf7 # Enable RTT
9 # Enable RTT console
15 # This outputs all HCI traffic to a separate RTT channel. Use `btmon
/Zephyr-latest/doc/develop/flash_debug/
Dnordic_segger.rst18 * Segger RTT Console
153 RTT Console
156 Segger's J-Link supports `Real-Time Tracing (RTT)`_, a technology that allows a terminal
158 and the development computer for logging and input. Zephyr supports RTT on nRF5x targets,
161 To use RTT, you will first need to enable it by adding the following lines in your ``.conf`` file:
171 supports SEGGER J-Link RTT. This symbol is set automatically by the SoC
176 If you get no RTT output you might need to disable other consoles which conflict
177 with the RTT one if they are enabled by default in the particular sample or
185 Once compiled and flashed with RTT enabled, you will be able to display RTT console
191 * Open the "J-Link RTT Viewer" application
[all …]
/Zephyr-latest/subsys/tracing/sysview/
DKconfig10 int "Buffer size for SystemView RTT"
14 int "RTT channel for SystemView"
/Zephyr-latest/scripts/west_commands/
Ddebug.py79 class Rtt(WestCommand): class
82 super(Rtt, self).__init__(
83 'rtt',
85 'open an rtt shell',
/Zephyr-latest/scripts/west_commands/runners/
Dopenocd.py123 return RunnerCaps(commands={'flash', 'debug', 'debugserver', 'attach', 'rtt'}, rtt=True)
185 parser.add_argument('--rtt-port', default=DEFAULT_OPENOCD_RTT_PORT,
186 help='openocd rtt port, defaults to 5555')
216 self.logger.info(f'OpenOCD RTT server running on port {self.rtt_port}')
251 elif command in ('attach', 'debug', 'rtt'):
378 if command == 'rtt':
381 raise ValueError("RTT Control block not be found")
385 # start the internal openocd rtt service via gdb monitor commands
387 ['-ex', f'monitor rtt setup 0x{rtt_address:x} 0x10 "SEGGER RTT"'])
389 gdb_cmd.extend(['-ex', 'monitor rtt start'])
[all …]
Dpyocd.py79 return RunnerCaps(commands={'flash', 'debug', 'debugserver', 'attach', 'rtt'},
81 tool_opt=True, rtt=True)
143 if command == 'rtt':
144 self.rtt(**kwargs)
218 def rtt(self): member in PyOcdBinaryRunner
221 raise ValueError('RTT control block not found')
223 self.logger.debug(f'rtt address: 0x{rtt_addr:x}')
226 ['rtt'] +
/Zephyr-latest/samples/drivers/led/sx1509b_intensity/
DREADME.rst22 The log is configured to output to RTT. Segger J-Link RTT Viewer can be used to view the log.
/Zephyr-latest/include/zephyr/shell/
Dshell_rtt.h32 * @brief Function provides pointer to shell rtt backend instance.
34 * Function returns pointer to the shell rtt instance. This instance can be
/Zephyr-latest/scripts/
Dwest-commands.yml49 - name: rtt
50 class: Rtt
51 help: open an rtt shell
/Zephyr-latest/drivers/console/
DKconfig131 bool "Use RTT console"
146 RTT session is inactive.
152 Sleep period between TX retry attempts. During RTT session, host pulls data
154 if traffic on RTT increases (also from host to device). In case of
161 If enabled RTT console will busy wait between TX retries when console
162 assumes that RTT session is active. In case of heavy traffic data can
/Zephyr-latest/samples/sensor/accel_trig/
Dsample.yaml34 - SNIPPET=rtt-tracing;rtt-console
/Zephyr-latest/subsys/shell/backends/
DKconfig.backends187 bool "RTT backend"
192 # RTT backend can only be called from thread context.
195 Enable RTT backend.
201 default "rtt:~$ "
203 Displayed prompt name for RTT backend. If prompt is set, the shell will
219 RTT session is inactive.
225 Sleep period between TX retry attempts. During RTT session, host pulls
227 increased if traffic on RTT increases (also from host to device). In
235 Determines how often RTT is polled for RX byte.
278 module-str = RTT shell backend
/Zephyr-latest/samples/sensor/accel_polling/
Dsample.yaml40 - SNIPPET=rtt-tracing;rtt-console
/Zephyr-latest/boards/makerbase/mks_canable_v20/doc/
Dindex.rst115 :west-args: -S rtt-console
118 The argument ``-S rtt-console`` is needed for debug purposes with SEGGER RTT protocol.
119 This option is optional and may be omitted. Omitting it frees up RAM space but prevents RTT usage.
121 If option ``-S rtt-console`` is selected, the connection to the target can be established as follow…
135 Current OpenOCD config will skip Segger RTT for OpenOCD under 0.12.0.
/Zephyr-latest/boards/holyiot/yj16019/
Dholyiot_yj16019_defconfig9 # Enable RTT

12345678