# RPi 5 rev 1.1 stuck on uboot logo

**URL:** <https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003>\
**Category:** General Discussions\
**Created:** [September 17, 2025, 9:51pm UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003 "2025-09-17T21:51:52Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![swapnil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/swapnil/32/2563_2.png) [@swapnil](https://hub.mender.io/u/swapnil)\
**Post date:** [September 17, 2025, 9:51pm UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/1 "2025-09-17T21:51:52Z")

</div>

I am trying to build an image on a new Raspberry Pi 5 Model B Rev 1.1. But after using mender-convert and flashing the image on the SD card, the RPi is stuck on the U-Boot logo

The same image works with both Raspberry Pi 5 Model B Rev 1.0 and Raspberry Pi 4

used this to create the mender image

```auto
MENDER_ARTIFACT_NAME=release-1 ./docker-mender-convert \
    --disk-image input/2025-05-13-raspios-bookworm-arm64-lite.img \
    --config configs/raspberrypi/uboot/debian/raspberrypi5_bookworm_64bit_config \
    --overlay input/rootfs_overlay_demo/

```

Can someone help me get this working?

Thanks!

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [September 18, 2025, 7:14am UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/2 "2025-09-18T07:14:30Z")

</div>

Hi @swapnil,

Thanks for reaching out! Concerning the 1.1 Rev, it needs the D0 DTB to be added to the overlays. Can you check if it is present? See the corresponding fix in Yocto at [Merge pull request #413 from TheYoctoJester/scarthgap\_rpi5\_d0 · mendersoftware/meta-mender-community@559e5c1 · GitHub](https://github.com/mendersoftware/meta-mender-community/commit/559e5c157625429333079aa41b48b041219206ec)

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![swapnil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/swapnil/32/2563_2.png) [@swapnil](https://hub.mender.io/u/swapnil)\
**Post date:** [September 18, 2025, 7:39pm UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/3 "2025-09-18T19:39:08Z")

</div>

Thanks for the comment! I had to look up, but the overlays/bcm2712d0.dtbo is present.  
While debugging the above, I removed the following in config.txt:

```auto
[all]
kernel=kernel8.img

```

Or modified it to:

```auto
[all]
kernel=kernel_2712.img

```

On the flashed SD card. In either case, it uses kernel\_2712.img to boot, and I am no longer getting stuck on the U-Boot logo.

However, now I am facing another issue where the ${mender\_kernel\_root} in cmdline.txt isn’t being resolved. Here is my cmdline.txt:

```auto
console=serial0,115200 console=tty1 root=${mender_kernel_root} rootfstype=ext4 fsck.repair=yes rootwait init=/usr/lib/raspberrypi-sys-mods/firstboot cfg80211.ieee80211_regdom=US

```

And the error on screen:

```auto
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount... Begin: Resizing root filesystem...\n\nDepending on storage size and speed, this may take a while.... lsblk: ${mender_kernel_root}: not a block device 
done.
Begin: Will now check root file system... fsck from util-linux 2.38.1
Checking all file systems.
done.
3.302873] ${mender_kernel_root}: Can't lookup blockdev
mount: mounting ${mender kernel_root} on /root failed: No such file or directory 
Failed to mount ${mender_kernel_root} as root file system.

```

Modifying to `root=/dev/mmcblk0p2` in cmdline.txt works, but this will break the rootfs updates. Any help or suggestions on how to fix this? Thanks!

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [September 19, 2025, 6:41am UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/4 "2025-09-19T06:41:37Z")

</div>

Hi @swapnil,

Not surprising you’re not getting stuck with `u-boot` anymore and that the Mender integration isn’t working anymore, because with

```auto
[all]
kernel=kernel_2712.img

```

you essentially skip `u-boot`.😬

As said, the question rather is why `u-boot` gets stuck. Do you have a serial debug terminal? What do you see there when stuck?

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![swapnil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/swapnil/32/2563_2.png) [@swapnil](https://hub.mender.io/u/swapnil)\
**Post date:** [September 19, 2025, 12:12pm UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/5 "2025-09-19T12:12:34Z")

</div>

I suspected that this was happening since overriding the RASPBERRYPI\_KERNEL\_IMAGE to kernel\_2712.img was also causing the RPI to get stuck at the U-Boot logo. When the RPI gets stuck at the U-Boot logo, I am unable to see any logs on the serial console.

---

<div class="post-metadata">

**Author:** ![adrian](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/adrian/32/2688_2.png) [@adrian](https://hub.mender.io/u/adrian)\
**Post date:** [September 29, 2025, 3:49pm UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/6 "2025-09-29T15:49:15Z")

</div>

Hi @swapnil ,

I ran into the same issue when I tried to convert an image for the RevPi 5.

The only way I have found so far to get around it is to disable UART by changing enable\_uart=1 to 0 in the config.txt on the firmware partition. I read somewhere that UBOOT gets stuck if anything is transmitting via UART during boot, which some of the Kunbus devices seem to do.  
Unfortunately, that approach seems to break a lot of functionality (including login…). Hope you’ll have more luck than I did 🙂

Greetings  
Martin

---

<div class="post-metadata">

**Author:** ![swapnil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/swapnil/32/2563_2.png) [@swapnil](https://hub.mender.io/u/swapnil)\
**Post date:** [September 30, 2025, 8:17pm UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/7 "2025-09-30T20:17:32Z")

</div>

Thanks, @adrian! That seems to be working for the RPi 5.

However, it breaks the boot process on the RPi 4. I’m trying to understand this, as per the documentation at [mender-convert/configs/raspberrypi/uboot/include/common\_config at bc63c51ce683e7787aa541018443d9f577dcd540 · mendersoftware/mender-convert · GitHub](https://github.com/mendersoftware/mender-convert/blob/bc63c51ce683e7787aa541018443d9f577dcd540/configs/raspberrypi/uboot/include/common_config#L67), where it states that UART is required for U-Boot to operate correctly.

I’m trying to determine if it’s possible to use the same image for both the RPi 4 and RPi 5. I also want to know what could break if the UART is disabled, and if there are any permanent solutions.

---

<div class="post-metadata">

**Author:** ![swapnil](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/swapnil/32/2563_2.png) [@swapnil](https://hub.mender.io/u/swapnil)\
**Post date:** [October 2, 2025, 2:55pm UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/8 "2025-10-02T14:55:57Z")

</div>

For now, I am using this in config.txt

```auto
[pi4]
enable_uart=1

[pi5]
enable_uart=0

```

Still trying to understand if disabling UART breaks anything [mender-convert/configs/raspberrypi/uboot/include/common\_config at bc63c51ce683e7787aa541018443d9f577dcd540 · mendersoftware/mender-convert · GitHub](https://github.com/mendersoftware/mender-convert/blob/bc63c51ce683e7787aa541018443d9f577dcd540/configs/raspberrypi/uboot/include/common_config#L67), where it states that UART is required for U-Boot to operate correctly.

---

<div class="post-metadata">

**Author:** ![mosci](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mosci/32/2655_2.png) [@mosci](https://hub.mender.io/u/mosci)\
**Post date:** [February 15, 2026, 6:27pm UTC](https://hub.mender.io/t/rpi-5-rev-1-1-stuck-on-uboot-logo/8003/9 "2026-02-15T18:27:42Z")

</div>

I ran into that problem yesterday, while getting my cm5  
up and running.  
The problem was in the boot.scr, which loads the bootargs from the cmdline.txt, before executing mender\_setup and then never writes them back …  
so still ${mender\_kernel\_root} is used instead of the interpolated version.  
the fix is to write a new boot.cmd and make an boot.scr from it.

here’s mine, if you wanna give it a try …  
content of boot.cmd:

fdt addr ${fdt\_addr}  
fdt move ${fdt\_addr} ${fdt\_addr\_r}  
fdt get value bootargs /chosen bootargs  
run mender\_setup  
setenv bootargs “${bootargs}”  
mmc dev ${mender\_uboot\_dev}  
mw.w ${kernel\_addr\_r} 0x8b1f  
if load ${mender\_uboot\_root} ${ramdisk\_addr\_r} /boot/vmlinuz; then  
if cmp.w ${kernel\_addr\_r} ${ramdisk\_addr\_r} 1; then  
echo “Decompressing kernel…”  
unzip ${ramdisk\_addr\_r} ${kernel\_addr\_r}  
else  
echo “Copying kernel…”  
cp.b ${ramdisk\_addr\_r} ${kernel\_addr\_r} ${filesize}  
fi  
if load ${mender\_uboot\_root} ${ramdisk\_addr\_r} /boot/initrd.img; then  
setenv ramdisk\_param “${ramdisk\_addr\_r}:${filesize}”  
else  
setenv ramdisk\_param “-”  
fi  
booti ${kernel\_addr\_r} ${ramdisk\_param} ${fdt\_addr\_r}  
fi  
run mender\_try\_to\_recover

and that’s how to make a boot.scr from it, which needs to get placed next to the u-boot.bin (boot partition)  
mkimage -A arm64 -T script -C none -n “Boot script” -d boot.cmd boot.scr