No valid device tree binary found - after added meta-xilix-tools layer.

[jiin995]

Hello, we have a problem with this layer. We use poky zeus and after we configure bblayers.conf and local.conf as described below, when booting the target system (zybo-zynq7) on serial we see this error:

No valid device tree binary found - please append one to U-Boot binary, use u-boot-dtb.bin or define CONFIG_OF_EMBED. For sandbox, use -d <file.dtb>
initcall sequence 04063390 failed at call 04058b00 (err=-1)
### ERROR ### Please RESET the board ###

bblayers.conf

BBLAYERS ?= " \
  /home/se/yocto/test_from_0/poky-zues/meta \
  /home/se/yocto/test_from_0/poky-zues/meta-poky \
  /home/se/yocto/test_from_0/poky-zues/meta-yocto-bsp \
  /home/se/yocto/test_from_0/poky-zues/meta-openembedded/meta-python \
  /home/se/yocto/test_from_0/poky-zues/meta-openembedded/meta-oe\
  /home/se/yocto/test_from_0/poky-zues/meta-xilinx/meta-xilinx-bsp \
  /home/se/yocto/test_from_0/poky-zues/meta-xilinx/meta-xilinx-contrib \
  /home/se/yocto/test_from_0/poky-zues/meta-xilinx/meta-xilinx-standalone \
  /home/se/yocto/test_from_0/poky-zues/meta-xilinx-tools \
"

local.conf

#Top is default file except for MACHINE that is configured for build on zybo-zynq7

HDF_BASE = "file://"
HDF_PATH = "/home/se/yocto/test_from_0/poky-zues/zybo/gpio.xsa"
XSCT_STAGING_DIR="/home/se/yocto/poky-zeus/zynq/xsct"

XILINX_VER_MAIN="2020.1"
PREFERRED_PROVIDER_virtual/boot-bin="xilinx-bootbin"

IMAGE_INSTALL_append = " xilinx-bootbin" 
BIF_PARTITION_ATTR= "fsbl bitstream u-boot"
BIF_PARTITION_ATTR[fsbl]="bootloader"
BIF_PARTITION_IMAGE[fsbl]="${DEPLOY_DIR_IMAGE}/fsbl-${MACHINE}.elf"
BIF_PARTITION_DEPENDS[fsbl]="virtual/fsbl:do_deploy"
BIF_PARTITION_IMAGE[bitstream]="${DEPLOY_DIR_IMAGE}/download-${MACHINE}.bit"
BIF_PARTITION_IMAGE[u-boot]="${DEPLOY_DIR_IMAGE}/u-boot-${MACHINE}.elf"
BIF_PARTITION_DEPENDS[u-boot]="virtual/bootloader:do_deploy"

We tried to change xsa but the results is the same.

[embed-me]

I also used the zybo-zynq7 machine, 2020.1 and zeus as a starting point for a custom board development. Run into the same issue, however, adding CONFIG_OF_EMBED=y to the corresponding u-boot defconfig fixed it for me.