# Raspberry Pi 3 Model B/B+ Raspbian **URL:** \ **Category:** Debian family\ **Created:** [November 29, 2018, 12:12am UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140 "2018-11-29T00:12:59Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![eystein](https://avatars.discourse-cdn.com/v4/letter/e/e5b9ba/32.png) [@eystein](https://hub.mender.io/u/eystein)\ **Post date:** [November 29, 2018, 12:13am UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/1 "2018-11-29T00:13:00Z")
# Board description The Raspberry Pi 3 Model B/B+ is a popular single board computer based on Broadcom SoCs. It is the most powerful board within the Raspberry Pi family and probably the most popular with “makers”. ![770A5842-462x322](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/1X/c870116a18648951ba6e43fdde2312805dba6d8e.jpeg) URL: [https://www.raspberrypi.org/products/raspberry-pi-3-model-b-plus](https://www.raspberrypi.org/products/raspberry-pi-3-model-b-plus?target=_blank) URL: [https://www.raspberrypi.org/products/raspberry-pi-3-model-b](https://www.raspberrypi.org/products/raspberry-pi-3-model-b?target=_blank) Wiki: [https://elinux.org/RPi\_Hub](https://elinux.org/RPi_Hub?target=_blank) # Test results The Raspberry Pi OS releases in the table below have been tested by the Mender community. Please update it if you have tested this integration on other [Raspberry Pi OS releases](https://downloads.raspberrypi.org/?target=_blank): | Rasbian | Build | Runtime | | --- | --- | --- | | Raspberry Pi OS Bullseye 2023-05-03 | :test_works: | :test_works: | | Raspberry Pi OS Bullseye 2022-09-22 | :test_works: | :test_works: | | Raspberry Pi OS Bullseye 2022-01-28 | :test_works: | :test_works: | | Raspberry Pi OS Bullseye 2021-10-30 | :test_works: | :test_works: | | Raspberry Pi OS Buster 2020-05-27 | :test_works: | :test_works: | | Raspbian Buster 2020-02-05 | :test_works: | :test_works: | | Raspbian Buster 2019-09-26 | :test_works: | :test_works: | | Raspbian Buster 2019-09-16 | :test_works: | :test_works: | | Raspbian Buster 2019-07-10 | :test_works: | :test_works: | | Raspbian Buster 2019-06-20 | :test_works: | :test_workaround: [Note: Upgrading from Stretch](#footnote_boot_files) | | Raspbian Stretch 2019-04-08 | :test_works: | :test_works: | | Raspbian Stretch 2018-11-13 | :test_works: | :test_works: | **Build** Means that the image generation completes without errors and outputs images. **Runtime** Means that Mender has been verified to work on the board. # Image downloads The Raspberry Pi OS images in the table below come with Mender integrated. | Release | Size (uncompressed) | Size (compressed) | SHA-256 | | --- | --- | --- | --- | | [Raspberry Pi OS Bullseye Lite 2023-05-03](https://d4o6e0uccgv40.cloudfront.net/2023-05-03-raspios-bullseye-armhf-lite/arm/2023-05-03-raspios-bullseye-armhf-lite-raspberrypi3-mender-convert-4.2.2.img.xz) | 7.4 GB | 730 MB | d9c54504de253d7c44f71523884695dc88fd779ed4bc9f6759506a29b73821df | | [Raspberry Pi OS Bullseye Lite 2022-09-22](https://d4o6e0uccgv40.cloudfront.net/2022-09-22-raspios-bullseye-armhf-lite/arm/2022-09-22-raspios-bullseye-armhf-lite-raspberrypi3-mender-convert-4.1.0.img.xz) | 7.4 GB | 664 MB | 6be5ffdc7e1a8ca0f6775a4d128d27db1e9ed6c51ea9644a8ab4fffd205e2003 | | [Raspberry Pi OS Bullseye Lite 2022-01-28](https://d4o6e0uccgv40.cloudfront.net/2022-01-28-raspios-bullseye-armhf-lite/arm/2022-01-28-raspios-bullseye-armhf-lite-raspberrypi3-mender-convert-3.0.0.img.xz) | 7.4 GB | 575 MB | dc1ac00cade5eba08e98a14fd7e78e197160cd491882549e9479f93e289e2685 | | [Raspberry Pi OS Bullseye Lite 2021-10-30](https://d4o6e0uccgv40.cloudfront.net/2021-10-30-raspios-bullseye-armhf-lite/arm/2021-10-30-raspios-bullseye-armhf-lite-raspberrypi3-mender-convert-2.6.2.img.xz) | 7.4 GB | 564 MB | 3e48e83d56ba546d43087211d2017cba020489c290bce2c4f7735da52745809b | | [Raspberry Pi OS Buster Lite 2021-01-11](https://d4o6e0uccgv40.cloudfront.net/2021-01-11-raspios-buster-armhf-lite/arm/2021-01-11-raspios-buster-armhf-lite-raspberrypi3-mender-convert-2.6.0.img.xz) | 7.4 GB | 552 MB | 170743eeac0935b96b987c53c1ec909f4a02e6e600b3f09508b0ab49ffbdf509 | | [Raspberry Pi OS Buster Lite 2020-05-27](https://d4o6e0uccgv40.cloudfront.net/2020-05-27-raspios-buster-lite-armhf/arm/2020-05-27-raspios-buster-lite-armhf-raspberrypi3-mender-2.5.0.img.xz) | 7.4 GB | 546 MB | 68c30d665c3ee567a8cd225ddca147ca8f91dc4efdeca90a796048ac5124500c | | [Raspbian Buster Lite 2020-02-05](https://d4o6e0uccgv40.cloudfront.net/2020-02-05-raspbian-buster-lite/arm/2020-02-05-raspbian-buster-lite-mender-2.2.0.img.xz) | 7.4 GB | 549 MB | 52d3113156715c3b4de3a12a729d17a96fe5af7eba886f862af8ba55543e743a | # Get started If you are starting with Mender, use a prebuilt image from above and follow the [Mender Get Started](https://docs.mender.io/get-started). # Convert your own image (advanced) To save time, use a prebuilt image and follow the [Mender Get Started](https://docs.mender.io/get-started). The rest of this post explains how to build your own customized Raspberry Pi OS image with Mender integrated. ## Prerequisites - A Linux-based laptop/workstation (Ubuntu has been verified to work) - You need to [install Docker Engine](https://docs.docker.com/install) to use this tutorial ### Build Docker image for `mender-convert` Open a terminal and clone the [mender-convert repository](https://github.com/mendersoftware/mender-convert), e.g. ```bash git clone -b 3.0.0 https://github.com/mendersoftware/mender-convert.git ``` Enter your `mender-convert` environment: ```bash cd mender-convert ``` There is a utility script which can be used to generate the appropriate docker image to run `mender-convert`: ```bash ./docker-build ``` This will create a container image you can use to run `mender-convert`. ## Download the latest stable Raspberry Pi raw disk image Download the raw Raspberry Pi disk image into a subdirectory `input`: ```bash mkdir -p input cd input wget https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2022-01-28/2022-01-28-raspios-bullseye-armhf-lite.zip ``` Extract the raw Raspberry Pi disk image: ```bash unzip 2022-01-28-raspios-bullseye-armhf-lite.zip && cd .. ``` ## Convert the Raspberry Pi disk image to support Mender With the raw disk image and the container configured above, we can convert the image. You can get your Mender Professional tenant token at the [My organization page in Mender Professional](https://hosted.mender.io/ui/#/settings/my-organization). Configure the Mender client for hosted Mender server: ```bash ./scripts/bootstrap-rootfs-overlay-hosted-server.sh \ --output-dir ${PWD}/input/rootfs_overlay_demo \ --tenant-token "Paste token from Mender Professional" ``` There are additional scripts in the `scripts/` directory to configure with a local demo server, or production server. Run mender-convert inside the container by running: ```bash MENDER_ARTIFACT_NAME=release-1 ./docker-mender-convert \ --disk-image input/2022-01-28-raspios-bullseye-armhf-lite.img \ --config configs/raspberrypi3_config \ --overlay ./input/rootfs_overlay_demo ``` Conversion will take 10-15 minutes, depending on your storage and resources available. **NOTE**! You will need an SD card with an capacity of at least **8GB** when using the default arguments. The SD card layout will be the following using the default arguments: | Part | Type | Purpose | Size | Configure size | | --- | --- | --- | --- | --- | | mmcblk0p1 | vfat | Store the bootloader | 256MB | `MENDER_BOOT_PART_SIZE_MB` | | mmcblk0p2 | ext4 | Store the root file system and kernel (active) | 3892MB | `MENDER_STORAGE_TOTAL_SIZE_MB` [1](#footnote1) | | mmcblk0p3 | ext4 | Store the root file system and kernel (inactive) | 3892MB | `MENDER_STORAGE_TOTAL_SIZE_MB` [1](#footnote1) | | mmcblk0p4 | ext4 | Store persistent data, preserved during Mender updates. | 128MB | `MENDER_DATA_PART_SIZE_MB` [2](#footnote2) | 1. The rootfs partition size is calculated using the following formula: ``` (storage-total-size-mb - data-part-size-mb - boot-part-size) / 2 ``` 2. You rarely need to adjust the data part size using `MENDER_DATA_PART_SIZE_MB` as this will expanded on first boot to occupy the remaining free blocks of the SD card. You can read more about the partition layout required for Mender [here](https://docs.mender.io/devices/general-system-requirements#partition-layout) ## Use the output images After a successful conversion, the images and artifacts are: - deploy/2021-10-30-raspios-bullseye-armhf-lite-raspberrypi3-mender.cfg - deploy/2021-10-30-raspios-bullseye-armhf-lite-raspberrypi3-mender.ext4 - deploy/2021-10-30-raspios-bullseye-armhf-lite-raspberrypi3-mender.img - deploy/2021-10-30-raspios-bullseye-armhf-lite-raspberrypi3-mender.mender The disk image (with `.img` suffix) is used to provision the device storage for devices without Mender running already. You can write write the `img` image to an SD card using the following command: ```bash cat deploy/2021-10-30-raspios-bullseye-armhf-lite-raspberrypi3-mender.img | sudo dd of= bs=4M && sudo sync ``` **Be careful! If you point to the wrong `` when executing the above command, you risk overwriting your workstation’s local or connected storage devices.** On the other hand, if you already have Mender running on your device and want to deploy a rootfs update from this conversion, you should use the [Mender Artifact](https://docs.mender.io/overview/artifact) files, which have `.mender` suffix. You can either deploy this Artifact in managed mode with the Mender server (upload it under Releases in the server UI) or by using the Mender client only in [Standalone deployments](https://docs.mender.io/client-configuration/standalone-deployments). ### Boot from the SD card and connect to your Mender server Ensure your device has Internet connectivity (e.g. through Ethernet cable with DHCP support). After provisioning a SD card with the converted disk image (`.sdimg`) above, boot your device from it. After about 10 minutes, you should see your device Pending authorization under the Devices tab in your Mender server. Authorize your device to join your Mender server. You can now deploy software updates to your Raspberry Pi using the Mender server! # An improved workflow to generate Artifacts The workflow of using an emulated device works for testing purposes, but it might have some limitations as we are emulating and not logged in to a real device or user. When working with real deployments the recommended workflow is to have one _golden device_, that has _not_ been converted to support Mender. On this device you carry out all the modifications you need, and then use the resulting SD card to create Mender Artifact files, in summary: - flash vanilla Rasbian to the SD card - boot the SD card, log in and make any modifications needed - copy the SD card into an image on your workstation (e.g. using `dd`) - run `mender-convert` with the `--disk-image` option to generate a Mender Artifact (like above) - upload the Artifact to your Mender server - deploy it to your devices Note that your golden device or SD card is not running Mender and is not modified during deployments. It is simply the “source” for generating the Artifacts that you deploy to the devices in the field. # References - The documentation on [Building a Mender Debian image](https://docs.mender.io/artifacts/debian-family) contains more information about using Mender with the Debian family of distributions. - The official [Mender documentation](https://docs.mender.io/) explains how Mender works. This is simply a board-specific complement to the official documentation. # Known issues ### raspi-config does not work as expected on a converted image The `raspi-config` tool is a small utility that is commonly used on Raspberry Pi OS to configure various aspects of the Raspberry Pi hardware and trying to use this tool on a converted image will not work (by design). Specifically it relates to fact that we change the mount point of the boot partition, which on a stock image is mounted at `/boot`, but on a converted image it is mounted at `/uboot`. The `raspi-config` tool will try to perform lookups of files in `/boot`, and this is typically what will fail when trying to run this tool on a converted image. The recommend approach is to use the `raspi-config` utility on the “Golden Image” as described in the “ **An improved workflow to generate Artifacts** ” section above, and not try to modify the converted image as this should be viewed as a static configuration that you can share across your device fleet. ## Boot firmware files Raspberry Pi boards have a set of boot firmware files that are located on the vfat boot part, and a selection of these files are: ```auto bootcode.bin fixup.dat fixup_cd.dat fixup_db.dat fixup_x.dat start.elf start_cd.elf start_db.elf start_x.elf ``` Occasionally there will be changes to the Raspberry Pi software stack that requires that these files are updated. One example would be a change in the Linux kernel that relies on functional changes in the boot firmware and in this case you need to update the boot firmware together with the Linux kernel to get a functional device. See this [thread ](https://groups.google.com/a/lists.mender.io/d/msg/mender/98PMIMUp8kA/cOvIes1gDAAJ) where the limitations of the boot firmware files on Raspberry Pi are discussed. Because of this limitation certain upgrade paths using Mender might not work out-of-the box, e.g one known that will not work is: - Raspbian Stretch 2019-04-08 → Raspbian Buster 2019-06-20 To support this update path you must update the boot firmware files at the same time you are updating to `Raspbian Buster 2019-06-20`. You can utilize [state-scripts](https://docs.mender.io/artifacts/state-scripts) for this. Note that it is unsafe to do update the boot firmware files because there is no way you can update these files atomically and it is not possible to roll-back in case you install something that does not boot, which might render your device unusable without physical intervention. ## Devicetree is not updated To be able to support update of Linux kernel and devicetree, Mender requires these to be installed in the `/boot` directory for each rootfs (normally `/dev/mmcblk0p2` and `/dev/mmcblk0p3` ). On the other hand, the Raspberry Pi boot firmware requires that the DTB file is in the same partition as the boot firmware ( `/dev/mmcbl0p1` ) and the config.txt file. For now Mender will not use the DTB that is delivered with new artifacts and will continue to boot with the original DTB that was populated using the `sdimg` file. ## Problem using ‘dtoverlay=pi3-disable-bt’ > `pi3-disable-bt` disables the Bluetooth device and restores UART0/ttyAMA0 to > GPIOs 14 and 15. It is also necessary to disable the system service that > initialises the modem so it doesn’t use the UART There is currently a known issue with above functionality, that is to enable `UART0` on PIN 14 and 15. It is actually not something that is caused by Mender specifically, but Mender requires `U-boot` to be present to support robust features such as roll-back. `U-boot` is typically not enabled if you do a stock Raspberry Pi and some people are often surprised that the Bluetooth UART stopped working when they integrate Mender . The problem is in `U-boot` which does conflicting configuration, and there is a workaround reported [here](https://github.com/agherzan/meta-raspberrypi/issues/374) and it has been reported to U-boot but unclear when/if it will be fixed. * * * _If this post was useful to you, please press like, or leave a thank you note to the contributor who put valuable time into this and made it available to you. It will be much appreciated!_ ---
**Author:** ![eystein](https://avatars.discourse-cdn.com/v4/letter/e/e5b9ba/32.png) [@eystein](https://hub.mender.io/u/eystein)\ **Post date:** [May 3, 2019, 11:08pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/23 "2019-05-03T23:08:46Z")
Tested newest Raspbian (2019-04-08) with Hosted Mender just now. No issues. Also upgrading from 2018-11-13 to 2019-04-08 using a Mender Artifact works as expected! 🙂 ---
**Author:** ![gil0109](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/gil0109/32/124_2.png) [@gil0109](https://hub.mender.io/u/gil0109)\ **Post date:** [June 1, 2019, 12:30am UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/24 "2019-06-01T00:30:34Z")
I built my mender image using 1.1x in [Feb](https://github.com/mendersoftware/mender-convert/tree/2743366dbee00f77f5f8a4c49864d0c94ebc792e), then Mender Server 2.0 was released. Will my image work if I upgrade my server to Mender 2.0? There was one change in your readme where you removed this line: ./docker-mender-convert from-raw-disk-image **–mender-client /mender** Currently, the image I created works great with Mender 1.7 ---
**Author:** ![kacf](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/kacf/32/146_2.png) [@kacf](https://hub.mender.io/u/kacf)\ **Post date:** [June 3, 2019, 6:18am UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/25 "2019-06-03T06:18:05Z")
Yes, that should be no problem! ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [August 12, 2019, 1:02pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/26 "2019-08-12T13:02:37Z")
3 posts were split to a new topic: [Issues adding Mender to 2018-04 raspbian lite](https://hub.mender.io/t/issues-adding-mender-to-2018-04-raspbian-lite/907) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [August 6, 2019, 8:34am UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/29 "2019-08-06T08:34:46Z")
11 posts were split to a new topic: [Problems with Raspbian Buster](https://hub.mender.io/t/problems-with-raspbian-buster/888) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [August 12, 2019, 12:12pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/38 "2019-08-12T12:12:45Z")
5 posts were split to a new topic: [Issue with GL driver on Raspbian Stretch](https://hub.mender.io/t/issue-with-gl-driver-on-raspbian-stretch/906) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [January 15, 2020, 1:50pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/45 "2020-01-15T13:50:35Z")
6 posts were split to a new topic: [Device not visible in “Pending”](https://hub.mender.io/t/device-not-visible-in-pending/1439) ---
**Author:** ![mirzak](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/mirzak/32/2056_2.png) [@mirzak](https://hub.mender.io/u/mirzak)\ **Post date:** [April 3, 2020, 9:20am UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/51 "2020-04-03T09:20:33Z")
3 posts were split to a new topic: [Can I create a new artifact from an mender based sdimg?](https://hub.mender.io/t/can-i-create-a-new-artifact-from-an-mender-based-sdimg/1741) ---
**Author:** ![thesillywhat](https://avatars.discourse-cdn.com/v4/letter/t/57b2e6/32.png) [@thesillywhat](https://hub.mender.io/u/thesillywhat)\ **Post date:** [August 10, 2020, 10:04pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/55 "2020-08-10T22:04:09Z")
Are there any standard set of test cases, that one should conduct to test the integrity of the system. Apart from the normal ones ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [August 11, 2020, 2:27pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/56 "2020-08-11T14:27:28Z")
See this link: [https://docs.mender.io/hosted/devices/yocto-project/bootloader-support/u-boot/integration-checklist](https://docs.mender.io/hosted/devices/yocto-project/bootloader-support/u-boot/integration-checklist) Of course that just tests Mender. You probably will need to review Raspberry Pi docs and general Yocto docs to understand other parts of the system and the needs for testing there. Drew ---
**Author:** ![thesillywhat](https://avatars.discourse-cdn.com/v4/letter/t/57b2e6/32.png) [@thesillywhat](https://hub.mender.io/u/thesillywhat)\ **Post date:** [August 11, 2020, 3:12pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/57 "2020-08-11T15:12:52Z")
Yes, Sorry I did not phrase my question properly. I did perform those steps. What I wanted to know. How do I test the retry and rollback feature from the [https://hosted.mender.io](https://hosted.mender.io) How do I create a failed scenario? How do I create a retry scenario? I think I don’t know care about the fail scenario because the board integration checklist takes care of that. but How Do I create a retry scenario? ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [August 11, 2020, 7:20pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/58 "2020-08-11T19:20:02Z")
The steps in the integration checklist do verify that rollback is performed but if you want to test it in a full deployment then just power cycle the board while it is rebooting the first time. Testing a retry will require implementing state scripts. You can see our [examples here](https://github.com/mendersoftware/meta-mender/tree/master/meta-mender-demo/recipes-mender/example-state-scripts). If you create a ArtifactCommit\_Enter script that returns “21” then it will retry. You will need to make sure to eventually return OK to avoid the server timing out the deployment. Drew ---
**Author:** ![Aalex](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@Aalex](https://hub.mender.io/u/Aalex)\ **Post date:** [May 31, 2021, 1:10pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/59 "2021-05-31T13:10:45Z")
Im still having the Problem with my Image not booting after converting it due to ‘dtoverlay=pi3-disable-bt’. Can someone explain how exactly to aply the workaround reported in [here](https://github.com/agherzan/meta-raspberrypi/issues/374) Im not very experienced with patching uboot. ---
**Author:** ![Aalex](https://avatars.discourse-cdn.com/v4/letter/a/eb9ed0/32.png) [@Aalex](https://hub.mender.io/u/Aalex)\ **Post date:** [June 14, 2021, 7:28am UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/60 "2021-06-14T07:28:04Z")
Hi, I was able to fix the problem with disable-bt overlay: - I forked the mender-uboot and applied the patch mentioned [here](https://github.com/agherzan/meta-raspberrypi/issues/374) - I patched integration-scripts to create the binaries - I run mender-convert using the patched binaries Everything is now running nice and smoothly and i can use ttyAMA0. I think it would make sense to offer that patched version of mender-uboot binaries for a “new” device type (raspberrypi3serial) and by assigning RASPBERRYPI\_CONFIG=“raspberrypi3serial” those binaries would then be used when running mender convert. the raspberrypi\_config.) ---
**Author:** ![oleorhagen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/oleorhagen/32/297_2.png) [@oleorhagen](https://hub.mender.io/u/oleorhagen)\ **Post date:** [June 14, 2021, 1:09pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/61 "2021-06-14T13:09:21Z")
Sounds interesting! How about a PR, and we’ll take it from there? 😄 ---
**Author:** ![sensslen](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/sensslen/32/245_2.png) [@sensslen](https://hub.mender.io/u/sensslen)\ **Post date:** [February 11, 2022, 3:36pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/62 "2022-02-11T15:36:06Z")
I just encountered an issue when upgrading from buster to bullseye. This update does also need updates to the boot partition. I’m writing this here in the hope it helps others spend less time debugging… ---
**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 18, 2022, 8:50pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/63 "2022-11-18T20:50:59Z")
5 posts were split to a new topic: [Mender-convert for Raspberry Pi 3 - storage/card too small](https://hub.mender.io/t/mender-convert-for-raspberry-pi-3-storage-card-too-small/5427) ---
**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 18, 2022, 2:37pm UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/67 "2022-11-18T14:37:58Z")
A post was split to a new topic: [Mender-convert for Raspberry Pi - 64bit?](https://hub.mender.io/t/mender-convert-for-raspberry-pi-64bit/5422) ---
**Author:** ![spratesi](https://avatars.discourse-cdn.com/v4/letter/s/eb8c5e/32.png) [@spratesi](https://hub.mender.io/u/spratesi)\ **Post date:** [September 26, 2023, 6:59am UTC](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140/68 "2023-09-26T06:59:44Z")
I’ve noticed the latest pre-built image (2022-01-28) has `raspberrypi4` in the filename, it is therefore for the Pi 4 and is misplaced in this page I think… (to verify it’s not only a wrong filename, I’ve checked the kernel file, and is the one for the Pi 4 32bit, `kernel7l.img`) [Next page](https://hub.mender.io/t/raspberry-pi-3-model-b-b-raspbian/140.md?page=2)