Skip to content

DT: error in generated_dts_board_fixups.h for board: frdm_k64f #13243

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

Closed
jakub-uC opened this issue Feb 11, 2019 · 4 comments
Closed

DT: error in generated_dts_board_fixups.h for board: frdm_k64f #13243

jakub-uC opened this issue Feb 11, 2019 · 4 comments
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug platform: NXP NXP priority: low Low impact/importance bug
Milestone

Comments

@jakub-uC
Copy link
Collaborator

It is not possible to build application:
~/zephyr/zephyr/tests/net/all
for frdm_k64f board.

  1. Go to ~/zephyr/zephyr/tests/net/all
  2. mkdir b && cd b
  3. cmake -GNinja -DBOARD=frdm_k64f ..
  4. ninja
  5. See error

Expected behavior
Project will compile

Impact
It is not possible to build this test for frdm_k64f board. In my opinion it is serious.

Environment (please complete the following information):

  • OS: Linux
  • Zephyr SDK
  • Commit SHA or Version used: acaae57 (the newest master)

Screenshots or console output

dt error

Additional context
I can build it without any error for nrf52840_pca10056 board.

@jakub-uC jakub-uC added the bug The issue is a bug, or the PR is fixing a bug label Feb 11, 2019
@galak galak added the platform: NXP NXP label Feb 11, 2019
@galak galak added this to the v1.14.0 milestone Feb 11, 2019
@galak
Copy link
Collaborator

galak commented Feb 11, 2019

The issue is that the build isn't valid on frdm-k64f as defined by default. It enables bluetooth, but there is no bluetooth controller. BT_UART is enabled and expects that zephyr,bt-uart is defined in the dts, but since the based frdm-k64f doesn't have bt, that isn't set. Thus the build errors.

@pfalcon pfalcon changed the title DT: error in generated_dts_board_fixups.h for board: frmd_k64f DT: error in generated_dts_board_fixups.h for board: frdm_k64f Feb 11, 2019
@MaureenHelm
Copy link
Member

MaureenHelm commented Feb 11, 2019

Is this purely a build test or is it supposed to do something at runtime? If it's just a build test, then you can build it like this:

$ cmake -DBOARD=frdm_k64f -DSHIELD=frdm_kw41z ..
$ make

It won't work at runtime because there is a pin conflict between Ethernet and BT UART.

@agansari
Copy link
Collaborator

agansari commented Feb 12, 2019

This issue will arise on any board without Bluetooth on board/soc that requires an external shield, not just K64F.
To fix this we can add something like the following:

diff --git a/tests/net/all/CMakeLists.txt b/tests/net/all/CMakeLists.txt
index 4491e40bd9..6a5aaddde3 100644
--- a/tests/net/all/CMakeLists.txt
+++ b/tests/net/all/CMakeLists.txt
@@ -1,4 +1,9 @@
 cmake_minimum_required(VERSION 3.13.1)
+
+if ((BOARD STREQUAL "frdm_k64f") OR (BOARD STREQUAL "mimxrt1050_evk"))
+    set(SHIELD frdm_kw41z)
+endif()
+
 include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)
 project(all)

But as @MaureenHelm asked, is this a build test?
If yes, then the change above will fix it.
If no, then you need a particular HW setup described here: https://docs.zephyrproject.org/latest/boards/shields/frdm_kw41z/doc/index.html

I expect boards without BT but have arduino-i2c dts nodes to request x_nucleo* shields.

@nashif nashif added the priority: low Low impact/importance bug label Feb 12, 2019
@nashif
Copy link
Member

nashif commented Feb 19, 2019

This is a build test only, the testcase.yaml says it:

  platform_whitelist: qemu_x86```

@nashif nashif closed this as completed Feb 19, 2019
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 platform: NXP NXP priority: low Low impact/importance bug
Projects
None yet
Development

No branches or pull requests

5 participants