Move the appropriate backend code for the ZynqMP FPGA configuration from the
interface subdirectory of the xilfpga library into the src directory so that
the files are picked up by the Makefile. Otherwise the FPGA configuration code
is non-functional.
Signed-off-by: Andreas Galauner
Hi all,
I just tried the current version of meta-xilinx on my Ultrazed and found
that FPGA configuration didn't work. I tried Linux and u-boot and got
failures all the time.
I then built a PMU firmware using the Xilinx SDK which worked to my
surprise. After a lot of diffing which didn't yield
On 31.07.2018 23:30, Manjukumar Harthikote Matha wrote:
> Can you submit the patch to u-boot mainline?
I just sent out the patch email.
- Andy
--
___
meta-xilinx mailing list
meta-xilinx@yoctoproject.org
pstream that. The
u-boot is just broken on Picozeds without this.
- Andy
commit 3115e00df2fc969becff15811c5ff5feb0ecd036
Author: Andreas Galauner
Date: Sat Nov 25 06:37:25 2017 +0100
Fix picozed device tree
diff --git a/arch/arm/dts/zynq-picozed.dts b/arch/arm/dts/zynq-picozed.dts
index e15667c10
p/fit_spl_atf.its
new file mode 100644
index 00..d8850eb248
--- /dev/null
+++ b/board/xilinx/zynqmp/fit_spl_atf.its
@@ -0,0 +1,54 @@
+/*
+ * Copyright (C) 2017 Theobroma Systems Design und Consulting GmbH
+ * Copyright (C) 2018 Andreas Galauner <andr...@galauner.de>
+ *
+ * Min
On 04.05.2018 21:25, Andreas Galauner wrote:
> It seems that it expects a FIT image there.
>
> If somebody knows how to use this, any help would be great.
> Ideally I'd like to have it boot a FIT image containing the BL31, BL32
> (I'd try to hack support into u-boot for this once
On 01.05.2018 11:05, Martin Lund wrote:
> Hi Manju,
>
>
> Ok, I've updated u-boot-mkimage to use the 2018.1 recipe from
> meta-petalinux by copying the files to the meta-xilinx layer.
>
>
> Then when building arm-trusted-firmware it triggered a rebuild to update
> u-boot-mkimage which resulted
This change enables three more Xilinx ZynqMP driver in the linux-xlnx kernel:
* Common Clock Infrastructure
* NVMem firmware support
* Reset controller
The Common Clock Infrastructure is needed for newer device trees which use it,
otherwise the kernel doesn't boot
The NVMem firmware
This change enables three more Xilinx ZynqMP driver in the linux-xlnx kernel:
* Common Clock Infrastructure
* NVMem firmware support
* Reset controller
The Common Clock Infrastructure is needed for newer device trees which use it,
otherwise the kernel doesn't boot
The NVMem firmware
