Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

boards: thingy53: Inconsistent method of setting USB related log level #54703

Closed
mkapala-nordic opened this issue Feb 10, 2023 · 0 comments · Fixed by #54488
Closed

boards: thingy53: Inconsistent method of setting USB related log level #54703

mkapala-nordic opened this issue Feb 10, 2023 · 0 comments · Fixed by #54488
Labels
bug The issue is a bug, or the PR is fixing a bug

Comments

@mkapala-nordic
Copy link
Contributor

Describe the bug
Current method of setting default USB related log levels for Thingy:53 board leads to generating inconsistent configuration:

CONFIG_USB_CDC_ACM_LOG_LEVEL=0
CONFIG_USB_CDC_ACM_LOG_LEVEL_OFF is not set
CONFIG_USB_CDC_ACM_LOG_LEVEL_ERR is not set
CONFIG_USB_CDC_ACM_LOG_LEVEL_WRN is not set
CONFIG_USB_CDC_ACM_LOG_LEVEL_INF=y
CONFIG_USB_CDC_ACM_LOG_LEVEL_DBG is not set

Affected are USB_CDC_ACM_LOG_LEVEL and USB_DEVICE_LOG_LEVEL options.

Expected behavior
Logs config should be consistent:

CONFIG_USB_CDC_ACM_LOG_LEVEL_OFF=y
# CONFIG_USB_CDC_ACM_LOG_LEVEL_ERR is not set
# CONFIG_USB_CDC_ACM_LOG_LEVEL_WRN is not set
# CONFIG_USB_CDC_ACM_LOG_LEVEL_INF is not set
# CONFIG_USB_CDC_ACM_LOG_LEVEL_DBG is not set
CONFIG_USB_CDC_ACM_LOG_LEVEL=0

To Reproduce
Steps to reproduce the behavior:

  • Enable CONFIG_LOG=y in prj.conf of hello_world sample
  • Build hello_world sample for thingy53_nrf5340_cpuapp
  • Check build/zephyr/.config
  • Logs related options are inconsistent

Environment (please complete the following information):

  • OS: Ubuntu 22.04 LTS
  • Toolchain: zephyr sdk 0.15.2
  • Commit SHA or Version used: 3.3.0-rc2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
1 participant