Logging

[Elbert]

nRF Connect SDK v2.0.0

VS Code 1.70.2

nRF9160 development kit

To view all possible log messages the fololwing logging configuration is set up in prj.conf:

CONFIG_LOG=y

CONFIG_LOG_MODE_IMMEDIATE=y

CONFIG_LOG_OVERRIDE_LEVEL=4

This causes a Cortex hard fault in debugger session.

With CONFIG_LOG_OVERRIDE_LEVEL=3 no problem and it is possible to step through the application in the debugger.

Increasing thread stack size does not help.

Does anyone known how to solve this?

[nRF5xFanboy]

Hi Elbert,

just a though 

Could you please check your LOG_DBG statements I think one of them may cause this hard-fault due to wrong parameters of formatting.

Best regards,
    nRF5xFanBoy

[Elbert]

Hi nRF5xFanBoy,

Thanks for your thought.

With CONFIG_LOG_OVERRIDE_LEVEL=3 the LOG_DBG statements in my application are shown correct, so I assume that when set to 4 these statements are still OK. Could it be possible that a LOG_DBG statement in other (nRF connect) sources is incorrect? How can I verify this?

Best regards,

Elbert

[nRF5xFanboy]

Hi Elbert,

This is correct if the log level is at runtime.
But the zephyr logging is handled at compile time. This inactive parts are not in the runtime code.
So is level3 is active , the logging debug (=level4) do not show.

Best regards,
    nRF5xFanBoy

[Elbert]

Does the mean that it is not possible to use CONFIG_LOG_OVERRIDE_LEVEL=4?

[nRF5xFanboy]

Hi Elbert,

I try to clarify.

When you use log debug statements in the code and compile with CONFIG_LOG_OVERRIDE_LEVEL = 4 the log debug statements are performed.

When you compile with CONFIG_LOG_OVERRIDE_LEVEL = 3 the log debug statements are not performed because they are removed from code during compilation.

LOG_OVERRIDE_LEVEL — Zephyr Project Documentation

Hope it helps,

best regards,
   nRF5xFanBoy