Closed ghost closed 4 years ago
Starting with 2019.2 (which one was appended on top of poky/oe/xilinx-bsp thud versions), recipes parsing to build an image for zcu102-zynmp fails on:
Nothing PROVIDES 'bootgen-native' … Required by /xilinx-bootbin_1.0
CONF_VERSION = "1" MACHINE = "zcu102-zynqmp" LICENSE_FLAGS_WHITELIST+="xilinx" #PREFERRED_PROVIDER_virtual/pmu-firmware = "pmu-firmware" PREFERRED_PROVIDER_virtual/boot-bin = "xilinx-bootbin" #PREFERRED_PROVIDER_virtual/dtb = "device-tree" #PREFERRED_PROVIDER_virtual/pmu-firmware = "zynqmp-pmu-pmu-firmware" IMAGE_INSTALL_append=" xilinx-bootbin" BIF_PARTITION_ATTR= "fsbl pmu atf u-boot" BIF_PARTITION_ATTR[fsbl]="bootloader, destination_cpu=a53-0" BIF_PARTITION_IMAGE[fsbl]="${DEPLOY_DIR_IMAGE}/fsbl-${MACHINE}.elf" BIF_PARTITION_DEPENDS[fsbl]="virtual/fsbl:do_deploy" BIF_PARTITION_ATTR[pmu]="destination_cpu=pmu" BIF_PARTITION_IMAGE[pmu]="${DEPLOY_DIR_IMAGE}/pmu-firmware-${MACHINE}.elf" BIF_PARTITION_DEPENDS[pmu] ?= "virtual/pmu-firmware:do_deploy"
Despite what the README file states, the entry
PREFERRED_PROVIDER_virtual/boot-bin = "xilinx-bootbin"
should be included in addition to :
IMAGE_INSTALL_append=" xilinx-bootbin"
The boot-gen tool do not come anymore from the XSCT tarball ?
boot-gen
see https://lists.yoctoproject.org/g/meta-xilinx/message/4673
Since this release, the meta-layer is only compliant with rel-v* branches of meta-xilinx-bsp. This should be noticed into the README.
rel-v*
meta-xilinx-bsp
Starting with 2019.2 (which one was appended on top of poky/oe/xilinx-bsp thud versions), recipes parsing to build an image for zcu102-zynmp fails on:
Nothing PROVIDES 'bootgen-native' … Required by /xilinx-bootbin_1.0
Despite what the README file states, the entry
PREFERRED_PROVIDER_virtual/boot-bin = "xilinx-bootbin"
should be included in addition to :
IMAGE_INSTALL_append=" xilinx-bootbin"
The
boot-gen
tool do not come anymore from the XSCT tarball ?