# \[INCOMPLETE\] Xilinx Zynq 7000

**URL:** https://hub.mender.io/t/incomplete-xilinx-zynq-7000/669
**Category:** Yocto Project
**Created:** [June 5, 2019, 10:58pm UTC](https://hub.mender.io/t/incomplete-xilinx-zynq-7000/669 "2019-06-05T22:58:46Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![brymat](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/brymat/32/271_2.png) [@brymat](https://hub.mender.io/u/brymat)
#### Post date: [June 7, 2019, 2:57pm UTC](https://hub.mender.io/t/incomplete-xilinx-zynq-7000/669/3 "2019-06-07T14:57:32Z")

</div>

Thanks for the feedback, I will incorporate those suggestions as I work through a few other details.

Regarding Petalinux, it really is quite an invasive tool set. Unlike the one you suggested, [kas](https://github.com/siemens/kas), Petalinux almost tries to completely mask Yocto and bitbake. So the command `petalinux-config` actually generates it’s own config files which are then used to generate input files to bitbake when you run `petalinux-build`. This is one of the main [reasons](https://hub.mender.io/t/interest-in-a-xilinx-zynq-board-integration/662/2) for the suggestion to avoid Petalinux.

I am realizing my instructions above do require some knowledge of Petalinux to make it work. I will try add more details to the setup to make that a bit easier.

---

_[View the full topic](https://hub.mender.io/t/incomplete-xilinx-zynq-7000/669)._