How to see the NRF_LOG_INFO() log?

[William.SportsArt]

Hi,

My environment:

MDK IDE-Version: V5.38.0.0
SKD v17.1.0
nRF52-DK PCA10040 / s132

I tried to set "NRF_LOG_BACKEND*" in sdk_config.h, all of the definitions are enabled and I still can not see the "NRF_LOG_INFO()" log!?

How(Where) do I see the log? 

Thank you.

[Karl Ylvisaker]

Hello,

Are you working with an example from the SDK?
The default logger output will be over UART, and so you may see the logs using a serial terminal/monitor if you have set the log level high enough to be output.
If you are using the BLE UART examples then the default logger output will be RTT, in which case you can see it in the 'debug terminal' or standalone RTT Viewer application from Segger.

Could you share your sdk_config.h file, so that I can verify if there's any issues with the configuration?

Best regards,
Karl

[William.SportsArt]

Hi Karl,

Thank you reply.

The project works with an example from 
"\nRF52-DK\nRF5_SDK_17.1.0_ddde560\examples\ble_central\ble_app_uart_c\pca10040\s132\arm5_no_packs".
The sdk_config.h is in the attachment.

8473.sdk_config.h

[Karl Ylvisaker]

William.SportsArt said:

Thank you reply.

No problem at all, I am happy to help! :) 

The sdk_config.h shows that it is the RTT backend that is enabled for the NRF_LOG module, and so you will either need to use the Debug terminal in SES, or the Segger RTT Viewer standalone desktop application to see the log output. The reason for this is that the BLE UART application already uses the UART for the application, and so it can not also be used for the logger.
Please try either one of these options, and let me know if you then are able to see your logs.

Best regards,
Karl

[William.SportsArt]

Hi Karl,

There are 2 ways to see the debug log:

1. Using printf() and then debug string redirect to UART. (Figure 1)

2. Using NRF_LOG_INFO()and then debug string redirect to Segger J-Link Viewer. (Figure 2)

These 2 ways also see the main.c of example. (Figure 3)

Now, I can see the log, thank you.