# Build PYNQ OS for ZCU102 with Yocto

**URL:** <https://discuss.pynq.io/t/build-pynq-os-for-zcu102-with-yocto/2537>\
**Category:** Support\
**Created:** [April 12, 2021, 4:21pm UTC](https://discuss.pynq.io/t/build-pynq-os-for-zcu102-with-yocto/2537 "2021-04-12T16:21:55Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![PeterOgden](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/peterogden/32/55_2.png) [@PeterOgden](https://discuss.pynq.io/u/PeterOgden)\
**Post date:** [May 5, 2021, 1:42pm UTC](https://discuss.pynq.io/t/build-pynq-os-for-zcu102-with-yocto/2537/21 "2021-05-05T13:42:18Z")

</div>

This most like means that the UIO driver isn’t configured to bind to the device. There are a couple of ways to do this. Easiest way is to add `uio_pdrv_genirq.of_id=generic-uio` to the kernel command line. If the UIO device is compiled as a module you can also add a file containing `options uio_pdrv_genirq of_id=generic-uio` to /etc/modprobe.d and then `modprobe uio_pdrv_genirq`.

Peter

---

_[View the full topic](https://discuss.pynq.io/t/build-pynq-os-for-zcu102-with-yocto/2537)._