> On Aug 21, 2017, at 04:20, Mike Looijmans <mike.looijm...@topic.nl> wrote: > > > I recall having done this stuff about half a year ago, and at least then I > could create an SPL based loader that actually booted. The layer above looks > like regression to me.
Xilinx "official" support is in FSBL for zynqmp. They removed the SPL zynqmp stuff from their u-boot fork if I am not mistaken. And they configure everything using their own stack including other layers such as meta-linaro and meta-petalinux. > > Current state is that if I generate FSBL using Vivado SDK I can make it load > u-boot by generating a boot.bin containing the FSBL and u-boot.elf. But then > I don't have the PMU firmware and ATF and thus the kernel won't run. Had the same problem. This is because we are hanging on to the old trail (without the extra layers Xilinx wants us to use). > > I tried putting ATF and PMU firmware from the meta-xilinx build into the > boot.bin using the proper attributes, but that results in complete and utter > quiet hangup after power-up. I only see the FSBL start message on the uart. I had to fork a machine from zcu102 in u-boot (so I forked u-boot-xlnx) in my env. Also forked meta-xilinx-tools such that my machine does the same configuration of xilinx-bootbin as zcu102 so the ATF and PMU firmware are bundled inside boot.bin. My fork of u-boot-xlnx/include/configs/xilinx_zynqmp_zcu102.h is where I tie it all together with the right file names for linux image and dtb to match what I have put into the partition using wic, and the default names that yocto uses for those. It was a bit of a hassle, and a annoyance compared to the ease of build of the zynq7 series board, but in the end, learned a lot and am more than ever the master of my domain! ;) Hope this helps a bit. Cheers! /jfd -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
