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 may give me some clues as to why xilinx-tools does not follow Yocto releases, but can you enlighten me as to why? I am not asking why xilinx-tools does not follow every Yocto release, but why every xilinx-tools release does not use the latest Yocto at the time. Wasn't Sumo available at the time of the 2018.3 release? (I know that this would not have helped our Python problem). Cheers, Geoff. ________________________________ From: Manjukumar Harthikote Matha <[email protected]> Sent: March 20, 2019 1:02:10 PM To: Geoff Gillett; [email protected] Subject: RE: [xilinx-tools] Why does it require Rocko? 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.yoctoproject.org/pipermail/meta-xilinx/2019-February/004250.html Are you witnessing any issue other than device-tree? Thanks, Manju From: [email protected] [mailto:[email protected]] On Behalf Of Geoff Gillett Sent: Wednesday, March 20, 2019 8:53 AM To: [email protected] Subject: [meta-xilinx] [xilinx-tools] Why does it require Rocko? 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.
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
