Hi Mike,
We tested by loading both the vivado generated and bootgen generated
bitstreams using 2018.3 and it worked fine, we are able to see Done and leds
glowing as per our design.
Is it a custom board or zcu102?
Do you need this patch on thud?
https://github.com/Xilinx/meta-xilinx/comm
Hi Geoff,
The only needed patch for Thud is the devicetree patch, which we had sent as
RFC. Meta-xilinx-tools currently does not follow Yocto releases at this point
of time, it is following Vivado release hence it is approx. 4months behind
Yocto release.
RFC patch is here:
https://lists.yoctop
Hi Manju,
Thanks for the clear explaination.
Cheers,
Geoff.
From: Manjukumar Harthikote Matha
Sent: March 20, 2019 1:36:09 PM
To: Geoff Gillett; meta-xilinx@yoctoproject.org
Subject: RE: [xilinx-tools] Why does it require Rocko?
Hi Geoff,
Historically this
Hi Christian,
I don't think the clock is the error here (mostly a red-herring). If you
look at the recipe that Emily is excluding (init-clock) -- it's an
update-rc.d recipe meaning it's installing itself to run on linux boot --
and it's a python script.
Strangely, including it seems to cause the
For the clock tree configuration, in my projects, I use the Vivado
configuration tool, , and then generates the psu_init_gpl files. It's static,
but it fits my needs and I don't know if there is any other solution (it's the
only one advertised in the Xilinx documentation I read). Actually, in my
Hi Manju,
Thank you for the quick useful response.
I have not tried to upgrade my basic build system yet but will give the patch a
try and get back to the list if any problems arise. This would fix our current
problems by allowing us to use Python3.7 which is good news.
I guess the patch ma
Hi,
We are a new applied science lab using Zynq's to embed our data acquisition and
control systems. We find the ability to use the xilinx-tools layer very useful
as it allows non HDL experts to configure hardware through the Vivado block
diagram, then Yocto builds the custom OS for our embedd
