Logging/Printing issues in the nRF 9160 DK

[Omar]

I am using the nrf9060dk device with the nrf connect software (V2.5.0), but I am facing some logging issues that I did not encounter in the previous versions of zephyr.

One issue is that when I use the printk() function, I get —dropped messages— and changing the baudrate does not help, even though priniting this data works fine in the nrf52840dk device.

Another issue is that the dk device restarts unexpectedly when -I assume- a fatal error happens, and I do not see any FATAL ERROR message in the logs as I did in the nrf52840 device.

I need your help urgently. I cannot troubleshoot without a functional logging system.

[Kazi Afroza Sultana]

Hello,

''One issue is that when I use the printk() function, I get —dropped messages— and changing the baudrate does not help, even though priniting this data works fine in the nrf52840dk device.''

Can you please show the code snippet of prinktk() part and the output you are seeing on the terminal? 

It seems like you are using putty as serial terminal. Can you please try to use another terminal like Termite?

''Another issue is that the dk device restarts unexpectedly when -I assume- a fatal error happens, and I do not see any FATAL ERROR message in the logs as I did in the nrf52840 device''. It happens for which application on the DK and what is the error log you got after building the application?

Thanks.

BR

Kazi

[Omar]

The first issue is solved by increasing the CONFIG_LOG_BUFFER_SIZE.

Restart problem occurs when I use MQTT publish function mqtt_publish()

[Kazi Afroza Sultana]

Hello,

You can disable CONFIG_RESET_ON_FATAL_ERROR in the config file. This enables the fatal error handler defined for Nordic DKs. When it is used, the system restarts after a fatal error. You also mentioned ''Restart problem occurs when I use MQTT publish function mqtt_publish()''.

So, CONFIG_RESET_ON_FATAL_ERROR=n might give you details on the crash.

[Omar]

now it stops instead of rebooting, but i can't see the fatal error message

[Kazi Afroza Sultana]

Hello,

It might be a secure fault; therefore, it is caught by TF-M, not the application. You can try to add the following configurations as well that should make TF-M use the same UART as the application for crash dumps.:

CONFIG_TFM_LOG_LEVEL_SILENCE=n

CONFIG_TFM_EXCEPTION_INFO_DUMP=y

CONFIG_TFM_SECURE_UART_SHARE_INSTANCE=y

CONFIG_TFM_SECURE_UART0=y