RTT presence not properly detected

[Konstantin Klitenik]

I'm seeing an issue where the entire system hangs if a crash is encountered. I was able to trace it down to LOG_PANIC(). It attempts to flush all the logs before proceeding, which makes sense. However, zephyr doesn’t seem to be able to detect that RTT is not connected and basically hangs spinning on RTT write. 

[Kenneth]

I guess you can disable log backend to rtt if you are not interested in the log. Alternatively you may try if any of these config options help:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_LOG_BACKEND_RTT_RETRY_CNT 
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/kconfig/index.html#CONFIG_LOG_BACKEND_RTT_RETRY_DELAY_MS 

[Konstantin Klitenik]

Well, we want the logs when RTT is connected. But those settings don't seem to do anything. Those default to 4 retries and delay is 5ms. We never changed them and when RTT is not connected, it's stuck forever.

[Kenneth]

I see your point, but unfortunately it kind of fight the purpose of the LOG_PANIC(), so I don't see any other way than to disable logging to RTT. Or possible start some wathdog that for sure will reset the system.

Kenneth

[Riccardo Gaiati]

Hi, I have the RTT log disable but LOG_PANIC still does not work in case of fault errors. I am using a littlefs partition to store the log file.

I can see that the function is invoked, but the info are not stored at all in the log file. 

Is there something else that need to be disable in order to have the LOG_PANIC working ?

Thanks in andvance !

Riccardo

[Kenneth]

Please make a new devzone case for your question, closing this thread.

Kenneth