[meta-xilinx] [xilinx-tools] Why does it require Rocko?

[Geoff Gillett]

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 embedded nodes. This would enable our science teams  to create not only the science package but the embedded instrumentation and control without detailed expertise in embedded Linux or HDL.


Our issue is we would like to track the Python releases, Yocto appears to have fixed the issues it had with Python tracking in the Thud release, but xilinx-tools appears to be stuck at Rocko.


We wonder what underlying problems are causing this?  We would like to investigate fixing it, first we would need to know what the issues are.


My understanding is:

  *   Yocto is a build system based on layers of recipes that construct components.
  *   xilinx-tools is a layer of recipes for building the device-tree and other BSP components using Xilinx's proprietary tools.

What I don't understand is why the recipes in xilinx-tools can't be handled by more recent versions of Yocto.

Does xilinx-tools work with more recent Yocto versions than Rocko?
I have a basic version of a build system working based on the 2018.3 Xilinx releases but have not tried upgrading Yocto/openembedded versions.

Cheers,
Geoff Gillett.
Senior Scientist, Quantum Valley Ideas Laboratories.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-xilinx/attachments/20190320/05c42238/attachment.html>