# Update from bullseye 32bit to trixie 64bit?

**URL:** <https://hub.mender.io/t/update-from-bullseye-32bit-to-trixie-64bit/8116>\
**Category:** Debian family\
**Created:** [November 25, 2025, 1:51pm UTC](https://hub.mender.io/t/update-from-bullseye-32bit-to-trixie-64bit/8116 "2025-11-25T13:51:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [November 27, 2025, 2:22pm UTC](https://hub.mender.io/t/update-from-bullseye-32bit-to-trixie-64bit/8116/2 "2025-11-27T14:22:50Z")

</div>

Hi @user706,

Thanks for reaching out!

So for question 1, this is just the generic compatibility check kicking in. By default, the `device_type` string for 32bit is `raspberrypi4` on the RPi4, and on 64bit it is `raspberrypi4-64` or `raspberrypi4_64`, depending on if you’re using `mender-convert` or Yocto to create the image. By setting [`MENDER_DEVICE_TYPE`](https://docs.mender.io/operating-system-updates-debian-family/variables#mender_device_type) accordingly, you can make this match easily.

Question 2 is more tricky. The Raspberry Pi first stage loader does set up a few things depending on the [`arm_64bit`](https://www.raspberrypi.com/documentation/computers/config_txt.html#arm_64bit) setting. `u-boot` then needs to match this accordingly. So for such a 32bit-\>64bit upgrade, you would need to also upgrade the bootloader which is a potentially destructive operation.

Hence, the answer is a “can be done, but depends.”

Greetz,  
Josef

---

_[View the full topic](https://hub.mender.io/t/update-from-bullseye-32bit-to-trixie-64bit/8116)._