Hi Chris,
Which boot mode are you using? I usually use JTAG and SD boot mode with
Yocto built image and boot.bin works as expected on our eval boards.
$ cat
./zcu111_zynqmp-xilinx-linux/xilinx-bootbin/1.0-r0/xilinx-bootbin-1.0/bootgen.bif
the_ROM_image:
{
[bootloader, destination_cpu=a53-0]
/tmp/sandeepg/yocto/2022.2/build-zynqmp/work/zcu111_zynqmp-xilinx-linux/xilinx-bootbin/1.0-r0/recipe-sysroot/boot/fsbl.elf
[destination_cpu=pmu]
/tmp/sandeepg/yocto/2022.2/build-zynqmp/work/zcu111_zynqmp-xilinx-linux/xilinx-bootbin/1.0-r0/recipe-sysroot/boot/pmufw.elf
[destination_device=pl]
/tmp/sandeepg/yocto/2022.2/build-zynqmp/deploy/images/zcu111-zynqmp/download-zcu111-zynqmp.bit
[destination_cpu=a53-0, exception_level=el-3, trustzone]
/tmp/sandeepg/yocto/2022.2/build-zynqmp/work/zcu111_zynqmp-xilinx-linux/xilinx-bootbin/1.0-r0/recipe-sysroot/boot/arm-trusted-firmware.elf
[destination_cpu=a53-0, load=0x100000]
/tmp/sandeepg/yocto/2022.2/build-zynqmp/work/zcu111_zynqmp-xilinx-linux/xilinx-bootbin/1.0-r0/recipe-sysroot/boot/devicetree/system-top.dtb
[destination_cpu=a53-0, exception_level=el-2]
/tmp/sandeepg/yocto/2022.2/build-zynqmp/work/zcu111_zynqmp-xilinx-linux/xilinx-bootbin/1.0-r0/recipe-sysroot/boot/u-boot.elf
}
$
We can make these changes and run the test.
Thanks,
Sandeep
On 4/7/2023 1:34 PM, Chris Laplante via lists.yoctoproject.org wrote:
Hi Mark,
Contrast this to meta-xilinx (2022.2) which uses the FSBL method. We
noticed that when building BOOT.BIN using PetaLinux, everything works
fine. When using Yocto, we end up with PS_ERROR_OUT asserting and our
red LED turning on. (This is a custom board).
I don't know much about this. The best I can say is that Yocto Project
integration doesn't support the bootgen method (CBR) that has to do with
secure booting. You need a different bootgen then what we have integrated
for secure boot. PetaLinux constructs files externally of the Yocto Project
configuration with external helpers that know about secure configurations and
other things.
(Sorry I don't understand much of this, only the basic BIF and bootgen calling
as implemented.)
(see below)
Can you share these patches? I'd like to see how invasive they are and if they
require any components that are not part of the regular Yocto Project
integrations.
I only had to change one line - patch is below. It *did* actually work with the
bootgen provided by meta-xilinx/meta-xilinx-tools.
I also don't fully understand any of this, but I don't think secure boot is
involved here. My understanding of PMU FW boot methods is that the only
difference between CBR and FSBL is that the former tacks the PMU FW onto the
end of the FSBL, whereas the latter includes the PMU FW as a separate image in
the BOOT.BIN.
Thanks,
Chris
diff --git a/meta-xilinx-core/recipes-bsp/bootbin/machine-xilinx-zynqmp.inc
b/meta-xilinx-core/recipes-bsp/bootbin/machine-xilinx-zynqmp.inc
index c5c4e385..748bcfdd 100644
--- a/meta-xilinx-core/recipes-bsp/bootbin/machine-xilinx-zynqmp.inc
+++ b/meta-xilinx-core/recipes-bsp/bootbin/machine-xilinx-zynqmp.inc
@@ -29,7 +29,7 @@ BIF_PARTITION_IMAGE[fsbl] ?= "${RECIPE_SYSROOT}/boot/fsbl.elf"
# specify BIF partition attributes for PMU Firmware
# destination cpu for PMU. Location where PMU binary is present and
dependency to build PMU Firmware
-BIF_PARTITION_ATTR[pmufw] ?= "destination_cpu=pmu"
+BIF_PARTITION_ATTR[pmufw] ?= "pmufw_image"
BIF_PARTITION_IMAGE[pmufw] ?= "${RECIPE_SYSROOT}/boot/pmufw.elf"
# specify BIF partition attributes for ATF
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5212):
https://lists.yoctoproject.org/g/meta-xilinx/message/5212
Mute This Topic: https://lists.yoctoproject.org/mt/98128052/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
