On 22-08-17 02:25, Jean-Francois Dagenais wrote:
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: [email protected]
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
On Aug 21, 2017, at 04:20, Mike Looijmans <[email protected]> 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.
I'm not sure they removed it, the u-boot-xlnx fork is about 8 months behind on
mainline u-boot.
Stangely, the mainline version has SPL support, an I actually can get the
board to boot with SPL. But I can't figure out how to make it load PMU and ATF.
There have been dozens of commits from Xilinx to support the zynqmp in u-boot
mainline. None of these are in the Xilnx fork, so I assumed that Xilinx had
seen the light... Apparently the opposite is true.
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! ;)
At least now I understand why there's so little interest in the MPSOC. The
licensing alone is a nightmare.
--
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx
