[meta-xilinx] rel-v2018.1 / zcu102-zynqmp: U-boot crashes with error "fdt_root: FDT_ERR_BADMAGIC"

Martin Lund malu at gomspace.com
Mon Apr 30 07:27:37 PDT 2018


The problem seems to be that u-boot has been upgraded to v2018.1 which introduces changes to how the ATF is booted and that has somehow broken the boot procedure.


I notice that a new CONFIG_SPL_ATF config option has been introduced in u-boot specifically to boot u-boot via ATF but it is not enabled in the xilinx_zynqmp_zcu102_rev1_0_defconfig so perhaps it is not a feature that should be used?


I remember that the old u-boot SPL is tricked to boot linux when in reality it is loading ATF. I believe this is why I'm now seeing an invalid FDT - the FDT is somehow not loaded correctly due to changes in u-boot's boot implementation after the upgrade.


I tried disabling CONFIG_SPL_OS_BOOT and enabling CONFIG_SPL_ATF. Then the SPL is looking for u-boot.img from the SD card but it seems that core-image-minimal only produces u-boot.bin?


I'm just looking for a combination that works so that I can build a stock meta-xilinx rel-v2018.1 for czu102-zynqmp that can actually boot from SD card.

Running into these basic issues makes me wonder if I'm he first to actually test the rel-v2018.1 release with the zcu102-zynqmp board?


________________________________
From: Martin Lund
Sent: Monday, April 30, 2018 1:14 PM
To: meta-xilinx at yoctoproject.org
Subject: rel-v2018.1 / zcu102-zynqmp: U-boot crashes with error "fdt_root: FDT_ERR_BADMAGIC"

Building and running core-image-minimal for the zcu102-zynqmp machine on the recently released rel-v2018.1 branch results in u-boot crashing with the following error:

fdt_root: FDT_ERR_BADMAGIC


Boot files are installed on the SD card following the normal guildelines - first partition (BOOT, vfat) is populated with the following files:

atf-uboot.ub
boot.bin
Image
Image-zynqmp-zcu102-rev1.0.dtb
u-boot.bin
uEnv.txt

We've seen the same error on two rel-2018.1 builds from two different build hosts.

Any ideas what might cause the .dtb / fdt to become broken like that?

Perhaps a broken dtc toolchain?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20180430/940090fa/attachment.html>


More information about the meta-xilinx mailing list