Hi,
I debugged the problem further. The PMU firmware, SPL and ATF pass
successfully with warrior branch. ATF sets entry-point at 0x8000000
where I see binary of u-boot.bin. The boot process enter there and stops
somewhere in _binary_u_boot_bin_start. Thus, I suspect problem with
U-Boot relocation. Has anybody experienced similar issue? My
understanding is that U-Boot takes size of RAM memory from device tree
and a board providing 2GB DDR, would have an entry:
memory {
device_type = "memory";
reg = <0x0 0x0 0x0 0x80000000>;
};
correct?
Regards,
Adrian
On 23.10.2019 13:32, Adrian Fiergolski wrote:
>
> Hi,
>
> I am experiencing issue booting a custom board based on ZynqMP+
> device. The boot process stops at ATF:
>
> U-Boot SPL 2019.01 (Oct 23 2019 - 10:34:53 +0000)
> EL Level: EL3
> Trying to boot from MMC2
> NOTICE: ATF running on XCZU6EG/silicon v4/RTL5.1 at 0xfffea000
> NOTICE: BL31: Secure code at 0x0
> NOTICE: BL31: Non secure code at 0x8000000
> NOTICE: BL31: v2.0(release):xilinx-v2019.1
> NOTICE: BL31: Built : 15:12:20, Oct 22 2019
>
> I checked with debugger and apparently, ATF fails to launch u-boot image.
>
> As mu setup, what is reflected properly in the device-tree, uses 2 SD
> controllers, just as a precaution, I applied two patches on PMU (link
> <https://github.com/topic-embedded-products/meta-topic/tree/master/recipes-bsp/pmu-firmware/pmu-firmware>),
> including the one enabling NODE_SD0 for the cores.
>
> Has anybody experienced a similar issue? Can somebody confirm a
> successful run of ZynqMP+ based platform with warrior branch?
>
> Regards,
>
> Adrian
>
--
_______________________________________________
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-xilinx
