How does SLM use RTT?

[xinjiang]

How does the slm routine of ncs1.9.1 use rtt log. Below is my configuration:

CONFIG_LOG=y
CONFIG_LOG_DEFAULT_LEVEL=3

CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_UART=n

With the default configuration, there should be RTT log output, but nothing happens in the actual window.

[Edvin]

Hello,

I have actually not used Segger Embedded Studio with the nRF Connect SDK. 

If you flash the sample you are running, and try to open Segger RTT Viewer after the application has started. Do you see the log in RTT Viewer?

Best regards,

Edvin

[xinjiang]

RTT Viewer also has no log output.

[xinjiang]

SLM is serial_lte_modem demo.Can you try running it and see if there is any log output.

[Edvin]

Edvin said:

What HW are you running on?

What HW are you running this on? A DK?

Best regards,

Edvin

[xinjiang]

Yes, is 9160 DK.

[Edvin]

I don't know exactly what's going on. Can you please try to run the same sample using the nRF Connect for VS Code extension tool for Visual Studio Code?

I have not used SES in NCS, and it is now discontinued (since NCS v2.0.0). I see that you are using v1.9.1, but perhaps it (SES) was not set up correctly. 

So can you please try the VS Code "IDE", and see if you can connect to the RTT Terminal either through nRF Connect for VS Code, or the RTT Viewer after programming via nRF Connect for VS Code?

Best regards,

Edvin

[xinjiang]

The RTT of ncs2.0.0 can output logs normally, but not of ncs1.9.1. This is my compiled configuration file, can you find the problem?0131.autoconf.h

[Edvin]

I can't see no obvious reason for this from autoconf.h. When you are testing ncs2.0.0 and ncs1.9.0, are you testing both using nRF Connect for VS Code?

I remembered one other thing that you can check. When you are using Segger Embedded Studio in NCS, you need to reload the project (close and re-open) whenever you change something in prj.conf (or other .conf files). Make sure that you try this.

BR,

Edvin