Hi Michal, > On Jun 20, 2019, at 08:18, Michal Simek <[email protected]> wrote: > > Hi, > > I have not a problem with this. I just retest it on zcu104. > my bootgen version is not capable to work with Image. It should be > Image.bin.
What is different between Image and Image.bin? I could not find the expression in any of the linux/arch/arm64/...Makefiles. Is it just Image renamed to Image.bin and this somehow makes a difference to bootgen? I switched to the Image-mymachine.bin symlink in my DEPLOYDIR and it makes no difference. I also tried loading my DTB at the same address as you, no difference, of course. I am booting on SD, are you? I see two FSBL banners in your pastebin (https://pastebin.com/Um1vmqpc) Xilinx Zynq MP First Stage Boot Loader Release 2019.1 May 24 2019 - 18:30:01 Xilinx Zynq MP First Stage Boot Loader Release 2019.1 May 24 2019 - 18:30:01 PMU Firmware 2019.1 May 24 2019 18:28:19 PMU_ROM Version: xpbr-v8.1.0-0 NOTICE: ATF running on XCZU7EG/EV/silicon v4/RTL5.1 at 0xfffea000 Shooting in the dark here... but is the FSBL copying itself to RAM then restarting? Or did you just copy/pasted two lines by mistake? Could there be some configuration missing from my kernel defconfig perhaps? (I will investigate this now.) Or some bad/missing configuration from our handoff file? I am still using the one generated by vivado 2018.3. Should we align this now to be sure? I will try and build these products for zcu104 then do deep comparisons of config files and generated code. Perhaps if I can swap in my psu_init.c/h I could try and boot it on my board... Anyway thanks for answering my questions. I will really make sure to send in patches for this alternate boot flow. Cheers! -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
