Different debug console behavior between zephyr 3.2 and 3.5

[MarsMSWu]

Hi, all

My previous zephyr base is 3.2 and current zephyr base is 3.5.
Both are them test in LPC55s69 EVB.
My project folder and config file in base 3.2 is work fine, can output log and LED toggle by 1s timer.
The debug log "SEC" also show by 1s timer...and button INTR also can detect by pressed 0 or 1.

But move my project folder and config file in base 3.5 is work abnormal.
It seems like LED still can toggle by 1s timer but output log by 1s timer is not show and no button INTR event.
No log can let me know is button INTR work or not but LED still can toggle by 1s timer...maybe the code is work

In my understanding, it should something difference between 3.2 and 3.5 for debug console control.

But I also try hello world in base 3.5, it works fine and can always show debug log in while loop.

If so, it seems like 3.5 should be no impact for debug console.

I had try to compare the config file, but not sure which one is important key config item for this behavior.
I really have no idea, is any one can advice for me ?

Thanks~

[MarsMSWu]

Hi all,

I have no idea for this behavior, so I try to not set CONFIG_LOG=y

After this try then the debug console can show more...even if 1s timer becomes abnormal

I don't know why... because CONFIG_LOG=y also set in base 3.2 and it works fine.

Thanks~

[DerekSnell]

Hi @MarsMSWu ,
It seems your app is dependent on the Logging subsystem. And yes, when using Logging, then CONFIG_LOGGING=y should be selected. You can read more at Logging. But it seems you found the key difference between the v3.2 build and your current build.

Best regards

[MarsMSWu]

Hi @DerekSnell ,
Do you mean you also agree "not set CONFIG_LOG=y" is correct solution for my case ?
BTW, CONFIG_LOGGING can't parse while compile...

I try to compare the BIN file size, as below


And


The BINARY size difference is 23KB, is it correct ? Just "CONFIG_LOG=y" enabled or not...

Thanks.

[DerekSnell]

Hi @MarsMSWu ,
Sorry, CONFIG_LOGGING was an error. As you found, the correct symbol is CONFIG_LOG.

Do you mean you also agree "not set CONFIG_LOG=y" is correct solution for my case ?

I was confused by your previous description, and the details of this issue. But based on your last response, and rereading this, it seems your v3.5 port only prints everything when CONFIG_LOG=n. Is that correct? I assume you are not using the Logging APIs then. Are you printing to the console with printk()?

If your app is not using the Logging APIs and features, then you can disable that subsystem. Many of the Zephyr drivers and subsystems use Logging, so you may find it helpful to enable for debugging. If you are using printk() in your app, and it does not print with CONFIG_LOG=y, do you have the CONFIG_LOG_PRINTK Kconfig selected? I also found this helpful blog from our friends at Golioth.

As for the memory used by the Logging subsystem: the Logging features are very configurable. The more features enabled, the more memory it consumes. If you want to include Logging with you app, you can try the different configurations to optimize the memory usage.

Best regards

[MarsMSWu]

Hi @DerekSnell ,
Yes, can output everything while CONFIG_LOG=n and we only use printk() for output.
Not use any LOG API function.

The CONFIG_LOG will impact my debug console output.
I try to keep enable CONFIG_LOG and add CONFIG_LOG_PRINTK=y then can't output everything.

I check my .config file of build folder, there is no CONFIG_LOG_PRINTK in the file.
Do you mean CONFIG_PRINTK ?

Thanks.

[DerekSnell]

Hi @MarsMSWu ,
I am referring to CONFIG_LOG_PRINTK.
Best regards