# 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:** 12
**Page:** 1
### Author:  [@keske](https://hub.mender.io/u/keske)
#### Post date: [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/1 "2022-09-21T11:32:27Z")
I am working on a device built around a raspberry pi CM3+ module
after migrating our yocto project from dunfell to kirkstone it is impossible to use u-boot and get a starting device. I have no output on my terminal, and the device is not reachable from outside (which it normally is)
The mender tag we use in the project before migration is dunfell-v2022.04
The required syntax changes for kirkstone have been applied, and the image i am building builds with no errors.
The local.conf used for the image is not changed regarding the mender parts (except for the increased boot partition)
this is an excerpt form the local.conf:
Mender specific changes:
> IMAGE\_INSTALL:append = " kernel-image kernel-devicetree"
> IMAGE\_FSTYPES:remove = " rpi-sdimg"
> VIRTUAL-RUNTIME\_initscripts = “”
> ENABLE\_UART = “1”
> RPI\_USE\_U\_BOOT = “1”
> INHERIT:append = " image-buildinfo mender-full rpi-update-firmware"
> MENDER\_SERVER\_URL = “127.0.0.1”
> MENDER\_FEATURES\_ENABLE:append = " mender-uboot mender-image-sd mender-growfs-data"
> MENDER\_FEATURES\_DISABLE:append = " mender-grub mender-image-uefi"
> MENDER\_ARTIFACT\_NAME = “release-1”
> ARTIFACTIMG\_FSTYPE = “ext4”
> MENDER\_STORAGE\_TOTAL\_SIZE\_MB = “3100”
> MENDER\_BOOT\_PART\_SIZE\_MB = “64”
> MENDER\_DATA\_PART\_SIZE\_MB = “1500”
> MENDER\_ARTIFACT\_EXTRA\_ARGS:append = " --no-default-clears-provides --no-default-software-version --no-checksum-provide"
> SDIMG\_ROOTFS\_TYPE = “ext4”
> IMAGE\_OVERHEAD\_FACTOR = “1.2”
there are no changes to any of the recipes used, and the board starts if I do not issue RPI\_USE\_U\_BOOT = “1” in the local.conf file, and after building change the file cmdline.txt to use /dev/mmcblk0p2 instead of ${mender\_kernel\_root}.
the change in cmdline.txt I made because the dmesg came up with:
waiting for root device ${mender\_kernel\_root} where I think ${mender\_kernel\_root} should have been replaced with the partition that mender indicates as active.
I read the mender kirkstone release notes but could not find any quirks there that indicate u-boot may cause troubles on kirkstone in our project.
I am kind of lost here, so any advice pointing me in the right direction is welcome.
Am I missing some mender variables maybe?
If more information is required regarding the configuration please ask.
---
### Author:  [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)
#### Post date: [September 21, 2022, 2:46pm UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/2 "2022-09-21T14:46:18Z")
Hi @keske,
This might be related to incompatibilites in the rpi firmware. Can you check if [this](https://github.com/mendersoftware/meta-mender/commit/5abe2e7b1f85b3482cb53b747ae9ced3f20a3e73) solves your problem?
Greetz,
Josef
---
### Author:  [@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")
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.
---
### Author:  [@kacf](https://hub.mender.io/u/kacf)
#### Post date: [September 22, 2022, 5:21am UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/4 "2022-09-22T05:21:45Z")
I don’t think the build error is related, we are patching it in the kirkstone branch automatically.
Does it help if you remove `ENABLE_UART = "1"`? Also, is it only upgrade which is broken, or is a fresh device unable to boot as well?
---
### Author:  [@keske](https://hub.mender.io/u/keske)
#### Post date: [September 22, 2022, 8:46am UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/5 "2022-09-22T08:46:53Z")
It is both the fresh install and the update that have this problem. removing ENABLE\_UART = “1” did not solve the problem unfortunately.
---
### Author:  [@keske](https://hub.mender.io/u/keske)
#### Post date: [September 22, 2022, 2:33pm UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/6 "2022-09-22T14:33:47Z")
Building and deploying a bare yocto-built image without mender brings the same results. so I guess it’s a u-boot problem rather than a mender problem.
A core-image-base with RPI\_USE\_U\_BOOT = “1” set, renders a not booting device, without it, it boots…
---
### Author:  [@oleorhagen](https://hub.mender.io/u/oleorhagen)
#### Post date: [October 17, 2022, 6:03am UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/7 "2022-10-17T06:03:01Z")
@keske did they resolve this upstream for you yet?
---
### Author:  [@keske](https://hub.mender.io/u/keske)
#### Post date: [October 17, 2022, 6:24am UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/8 "2022-10-17T06:24:36Z")
@oleorhagen , I don’t know yet. at the moment I am not working on the issue.
When the issue is resolved I will post here as soon as I am working on this again.
---
### Author:  [@dYalib](https://hub.mender.io/u/dYalib)
#### Post date: [August 8, 2023, 7:35am UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/9 "2023-08-08T07:35:11Z")
Hi, i know this is an old topic but since we struggle with the same problem, i will share our solution with you.
We figured out that we had to add the `CONFIG_OF_BOARD=y` parameter to the `u-boot/config/rpi_3_32b_defconfig` file.
You can do this simply with Yoctos patch functionality.
---
### Author:  [@emilm](https://hub.mender.io/u/emilm)
#### Post date: [February 7, 2024, 3:05pm UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/10 "2024-02-07T15:05:02Z")
How can the meta-raspberry pi not have added this if it’s necessary ???
---
### Author:  [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)
#### Post date: [February 9, 2024, 8:10am UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/11 "2024-02-09T08:10:12Z")
I just checked the `u-boot` repository, on `v2022.01` which is the version shipped with `kirkstone`. There, just those are set:
```auto
CONFIG_OF_BOARD_SETUP=y
...
CONFIG_OF_LIBFDT_OVERLAY=y
```
I’m not sure what the correlation is. @leon-anavi, maybe?
Greets,
Josef
---
### Author:  [@leon-anavi](https://hub.mender.io/u/leon-anavi)
#### Post date: [February 9, 2024, 10:57am UTC](https://hub.mender.io/t/migrating-from-yocto-dunfell-to-kirkstone-release-results-in-uboot-not-working-on-raspberrypi-cm3/5268/13 "2024-02-09T10:57:23Z")
> [@TheYoctoJester](#):
>
> v2022.01
Yes, I confirm this is the version shipped with Kirkstone.
This seems related more to U-Boot upstream rather than meta-raspberrypi. Have a look at this discussion in meta-raspberrypi regarding CM3: [Add u-boot defconfig for cm3 · Issue #812 · agherzan/meta-raspberrypi · GitHub](https://github.com/agherzan/meta-raspberrypi/issues/812)