-
Notifications
You must be signed in to change notification settings - Fork 6.1k
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
Kconfig: build system ignores 'default' values for some symbols in SoCs-level 'Kconfig.defconfig' after HWMv2 was applied #72793
Comments
The issue touches not only ARC nSIM platforms. For example, |
Workaround for zephyrproject-rtos#72793. Because of pointed issue CONFIG_XIP should be defined explicitly. Signed-off-by: Nikolay Agishev <agishev@synopsys.com>
Workaround for #72793. Because of pointed issue CONFIG_XIP should be defined explicitly. Signed-off-by: Nikolay Agishev <agishev@synopsys.com>
Workaround for zephyrproject-rtos/zephyr#72793. Because of pointed issue CONFIG_XIP should be defined explicitly. (cherry picked from commit 03b2767) Original-Signed-off-by: Nikolay Agishev <agishev@synopsys.com> GitOrigin-RevId: 03b2767 Change-Id: I0e02c8a30e297765f0aca92f42423e6ab19c9930 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/5588603 Tested-by: Tristan Honscheid <honscheid@google.com> Reviewed-by: Tristan Honscheid <honscheid@google.com> Commit-Queue: Tristan Honscheid <honscheid@google.com> Tested-by: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com>
@nashif I've updated the issue name so it would be more clear. It's not ARC-related (or architecture related) issue, but a regression in Kconfig configuration system introduced with HW model v2. It seems to be that we now handle the For this particular symbol ( |
Describe the bug
After HWMv2 model was applied, build system ignores
config XIP
that configured on SoC level of Kconfig.Synopsys nSIM platforms has following levels of XIP configs:
imply XIP
default n
If XIP configuration is not set on board level explicitly, then 2nd level (SoC-level) config is also skipped. And final configuration is taken from arch-level via
imply XIP
and assigned withXIP=y
value.To Reproduce
Steps to reproduce the behavior:
west build -b nsim/nsim_em samples/hello_world
cat build/zephyr/.config | grep XIP
CONFIG_XIP=y
Expected behavior
CONFIG_XIP=n
in .config file, as config XIP was not explicitly defined on board level. It defined withn
value on SoC level.Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: