[meta-xilinx] How to boot the ZynqMP?

[Mike Looijmans]

I managed to get it booting with some manual work.

- The meta-xilinx overlay delivers the ATF and PMU firmware.
- My own layer delivers u-boot and kernel and devicetree for my own board

The FSBL I've manually built using Vivado/SDK. The trick to get that working 
was that Vivado version >= 2017.1 was required. It doesn't work (any more) 
with the 2016 versions. I installed 2017.2 and only then the FSBL was able to 
load the PMU and ATF. Apparently there's a dependency there.

So all that is left is to automate the process of generating fsbl and boot.bin.

I'm pretty sure this can be done using just u-boot, since u-boot has support 
for ATF loading and, as I gather from various commits, the PMU as well. It can 
also create a boot.bin without the aid of bootgen. It provides the first-stage 
loader as well.
However, it seems to a well-kept secret how to actually integrate the PMU. I 
can generate a bootloader this way, but I don't know where to put the ATF and 
PMU. I suspect they're to be stored in a FIT image.

So for now I'm stuck with the much less streamlined FSBL flow.


On 22-08-17 20:25, Manjukumar Harthikote Matha wrote:
> Hi Giordon,
> 
> meta-xilinx-tools with xsct in your path would enable the same way , instead 
> of using the Vivado GUI to generate fsbl/pmu/boot.bin
> 
> http://www.wiki.xilinx.com/Using+meta-xilinx-tools+layer
> 

So how does one use this layer to just generate the FSBL and boot.bin?


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: mike.looijmans at topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail