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

Warning while compiling tests/drivers/build_all/eeprom #83696

Closed
yishai1999 opened this issue Jan 8, 2025 · 2 comments · Fixed by #83739
Closed

Warning while compiling tests/drivers/build_all/eeprom #83696

yishai1999 opened this issue Jan 8, 2025 · 2 comments · Fixed by #83739
Assignees
Labels
area: EEPROM bug The issue is a bug, or the PR is fixing a bug

Comments

@yishai1999
Copy link
Contributor

Describe the bug
When building the tests/drivers/build_all/eeprom application there is a warning (seemingly introduced by #79910) caused by the fact that there are two nodes with the same reg value in tests/drivers/build_all/eeprom/app.overlay (lines 86 and 98).

To Reproduce
west build -b stm32f4_disco zephyr/tests/drivers/build_all/eeprom/

Should also happen on any other board.

Expected behavior

Clean build with no warning.

Impact

Logs and console output

CMake Warning at /home/user/dev/yishai/zephyrproject/zephyr/cmake/modules/dts.cmake:426 (message):
  dtc raised one or more warnings:


  /home/user/dev/yishai/zephyrproject/build/zephyr/zephyr.dts:1058.26-1067.6:
  Warning (unique_unit_address_if_enabled): /test/spi@33334444/at25@0:
  duplicate unit-address (also used in node /test/spi@33334444/mb85rsxx@0)

Call Stack (most recent call first):
  /home/user/dev/yishai/zephyrproject/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  /home/user/dev/yishai/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /home/user/dev/yishai/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:4 (find_package)

Environment (please complete the following information):

  • OS: Linux
  • Toolchain: Zephyr SDK,
  • main branch - commit 52fd016

Additional context

@yishai1999 yishai1999 added the bug The issue is a bug, or the PR is fixing a bug label Jan 8, 2025
Copy link

github-actions bot commented Jan 8, 2025

Hi @yishai1999! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

@yishai1999
Copy link
Contributor Author

@henrikbrixandersen

@henrikbrixandersen henrikbrixandersen self-assigned this Jan 8, 2025
henrikbrixandersen added a commit to vestas-wind-systems/zephyr that referenced this issue Jan 9, 2025
Use unique SPI CS lines in the EEPROM build-all test.

Fixes: zephyrproject-rtos#83696

Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
kartben pushed a commit that referenced this issue Jan 10, 2025
Use unique SPI CS lines in the EEPROM build-all test.

Fixes: #83696

Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
Chenhongren pushed a commit to Chenhongren/zephyr that referenced this issue Jan 22, 2025
Use unique SPI CS lines in the EEPROM build-all test.

(cherry picked from commit 5575158)

Original-Fixes: zephyrproject-rtos#83696
Original-Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
GitOrigin-RevId: 5575158
Cr-Build-Id: 8726087171345732833
Cr-Build-Url: https://cr-buildbucket.appspot.com/build/8726087171345732833
Copybot-Job-Name: zephyr-main-copybot-downstream
Change-Id: Ie2330b511696aa9d4caa94ca53a2f43859b589f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/zephyr/+/6169112
Commit-Queue: Keith Short <keithshort@chromium.org>
Tested-by: ChromeOS Prod (Robot) <chromeos-ci-prod@chromeos-bot.iam.gserviceaccount.com>
Tested-by: Keith Short <keithshort@chromium.org>
Reviewed-by: Jonathon Murphy <jpmurphy@google.com>
Reviewed-by: Keith Short <keithshort@chromium.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: EEPROM bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants