Kconfig CONFIG_LOG_OVERRIDE_LEVEL=4 breaks logging system

RE: Kconfig CONFIG_LOG_OVERRIDE_LEVEL=4 breaks logging system

wkpolara — Tue, 18 Oct 2022 13:48:24 GMT

Alright, thanks Håkon

RE: Kconfig CONFIG_LOG_OVERRIDE_LEVEL=4 breaks logging system

Håkon Alseth — Tue, 18 Oct 2022 13:00:08 GMT

Hi Walt,

I can confirm that there's an issue with this configuration and the deferred logging option:

[quote user="wkpolara"]CONFIG_LOG_OVERRIDE_LEVEL=4[/quote]

The problem seems to be specific to the logging in the MPU initialization, more specifically these two LOG_DBG calls:

https://github.com/nrfconnect/sdk-zephyr/blob/v3.1.99-ncs1/arch/arm/core/aarch32/mpu/arm_mpu_v8_internal.h#L174

https://github.com/nrfconnect/sdk-zephyr/blob/v3.1.99-ncs1/arch/arm/core/aarch32/mpu/arm_mpu.c#L341

Disabling the MPU is not recommended.

One way to work around this is to change the logging method to for instance minimal footprint (CONFIG_LOG_MODE_MINIMAL).

I'll report this issue back to the team that works with the logger.

Kind regards,

Håkon

RE: Kconfig CONFIG_LOG_OVERRIDE_LEVEL=4 breaks logging system

wkpolara — Fri, 14 Oct 2022 17:48:33 GMT

Hi Håkon,

Thank you for the reply. I see your point about the gpio_pin_get_dt(), and your suggestion to just print directly the Info and Debug messages is good.

I understand that where the default log level is used, that can alternatively be used to change the log level in those modules.

However, I would still expect CONFIG_LOG_OVERRIDE_LEVEL=4 to work. Why does it break it instead?

Regards,

Walt

RE: Kconfig CONFIG_LOG_OVERRIDE_LEVEL=4 breaks logging system

Håkon Alseth — Thu, 13 Oct 2022 12:15:23 GMT

Hi,

[quote user=""]Edit prj.conf to set CONFIG_LOG_OVERRIDE_LEVEL=4 [/quote]

This will set all registered log modules to debug mode, which will use alot of stack memory.

To enable a given level on your specified logging module, you do this in the definition itself.

In your case, it is this:

LOG_MODULE_REGISTER(Blinky, CONFIG_LOG_DEFAULT_LEVEL);

So f you set CONFIG_LOG_DEFAULT_LEVEL=4 in prj.conf, you should get both info and debug prints.

This function:

ret = gpio_pin_get_dt(&led);

Is for a GPIO configured as input (ie. reads NRF_P0->IN register), and will not return the state of a output. The problem is that the zephyr gpio driver does not have a API for reading the state of a output device, it just sets it directly.

I would recommend that you instead just print directly:

LOG_INF("Info");
LOG_DBG("Debug");

Kind regards,

Håkon

RE: Kconfig CONFIG_LOG_OVERRIDE_LEVEL=4 breaks logging system

wkpolara — Wed, 12 Oct 2022 21:01:37 GMT

devzone.nordicsemi.com/.../1185.main.c

The "prj.conf" file won't upload as that file type is not allowed, but the full contents are shown above in the original post.