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?

[Elbert]

Hi nRF5xFanBoy,

I understand that (tried by log level per application file), but that is not the problem I see.

CONFIG_LOG_OVERRIDE_LEVEL=4 in the prj.conf should override log statements level in all files, including kernel. With CONFIG_LOG_OVERRIDE_LEVEL=3 all corresponding log statements are shown, but with CONFIG_LOG_OVERRIDE_LEVEL=4 a Cortex hard fault occurs in the oZone debugger.

That is the real problem and I do not understand why.

Best regards, Elbert

[nRF5xFanboy]

Hi Elbert,

Did you increase the stack size for the Ozone debugger (it consumes 'some'extra resources)

Best regards,
    nRF5xFanBoy

[Elbert]

Increased it a lot, but without any effect.

[nRF5xFanboy]

Is it always the same thread / file or function where it crashes?
Perhaps it could be a log_dbg statement with invalid arguments?
Is it crashing directly at start or lateron during running some time?

Instead of CONFIG_LOG_MODE_IMMEDIATE=y
you can try 
CONFIG_LOG_MODE_DEFERRED=y
or 
CONFIG_LOG_MODE_MINIMAL=y

both with additional
CONFIG_LOG_PRINTK=y

[Elbert]

It does not break at application main(), but crashes before.

Deferred/Minimal = same result.

CONFIG_LOG_PRINTK does not give information.