Skip to content

tests: logging: ip_k66f: build failures #89067

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.

Sign up for GitHub

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

Jump to bottom
Open
hakehuang opened this issue Apr 25, 2025 · 1 comment · May be fixed by #89115
Open

tests: logging: ip_k66f: build failures #89067

hakehuang opened this issue Apr 25, 2025 · 1 comment · May be fixed by #89115
Assignees
@mmahadevan108 @dleach02
Labels
area: Logging bug The issue is a bug, or the PR is fixing a bug platform: NXP NXP

Comments

@hakehuang
Copy link
Collaborator

Describe the bug

-- Generated zephyr.dts: /home/shared/disk/zephyr_project/zephyr_test/zephyr/twister-out/ip_k66f_mk66f18/zephyr/tests/subsys/logging/log_core_additional/logging.log_user/zephyr/zephyr.dts
-- Generated pickled edt: /home/shared/disk/zephyr_project/zephyr_test/zephyr/twister-out/ip_k66f_mk66f18/zephyr/tests/subsys/logging/log_core_additional/logging.log_user/zephyr/edt.pickle
-- Generated devicetree_generated.h: /home/shared/disk/zephyr_project/zephyr_test/zephyr/twister-out/ip_k66f_mk66f18/zephyr/tests/subsys/logging/log_core_additional/logging.log_user/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/shared/disk/zephyr_project/zephyr_test/zephyr/twister-out/ip_k66f_mk66f18/zephyr/tests/subsys/logging/log_core_additional/logging.log_user/zephyr/dts.cmake

warning: LOG_PRINTK (defined at subsys/logging/Kconfig.processing:8) was assigned the value 'n' but
got the value 'y'. See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOG_PRINTK and/or
look up LOG_PRINTK in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: LOG_PRINTK (defined at subsys/logging/Kconfig.processing:8) has direct dependencies !USERSPACE && !LOG_MODE_MINIMAL && LOG with value n, but is currently being y-selected by the following symbols:
 - LOG_BACKEND_RTT_FORCE_PRINTK (defined at subsys/logging/backends/Kconfig.rtt:103), with value y, direct dependencies LOG_BACKEND_RTT && !LOG_FRONTEND_ONLY && !LOG_MODE_MINIMAL && LOG (value: y), and select condition LOG_BACKEND_RTT && !LOG_FRONTEND_ONLY && !LOG_MODE_MINIMAL && LOG (value: y)
Parsing /home/shared/disk/zephyr_project/zephyr_test/zephyr/Kconfig
Loaded configuration '/home/shared/disk/zephyr_project/zephyr_test/zephyr/boards/segger/ip_k66f/ip_k66f_defconfig'
Merged configuration '/home/shared/disk/zephyr_project/zephyr_test/zephyr/tests/subsys/logging/log_core_additional/log_user.conf'
Merged configuration '/home/shared/disk/zephyr_project/zephyr_test/zephyr/twister-out/ip_k66f_mk66f18/zephyr/tests/subsys/logging/log_core_additional/logging.log_user/zephyr/misc/generated/extra_kconfig_options.conf'

error: Aborting due to Kconfig warnings

CMake Error at cmake/modules/kconfig.cmake:365 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  cmake/modules/zephyr_default.cmake:131 (include)
  share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  cmake/package_helper.cmake:101 (find_package)

Please also mention any information which could help others to understand
the problem you're facing:

  • What target platform are you using?
  • ip_k66f
  • What have you tried to diagnose or workaround this issue?
  • git bisect
  • Is this a regression? If yes, have you been able to "git bisect" it to a
    specific commit?
    this is introduced by this pr
https://github.com/zephyrproject-rtos/zephyr/pull/88269

To Reproduce

Steps to reproduce the behavior:
west build -p -b ip_k66f/mk66f18 tests/subsys/logging/log_core_additional -T logging.log_user

Expected behavior

build pass

Impact

logging system on ip_k66f platform

Logs and console output

see above

Additional context
@hakehuang hakehuang added the bug The issue is a bug, or the PR is fixing a bug label Apr 25, 2025
cjwinklhofer added a commit to cjwinklhofer/zephyr that referenced this issue Apr 25, 2025
@cjwinklhofer
tests: logging: Allow LOG_PRINTK from user space
d76a5f6 
The commit '3b29b9fa3b4 (tests: logging: restore userspace testing,
2025-04-18)' set CONFIG_LOG_PRINTK=n which brakes the build on the
platform 'ip_k66f'.

Without CONFIG_LOG_PRINTK=n (dependency from CONFIG_USERSPACE=y) some
tests in 'tests/subsys/logging/log_core_additional/logging.log_user'
would not build.

Remove this dependency so that LOG_PRINTK can also be used from user
space, which is possible since '77925656ab8 (logging: Fix runtime
message creation in user-mode thread, 2025-04-18)' and reset
CONFIG_LOG_PRINTK=y.

Fixes: zephyrproject-rtos#89067
Signed-off-by: Christoph Winklhofer <cj.winklhofer@gmail.com>
@cjwinklhofer
Copy link
Contributor

Prepared a possible fix: LOG_PRINTK can be called from user space - hence, reset CONFIG_LOG_PRINTK=y and remove the dependency from CONFIG_USERSPACE=y (in subsys/logging/Kconfig.processing). Hope this helps!

@cjwinklhofer cjwinklhofer linked a pull request Apr 25, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmahadevan108 mmahadevan108

@dleach02 dleach02

Labels
area: Logging bug The issue is a bug, or the PR is fixing a bug platform: NXP NXP
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

tests: logging: Allow LOG_PRINTK from user space cjwinklhofer/zephyr
5 participants
@hakehuang @henrikbrixandersen @cjwinklhofer @mmahadevan108 @dleach02