How to debug configuration issues?

RE: How to debug configuration issues?

Torsten Robitzki — Tue, 22 Oct 2024 14:12:30 GMT

Thank you!

RE: How to debug configuration issues?

Amanda Hsieh — Tue, 22 Oct 2024 14:08:03 GMT

I see there are three modes in <choice LOG_MODE: Mode>, and `CONFIG_LOG_MODE_IMMEDIATE=y` is used in my colleague's example. so it's worth to try.

RE: How to debug configuration issues?

Torsten Robitzki — Tue, 22 Oct 2024 13:35:23 GMT

So, you were just guessing? :-)

RE: How to debug configuration issues?

Amanda Hsieh — Tue, 22 Oct 2024 13:30:19 GMT

You can check the .config under build/mcuboot/zephyr to confirm the value of CONFIG_LOG_MODE_MINIMAL. I found CONFIG_LOG_MODE_MINIMAL=n doesn't take effect in the .config, and then try CONFIG_LOG_MODE_IMMEDIATE.

RE: How to debug configuration issues?

Torsten Robitzki — Tue, 22 Oct 2024 09:50:38 GMT

Hu Amanda,

thank you very much for your answer. According to the cited documentation, this should then work (LOG_BACKEND_RTT get the value y), right? :

CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_FRONTEND_ONLY=n
CONFIG_LOG_MODE_MINIMAL=n

But it still does not accept the value `y` (same message, as above). Adding `CONFIG_LOG_MODE_IMMEDIATE=y` does the trick, but where would I be able to pick up that information? How did you managed to find that adding `CONFIG_LOG_MODE_IMMEDIATE=y` would solve this configuration problem?

RE: How to debug configuration issues?

Amanda Hsieh — Mon, 21 Oct 2024 18:57:48 GMT

Hi,

See the description of CONFIG_LOG_BACKEND_RTT:

You can set CONFIG_LOG_MODE_IMMEDIATE=y and it would also disable CONFIG_LOG_MODE_MINIMAL.

Check out my colleague's unofficial sample mcuboot_smp_uart_feat_rtt.

Regards,
Amanda H.