Nrf log rtt

J-Link RTT Viewer is the main GUI application to use all features of RTT on the debugging host (Windows, macOS and Linux). RTT Viewer can be used stand-alone, opening an own connection to J-Link and target or in parallel to a running debug session, attaching to it and using this existing J-Link connection. An easy fix for this is to switch the NRF_LOG driver to RTT, which can send data over the JLINK programmers you will be getting next week. This can be done by setting NRF_LOG_BACKEND_RTT_ENABLED to 1 in your config, and by using an RTT client. Segger Embedded Studio automatigically displays those logs in the console.SEGGER's Real Time Transfer (RTT) is the proven technology for system monitoring and interactive user I/O in embedded applications. It combines the advantages of SWO and semihosting at very high performance. Bi-directional communication with the target application. Very high transfer speed without affecting real time behavior. Now to see log messages printed on RTT Viewer, open two terminals. On the first terminal, type this command and hit Enter JLinkExe -if SWD -device nrf52 -speed 4000 -autoconnect 1 On the second terminal, type this command and hit Enter JLinkRTTClient You will see the same log messages above appear on the terminal. Format log messages in NRF_LOGJun 19, 2022 · Добавил(а) microsin В SDK 12.0.0 или более новой версии встроена функция вывода отладочных сообщений в терминал реального времени (logging/debugging over Real Time Terminal, сокращенно RTT) соответствующий код находится в logger module NRF_LOG. SEGGER's Real Time Transfer (RTT) is the proven technology for system monitoring and interactive user I/O in embedded applications. It combines the advantages of SWO and semihosting at very high performance. Bi-directional communication with the target application. Very high transfer speed without affecting real time behavior. Jun 19, 2022 · Добавил(а) microsin В SDK 12.0.0 или более новой версии встроена функция вывода отладочных сообщений в терминал реального времени (logging/debugging over Real Time Terminal, сокращенно RTT) соответствующий код находится в logger module NRF_LOG. Debugging with Real Time Terminal FormerMember 8 Apr 2015 In SDK 12.0.0 or later, logging/debugging over RTT is built in to the logger module NRF_LOG. To enable logging over RTT, "check" the NRF_LOG_BACKEND_SERIAL_USES_RTT option in sdk_config.h in the configuration wizard. This tutorial is therefore mostly relevant for SDK 11 or older.The output from NRF_LOG_xxx can be displayed in a terminal (if logging over UART) or in the J-link RTT viewer (logging over RTT). The sdk_config.h file --> configuration wizard can be used to choose logging over UART or RTT. As you can see in nrf_log_backend_serial.c, logging over RTT uses SEGGER_RTT_xxx functions. Open J-Link RTT Viewer and connect to the board: LOG: Device "NRF52840_XXAA" selected. LOG: Found SW-DP with ID 0x2BA01477 LOG: Found SW-DP with ID 0x2BA01477 LOG: Scanning AP map to find all available APs LOG: AP [2]: Stopped AP scan as end of AP map has been reached LOG: AP [0]: AHB-AP (IDR: 0x24770011) LOG: AP [1]: JTAG-AP (IDR: 0x02880000) Both NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED are set to 1 in sdk_config.h. Perhaps I am using the wrong address or control block ID? My knowledge about RTT is admittedly quite limited. For reference, I am using a nrf52833. The text was updated successfully, but these errors were encountered:To enable logging over RTT, define NRF_LOG_USES_RTT=1 in the project. To enable logging over UART, define NRF_LOG_USES_UART=1. To enable logging over raw UART, define NRF_LOG_USES_RAW_UART=1. You can specify only one of these defines, not several at the same time. To disable logging, do not specify either one. Available protocolsNow to see log messages printed on RTT Viewer, open two terminals. On the first terminal, type this command and hit Enter JLinkExe -if SWD -device nrf52 -speed 4000 -autoconnect 1 On the second terminal, type this command and hit Enter JLinkRTTClient You will see the same log messages above appear on the terminal. Format log messages in NRF_LOGMenu path: (Top) → Sub Systems and OS Services → Logging. config LOG_BACKEND_RTT bool "Enable Segger J-Link RTT backend" default y if ! SHELL_BACKEND_RTT depends on USE_SEGGER_RTT && ! LOG_MINIMAL && LOG help When enabled, backend will use RTT for logging. This backend works on a per message basis. Only a whole message (terminated with a ...1> Compiling 'nrf_log_backend_serial.c' 2> Compiling 'nrf_log_backend_rtt.c' 3> Compiling 'nrf_log_backend_uart.c' 4> Compiling 'nrf_log_default_backends.c' 1> cc1: fatal error: C:\Nordic\components\libraries\experimental_log\src\nrf_log_backend_serial.c: No such file or directory 1> compilation terminated.2) Can I use the RTT viewer while debugging the code since RTT doesn't use SWO? Sometimes, the RTT viewer does not display log messages when I'm debugging. Sadly, I cannot find the condition while debugging with the RTT viewer turned on. 3) When debugging the project with SEGGER's Ozone, the terminal shows the RTT messages without the color ...This is an NRF_CONFIG macro. #define NRF_LOG_BACKEND_RTT_TX_RETRY_CNT Writing to RTT retries. If RTT fails to accept any new data after retries module assumes that host is not active and on next request it will perform only one write attempt. On successful writing, module assumes that host is active and scheme with retry is applied again. Note#define NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE Size of buffer for partially processed strings. Size of the buffer is a trade-off between RAM usage and processing. if buffer is smaller then strings will often be fragmented. It is recommended to use size which will fit typical log and only the longer one will be fragmented. Note If RTT is used, then a breakpoint is hit once flushed. #define NRF_LOG_FLUSH ( ) NRF_LOG_INTERNAL_FLUSH () Macro for processing all log entries from the buffer. It blocks until all buffered entries are processed by the backend. Note If logs are not deferred, this call has no use and is empty. #define NRF_LOG_INIT ( timestamp_func )1> Compiling 'nrf_log_backend_serial.c' 2> Compiling 'nrf_log_backend_rtt.c' 3> Compiling 'nrf_log_backend_uart.c' 4> Compiling 'nrf_log_default_backends.c' 1> cc1: fatal error: C:\Nordic\components\libraries\experimental_log\src\nrf_log_backend_serial.c: No such file or directory 1> compilation terminated.对于SEGGER RTT这个工具的确是个好东西(基本上只要是能用Jlink的芯片就能使用这个功能),但是许多时候还是在使用串口进行log输出,而对于nRF52832以及nRF52840这些芯片的串口非常稀缺的资源,所以使用SEGGER RTT作为调试接口是再好不过的,但是Nordic的sdk本身就有log ...3.2 配置RTT打印 nRF_Log 中勾选 RTT 选项 切换回 Text Editor 界面,可以发现已经把 NRF_LOG_BACKEND_RTT_ENABLE 设置为 1,也就是使能了 RTT。 在 nrf_log_default_backends.c 文件中,当我们使能了 NRF_LOG_BACKEND_RTT_ENABLE 后,对应会修改文件中对 RTT 初始化 四、开始打印日志 4.1 串口打印 打开串口调试助手,波特率设置为 115200 4.2 RTT打印 找到你的 SEGGER 的安装位置,找到驱动版本下的 JLinkRTTViewer.exe 打开后弹出选择界面。// <o> NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE - Size of buffer for partially processed strings. // <i> Size of the buffer is a trade-off between RAM usage and processing. // <i> if buffer is smaller then strings will often be fragmented. // <i> It is recommended to use size which will fit typical log and only the // <i> longer one will be fragmented.Debugging with Real Time Terminal FormerMember 8 Apr 2015 In SDK 12.0.0 or later, logging/debugging over RTT is built in to the logger module NRF_LOG. To enable logging over RTT, "check" the NRF_LOG_BACKEND_SERIAL_USES_RTT option in sdk_config.h in the configuration wizard. This tutorial is therefore mostly relevant for SDK 11 or older.2) Can I use the RTT viewer while debugging the code since RTT doesn't use SWO? Sometimes, the RTT viewer does not display log messages when I'm debugging. Sadly, I cannot find the condition while debugging with the RTT viewer turned on. 3) When debugging the project with SEGGER's Ozone, the terminal shows the RTT messages without the color ...Menu path: (Top) → Sub Systems and OS Services → Logging. config LOG_BACKEND_RTT bool "Enable Segger J-Link RTT backend" default y if ! SHELL_BACKEND_RTT depends on USE_SEGGER_RTT && ! LOG_MINIMAL && LOG help When enabled, backend will use RTT for logging. This backend works on a per message basis. Only a whole message (terminated with a ...This is an NRF_CONFIG macro. #define NRF_LOG_BACKEND_RTT_TX_RETRY_CNT Writing to RTT retries. If RTT fails to accept any new data after retries module assumes that host is not active and on next request it will perform only one write attempt. On successful writing, module assumes that host is active and scheme with retry is applied again. NoteThe NRF_LOG_DEFAULT_BACKENDS_INIT () macro can be used to initialize and attach RTT or UART backend. The following code snippet shows how NRF_LOG_PROCESS can be incorporated into the non-preemptive scheduler. #include "nrf_log_ctrl.h" #include "nrf_log_default_backends.h" int main ( void) { err_code = NRF_LOG_INIT (timestamp_func);본 동영상 포함된 블로그 글 : http://igotit.tistory.com/2328 제목 : 문제해결. nRF5 SDK. NRF_LOG_INFO not shown in SES Debug Terminal.in this case ...NRF_LOG_GETCHAR () - A blocking macro that returns the received byte. Applicable when RTT or UART are used for logging but you need this communication channel for loading data from the host, as in some of the examples. A module can have a section that overrides default logger settings for the given module.#define NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE Size of buffer for partially processed strings. Size of the buffer is a trade-off between RAM usage and processing. if buffer is smaller then strings will often be fragmented. It is recommended to use size which will fit typical log and only the longer one will be fragmented. Note My sdk_config.h has the following settings: #define NRF_LOG_BACKEND_RTT_ENABLED 1. #define NRF_LOG_BACKEND_UART_ENABLED 1. With the above settings applied to enable UART, I can always see debug output just fine using a separate terminal program to monitor the serial port on my MAC.And if I separately run JLinkExe -if SWD / JLinkRTTClientExe on ...본 동영상 포함된 블로그 글 : http://igotit.tistory.com/2328 제목 : 문제해결. nRF5 SDK. NRF_LOG_INFO not shown in SES Debug Terminal.in this case ...// <o> NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE - Size of buffer for partially processed strings. // <i> Size of the buffer is a trade-off between RAM usage and processing. // <i> if buffer is smaller then strings will often be fragmented. // <i> It is recommended to use size which will fit typical log and only the // <i> longer one will be fragmented.With ES V4.16 (MAC) will the Log not Work on my NRF52832DK2 But with V4.12 it works. Dear Segger team, can you fix this? This thing is also an hot theme in the Nordic ForumBoth NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED are set to 1 in sdk_config.h. Perhaps I am using the wrong address or control block ID? My knowledge about RTT is admittedly quite limited. For reference, I am using a nrf52833. The text was updated successfully, but these errors were encountered:My sdk_config.h has the following settings: #define NRF_LOG_BACKEND_RTT_ENABLED 1. #define NRF_LOG_BACKEND_UART_ENABLED 1. With the above settings applied to enable UART, I can always see debug output just fine using a separate terminal program to monitor the serial port on my MAC.And if I separately run JLinkExe -if SWD / JLinkRTTClientExe on ...This is an NRF_CONFIG macro. #define NRF_LOG_BACKEND_RTT_TX_RETRY_CNT Writing to RTT retries. If RTT fails to accept any new data after retries module assumes that host is not active and on next request it will perform only one write attempt. On successful writing, module assumes that host is active and scheme with retry is applied again. NoteThis file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Building an app that is a BLE heart rate client, but also needs to use the chip's UART for controlling an external speech module (only 9600 baud needed, no flow control). I assume this means I can't use the Segger "virtual COM port interface" for the nRF_LOG messages while debugging, and need to use RTT instead.1> Compiling 'nrf_log_backend_serial.c' 2> Compiling 'nrf_log_backend_rtt.c' 3> Compiling 'nrf_log_backend_uart.c' 4> Compiling 'nrf_log_default_backends.c' 1> cc1: fatal error: C:\Nordic\components\libraries\experimental_log\src\nrf_log_backend_serial.c: No such file or directory 1> compilation terminated.Open J-Link RTT Viewer and connect to the board: LOG: Device "NRF52840_XXAA" selected. LOG: Found SW-DP with ID 0x2BA01477 LOG: Found SW-DP with ID 0x2BA01477 LOG: Scanning AP map to find all available APs LOG: AP [2]: Stopped AP scan as end of AP map has been reached LOG: AP [0]: AHB-AP (IDR: 0x24770011) LOG: AP [1]: JTAG-AP (IDR: 0x02880000)#define NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE Size of buffer for partially processed strings. Size of the buffer is a trade-off between RAM usage and processing. if buffer is smaller then strings will often be fragmented. It is recommended to use size which will fit typical log and only the longer one will be fragmented. Note For rather long log files I want to archive the text from RTT Viewer into a file. But I see no possibility to keep the color information with my text file. Neither the clipboard nor the file written with the "Terminal Logging" contains any color information. Screen shots are no solution, between the log may be hundreds of lines of text.Jun 19, 2022 · Добавил(а) microsin В SDK 12.0.0 или более новой версии встроена функция вывода отладочных сообщений в терминал реального времени (logging/debugging over Real Time Terminal, сокращенно RTT) соответствующий код находится в logger module NRF_LOG. The output from NRF_LOG_xxx can be displayed in a terminal (if logging over UART) or in the J-link RTT viewer (logging over RTT). The sdk_config.h file --> configuration wizard can be used to choose logging over UART or RTT. As you can see in nrf_log_backend_serial.c, logging over RTT uses SEGGER_RTT_xxx functions. #define NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE Size of buffer for partially processed strings. Size of the buffer is a trade-off between RAM usage and processing. if buffer is smaller then strings will often be fragmented. It is recommended to use size which will fit typical log and only the longer one will be fragmented. Note See full list on infocenter.nordicsemi.com My sdk_config.h has the following settings: #define NRF_LOG_BACKEND_RTT_ENABLED 1. #define NRF_LOG_BACKEND_UART_ENABLED 1. With the above settings applied to enable UART, I can always see debug output just fine using a separate terminal program to monitor the serial port on my MAC.And if I separately run JLinkExe -if SWD / JLinkRTTClientExe on ...To enable logging over RTT, define NRF_LOG_USES_RTT=1 in the project. To enable logging over UART, define NRF_LOG_USES_UART=1. To enable logging over raw UART, define NRF_LOG_USES_RAW_UART=1. You can specify only one of these defines, not several at the same time. To disable logging, do not specify either one. Available protocols// <o> NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE - Size of buffer for partially processed strings. // <i> Size of the buffer is a trade-off between RAM usage and processing. // <i> if buffer is smaller then strings will often be fragmented. // <i> It is recommended to use size which will fit typical log and only the // <i> longer one will be fragmented.2) Can I use the RTT viewer while debugging the code since RTT doesn't use SWO? Sometimes, the RTT viewer does not display log messages when I'm debugging. Sadly, I cannot find the condition while debugging with the RTT viewer turned on. 3) When debugging the project with SEGGER's Ozone, the terminal shows the RTT messages without the color ...Now to see log messages printed on RTT Viewer, open two terminals. On the first terminal, type this command and hit Enter JLinkExe -if SWD -device nrf52 -speed 4000 -autoconnect 1 On the second terminal, type this command and hit Enter JLinkRTTClient You will see the same log messages above appear on the terminal. Format log messages in NRF_LOGTo enable logging over RTT, define NRF_LOG_USES_RTT=1 in the project. To enable logging over UART, define NRF_LOG_USES_UART=1. To enable logging over raw UART, define NRF_LOG_USES_RAW_UART=1. You can specify only one of these defines, not several at the same time. To disable logging, do not specify either one. Available protocolsFor rather long log files I want to archive the text from RTT Viewer into a file. But I see no possibility to keep the color information with my text file. Neither the clipboard nor the file written with the "Terminal Logging" contains any color information. Screen shots are no solution, between the log may be hundreds of lines of text.nRF Terminal, a serial and RTT terminal. C/C++ from Microsoft which adds language support for C/C++ including features such as IntelliSense. 7.3 Open nRF Connect for VS Code. Open the extension by clicking the icon (1) and set up the basic configuration (2), which is simply selecting the nRF Connect SDK and nRF Connect Toolchain. RTT Viewer; SoftDevice; 3. C Programming. Timers; NRF_LOG. Clear History. Built with Grav - The Modern Flat File CMS. edit this page. C Programming NRF_LOG. Introduction. NRF_LOG macros are used for printing logs on screen from Smablo Cpu Shield. The log are helpfull when debugging project and printing interresting values and logs for us.Open J-Link RTT Viewer and connect to the board: LOG: Device "NRF52840_XXAA" selected. LOG: Found SW-DP with ID 0x2BA01477 LOG: Found SW-DP with ID 0x2BA01477 LOG: Scanning AP map to find all available APs LOG: AP [2]: Stopped AP scan as end of AP map has been reached LOG: AP [0]: AHB-AP (IDR: 0x24770011) LOG: AP [1]: JTAG-AP (IDR: 0x02880000) Both NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED are set to 1 in sdk_config.h. Perhaps I am using the wrong address or control block ID? My knowledge about RTT is admittedly quite limited. For reference, I am using a nrf52833. The text was updated successfully, but these errors were encountered:Even if I compile an example where NRF_LOG_BACKEND_SERIAL_USES_UART 1 is enabled by default in sdk_config.h I do not get any logs on terminal. I have chmod 666 of /dev/ttyACM0 and set baudrate to default 115200 but still nothing. If I set NRF_LOG_BACKEND_SERIAL_USES_RTT instead of UART I also get nothing on JLinkRRTClient.Even if I compile an example where NRF_LOG_BACKEND_SERIAL_USES_UART 1 is enabled by default in sdk_config.h I do not get any logs on terminal. I have chmod 666 of /dev/ttyACM0 and set baudrate to default 115200 but still nothing. If I set NRF_LOG_BACKEND_SERIAL_USES_RTT instead of UART I also get nothing on JLinkRRTClient.Menu path: (Top) → Sub Systems and OS Services → Logging → Enable Segger J-Link RTT backend. config LOG_BACKEND_RTT_BUFFER int "Buffer number used for logger output." range 0 SEGGER_RTT_MAX_NUM_UP_BUFFERS default 0 depends on LOG_BACKEND_RTT && ! LOG_MINIMAL && LOG help Select index of up-buffer used for logger output, by default it uses ...#define NRF_LOG_BACKEND_RTT_TEMP_BUFFER_SIZE Size of buffer for partially processed strings. Size of the buffer is a trade-off between RAM usage and processing. if buffer is smaller then strings will often be fragmented. It is recommended to use size which will fit typical log and only the longer one will be fragmented. Note The output from NRF_LOG_xxx can be displayed in a terminal (if logging over UART) or in the J-link RTT viewer (logging over RTT). The sdk_config.h file --> configuration wizard can be used to choose logging over UART or RTT. As you can see in nrf_log_backend_serial.c, logging over RTT uses SEGGER_RTT_xxx functions. To enable logging over RTT, define NRF_LOG_USES_RTT=1 in the project. To enable logging over UART, define NRF_LOG_USES_UART=1. To enable logging over raw UART, define NRF_LOG_USES_RAW_UART=1. You can specify only one of these defines, not several at the same time. To disable logging, do not specify either one. Available protocolsMenu path: (Top) → Sub Systems and OS Services → Logging → Enable Segger J-Link RTT backend → Logger behavior. config LOG_BACKEND_RTT_MODE_BLOCK bool "Block until message is transferred to host." depends on <choice: Logger behavior> help Waits until there is enough space in the up-buffer for a message. (The 'depends on' condition ...This is an NRF_CONFIG macro. #define NRF_LOG_BACKEND_RTT_TX_RETRY_CNT Writing to RTT retries. If RTT fails to accept any new data after retries module assumes that host is not active and on next request it will perform only one write attempt. On successful writing, module assumes that host is active and scheme with retry is applied again. NoteLOG_X for standard printf-like messages where X can be DBG, INF, WRN, or ERR. For example, the following line: LOG_INF("nRF Connect SDK Fundamentals"); would give the output. is a timestamp (formatted in hh:mm:ss.ms,us) associated with the generation of the message. The logger gets the timestamp by calling the kernel function k_cycle_get_32 ... J-Link RTT Viewer is the main GUI application to use all features of RTT on the debugging host (Windows, macOS and Linux). RTT Viewer can be used stand-alone, opening an own connection to J-Link and target or in parallel to a running debug session, attaching to it and using this existing J-Link connection. Now to see log messages printed on RTT Viewer, open two terminals. On the first terminal, type this command and hit Enter JLinkExe -if SWD -device nrf52 -speed 4000 -autoconnect 1 On the second terminal, type this command and hit Enter JLinkRTTClient You will see the same log messages above appear on the terminal. Format log messages in NRF_LOG Menu path: (Top) → Sub Systems and OS Services → Logging. config LOG_BACKEND_RTT bool "Enable Segger J-Link RTT backend" default y if ! SHELL_BACKEND_RTT depends on USE_SEGGER_RTT && ! LOG_MINIMAL && LOG help When enabled, backend will use RTT for logging. This backend works on a per message basis. Only a whole message (terminated with a ...For rather long log files I want to archive the text from RTT Viewer into a file. But I see no possibility to keep the color information with my text file. Neither the clipboard nor the file written with the "Terminal Logging" contains any color information. Screen shots are no solution, between the log may be hundreds of lines of text.Even if I compile an example where NRF_LOG_BACKEND_SERIAL_USES_UART 1 is enabled by default in sdk_config.h I do not get any logs on terminal. I have chmod 666 of /dev/ttyACM0 and set baudrate to default 115200 but still nothing. If I set NRF_LOG_BACKEND_SERIAL_USES_RTT instead of UART I also get nothing on JLinkRRTClient.Jan 14, 2020 · という箇所を探し出し、 #define NRF_LOG_BACKEND_UART_ENABLED 1 と有効にしてください。 JLink経由でのデバッグ (SEGGER_RTTを使ってみる) JLink経由でデバッグを行うためには、JLink本体が欠かせません。 2) Can I use the RTT viewer while debugging the code since RTT doesn't use SWO? Sometimes, the RTT viewer does not display log messages when I'm debugging. Sadly, I cannot find the condition while debugging with the RTT viewer turned on. 3) When debugging the project with SEGGER's Ozone, the terminal shows the RTT messages without the color ...3.2 配置RTT打印 nRF_Log 中勾选 RTT 选项 切换回 Text Editor 界面,可以发现已经把 NRF_LOG_BACKEND_RTT_ENABLE 设置为 1,也就是使能了 RTT。 在 nrf_log_default_backends.c 文件中,当我们使能了 NRF_LOG_BACKEND_RTT_ENABLE 后,对应会修改文件中对 RTT 初始化 四、开始打印日志 4.1 串口打印 打开串口调试助手,波特率设置为 115200 4.2 RTT打印 找到你的 SEGGER 的安装位置,找到驱动版本下的 JLinkRTTViewer.exe 打开后弹出选择界面。본 동영상 포함된 블로그 글 : http://igotit.tistory.com/2328 제목 : 문제해결. nRF5 SDK. NRF_LOG_INFO not shown in SES Debug Terminal.in this case ...Both NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED are set to 1 in sdk_config.h. Perhaps I am using the wrong address or control block ID? My knowledge about RTT is admittedly quite limited. For reference, I am using a nrf52833. The text was updated successfully, but these errors were encountered:This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.An easy fix for this is to switch the NRF_LOG driver to RTT, which can send data over the JLINK programmers you will be getting next week. This can be done by setting NRF_LOG_BACKEND_RTT_ENABLED to 1 in your config, and by using an RTT client. Segger Embedded Studio automatigically displays those logs in the console.1> Compiling 'nrf_log_backend_serial.c' 2> Compiling 'nrf_log_backend_rtt.c' 3> Compiling 'nrf_log_backend_uart.c' 4> Compiling 'nrf_log_default_backends.c' 1> cc1: fatal error: C:\Nordic\components\libraries\experimental_log\src\nrf_log_backend_serial.c: No such file or directory 1> compilation terminated.Both NRF_LOG_ENABLED and NRF_LOG_BACKEND_RTT_ENABLED are set to 1 in sdk_config.h. Perhaps I am using the wrong address or control block ID? My knowledge about RTT is admittedly quite limited. For reference, I am using a nrf52833. The text was updated successfully, but these errors were encountered:Menu path: (Top) → Sub Systems and OS Services → Logging → Enable Segger J-Link RTT backend. config LOG_BACKEND_RTT_BUFFER int "Buffer number used for logger output." range 0 SEGGER_RTT_MAX_NUM_UP_BUFFERS default 0 depends on LOG_BACKEND_RTT && ! LOG_MINIMAL && LOG help Select index of up-buffer used for logger output, by default it uses ...3.2 配置RTT打印 nRF_Log 中勾选 RTT 选项 切换回 Text Editor 界面,可以发现已经把 NRF_LOG_BACKEND_RTT_ENABLE 设置为 1,也就是使能了 RTT。 在 nrf_log_default_backends.c 文件中,当我们使能了 NRF_LOG_BACKEND_RTT_ENABLE 后,对应会修改文件中对 RTT 初始化 四、开始打印日志 4.1 串口打印 打开串口调试助手,波特率设置为 115200 4.2 RTT打印 找到你的 SEGGER 的安装位置,找到驱动版本下的 JLinkRTTViewer.exe 打开后弹出选择界面。Menu path: (Top) → Sub Systems and OS Services → Logging → Enable Segger J-Link RTT backend. config LOG_BACKEND_RTT_BUFFER int "Buffer number used for logger output." range 0 SEGGER_RTT_MAX_NUM_UP_BUFFERS default 0 depends on LOG_BACKEND_RTT && ! LOG_MINIMAL && LOG help Select index of up-buffer used for logger output, by default it uses ...SEGGER's Real Time Transfer (RTT) is the proven technology for system monitoring and interactive user I/O in embedded applications. It combines the advantages of SWO and semihosting at very high performance. Bi-directional communication with the target application. Very high transfer speed without affecting real time behavior. Menu path: (Top) → Sub Systems and OS Services → Logging → Enable Segger J-Link RTT backend. config LOG_BACKEND_RTT_BUFFER int "Buffer number used for logger output." range 0 SEGGER_RTT_MAX_NUM_UP_BUFFERS default 0 depends on LOG_BACKEND_RTT && ! LOG_MINIMAL && LOG help Select index of up-buffer used for logger output, by default it uses ... 10l_2ttl