# Migrating from yocto dunfell to kirkstone release results in uboot not working on Raspberrypi CM3

**URL:** <https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268>\
**Category:** Yocto Project\
**Tags:** raspberrypi-cm3, uboot, kirkstone\
**Created:** [September 21, 2022, 11:32am UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268 "2022-09-21T11:32:27Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![keske](https://avatars.discourse-cdn.com/v4/letter/k/94ad74/32.png) [@keske](https://hub.mender.io/u/keske)\
**Post date:** [September 21, 2022, 5:07pm UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/3 "2022-09-21T17:07:23Z")

</div>

Hi @TheYoctoJester,

in the local conf I already have the line:  
INHERIT:append = " image-buildinfo mender-full rpi-update-firmware"  
and I also tried a build without this script. With the same result.

I suspect it is more the incompatibility issue of mender client (v3.3.0) with kirkstone that plays it’s fiddle.  
(I read about that in [Mender-client fails to build on kirkstone for qemux86-64](https://hub.mender.io/t/mender-client-fails-to-build-on-kirkstone-for-qemux86-64/5072))  
I don’t get build errors however.  
I will look into the patch mentioned in that thread tomorrow, to see if it makes a difference.

---

_[View the full topic](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268)._