Logging

RE: Logging

Elbert — Wed, 05 Oct 2022 12:23:55 GMT

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

Deferred/Minimal = same result.

CONFIG_LOG_PRINTK does not give information.

RE: Logging

nRF5xFanboy — Wed, 05 Oct 2022 12:05:21 GMT

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

RE: Logging

Elbert — Wed, 05 Oct 2022 11:54:19 GMT

Increased it a lot, but without any effect.

RE: Logging

nRF5xFanboy — Wed, 05 Oct 2022 11:52:12 GMT

Hi Elbert,

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

Best regards,
nRF5xFanBoy

RE: Logging

Elbert — Wed, 05 Oct 2022 11:49:23 GMT

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

RE: Logging

nRF5xFanboy — Wed, 05 Oct 2022 11:39:09 GMT

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

RE: Logging

Elbert — Tue, 04 Oct 2022 13:49:19 GMT

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

RE: Logging

nRF5xFanboy — Thu, 01 Sep 2022 11:50:35 GMT

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

RE: Logging

Elbert — Thu, 01 Sep 2022 09:04:43 GMT

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

RE: Logging

nRF5xFanboy — Wed, 31 Aug 2022 19:22:41 GMT

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