Logging issue on nRF_Connect 1.6.0 (Zephyr OS build v2.6.0-rc1-ncs1) - Unable to view the log's timestamp

[Rafalino]

Hello,

I have upgraded my project from nRF_Connect 1.5.1 to nRF_Connect 1.6.0.

It runs on nRF9160 and I use RTT viewer v7.50a.

The problem that I see is that the logs now don't contain the log time stamp.

It looks like this on nRF_Connect 1.6.0,  Zephyr OS build v2.6.0-rc1-ncs1 (no timestamp):

00> I: Network registration status: REGISTERED_HOME
00> I: LTE is now Connected

 

It used to look like this on nRF_Connect 1.5.1  Zephyr OS build v2.4.99-ncs2 (with timestamp):

00> [00:00:06.982,177] <inf> lte_app: Network registration status: REGISTERED_HOME
00> [00:00:06.982,208] <inf> lte_app: LTE is now Connected

Any suggestions on how to make it work on  nRF_Connect 1.6.0 ?

Thank you in advance ,

Rafalino

[Øyvind]

Hello Rafalino, 

Please note that our technical support staff is currently understaffed due to summer vacation, and a delayed answer must be expected.

---

Are you able to reproduce this in one of our standard samples? E.g. nRF9160 AT Client?

Kind regards,
Øyvind

[Rafalino]

Hello Øyvind,

I have tried  the https_client nRF9160 example of  nRF_Connect 1.6.0 and it also had the issue of no timestamp at the log.

Any other suggestions ?

Rafalino

[Øyvind]

Rafalino, did you add RTT yourself to the sample? If so, what did you add? If not, what board are you building for? The setting may be added through board config.

[Rafalino]

Hello Øyvind, 

These are the settings that I have on prj.conf : 

CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_LOG_MODE_DEFERRED=y
CONFIG_LOG_MODE_MINIMAL=n
CONFIG_LOG_STRDUP_BUF_COUNT=14
CONFIG_LOG_STRDUP_MAX_STRING=1024

# Segger RTT
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_FORMAT_TIMESTAMP=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_UART=n

Is there a chance something is wrong with Zephyr OS build v2.6.0-rc1-ncs1  ?

I saw the following : zephyr-v2.6.0 and it does say : Logging subsystem overhauled

Could that be the case ?

Rafalino

[Øyvind]

That is a good question. I was able to confirm missing timestamps in NCS 1.6.0. Have forwarded and awaiting feedback from our NCS team.

[Krzysztof Chruscinski]

Hi,

the reason for lack of logs is that different logging mode is used, namely `LOG_MODE_MINIMAL` which is simple redirection of all logs to printk with prefix for log level (E,W,I,D).

I see that you are enabling `LOG_MODE_DEFERRED` but seems that it is not enabled. Can you check in menuconfig what is selecting `LOG_MODE_MINIMAL` or `LOG_MINIMAL`?