### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [August 6, 2019, 6:53pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/1 "2019-08-06T18:53:21Z")
# Board description
The Raspberry Pi 4 Model B is the probably most popular board of the Raspberry Pi family.
URL: [https://www.raspberrypi.org/products/raspberry-pi-4-model-b/](https://www.raspberrypi.org/products/raspberry-pi-4-model-b/)
Wiki: [https://elinux.org/RPi\_Hub](https://elinux.org/RPi_Hub?target=_blank)
# Test results
Raspberry Pi 4 is one of the official reference devices of Mender and is easy to get started with. This device is continuously tested as part of Mender testing pipelines which assures high quality of the integration.
## Version notes
This tutorial uses **kirkstone** as the primary target, which is a currently supported LTS release by the Yocto Project. You can find more infomation on releases [here](https://wiki.yoctoproject.org/wiki/Releases).
**NOTE: after the Yocto 4.0 release “`kirkstone`”, `meta-mender-community` moved to [`kas`](https://hub.mender.io/t/using-kas-to-reproduce-your-yocto-builds/6020) configuration files. Please see the TODO: article for building later releases.**
Supported releases for following the tutorial are:
| Yocto Project | Tutorial applies | Maintenance |
| --- | --- | --- |
| scarthgap (5.0) | :test_fails: | :test_fails: does not apply |
| nanbield (4.3) | :test_fails: | :test_fails: does not apply |
| mickledore (4.2) | :test_fails: | :test_fails: does not apply |
| langdale (4.1) | :test_fails: | :test_fails: does not apply |
| kirkstone (4.0) | :test_works: | :test_works: LTS[1](#footnote1) |
| honister (3.4) | :test_fails: | :test_fails: EOL |
| hardknott (3.3) | :test_fails: | :test_fails: EOL |
| gatesgarth (3.2) | :test_fails: | :test_fails: EOL |
| dunfell (3.1) | :test_works: | :test_fails: EOL |
| zeus (3.0) | :test_works: | :test_fails: EOL |
| warrior (2.7) | :test_works: | :test_fails: EOL |
| thud (2.6) | :test_fails: | :test_fails: EOL |
| sumo (2.5) | :test_fails: | :test_fails: EOL |
| rocko (2.4) | :test_fails: | :test_fails: EOL |
1. Disabled GRUB integration for ARM systems which is default in meta-mender/meta-mender-raspberrypi. U-Boot is still primary integration method for this platform.
**Please note:** a failure in the “tutorial applies” column indicates that the instructions do not work without modification. Depending on the combination of release and host Linux distribution, installing other python versions or dependencies might provide a functional state.
**Build** Means that the Yocto Project build using this Mender integration completes without errors and outputs images.
**Runtime** Means that Mender has been verified to work on the board. For U-Boot-based boards, the [integration checklist](https://docs.mender.io/system-updates-yocto-project/board-integration/bootloader-support/u-boot/integration-checklist?target=_blank) has been verified.
# Getting started
## Prerequisites
- A supported Linux distribution and dependencies installed on your workstation/laptop as described in the [Yocto Mega Manual](https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#detailed-supported-distros)
- Google repo tool [installed](https://hub.mender.io/t/google-repo/58/2) and in your `PATH`.
## Configuring the build
### Setup Yocto environment
Set the Yocto Project branch you are building for:
```bash
# set to your branch, make sure it is supported (see table above)
export BRANCH="kirkstone"
```
Create a directory for your `mender-raspberrypi` setup to live in and clone the
meta information.
```bash
mkdir mender-raspberrypi && cd mender-raspberrypi
```
Initialize repo manifest:
```bash
repo init -u https://github.com/mendersoftware/meta-mender-community.git \
-m meta-mender-raspberrypi/scripts/manifest-raspberrypi.xml \
-b ${BRANCH}
```
Fetch layers in manifest:
```bash
repo sync
```
## Setup build environment
Initialize the build environment:
```bash
source setup-environment raspberrypi
```
### Configure Mender server URL (optional)
This section is not required for a successful build but images that are generated by default are only suitable for usage with the Mender client in [Standalone deployments](https://docs.mender.io/artifact-creation/standalone-deployment), due to lack of server configuration.
You can edit the `conf/local.conf` file to provide your Mender server configuration, ensuring the generated images and Mender Artifacts are connecting to the Mender server that you are using. There should already be a commented section in the generated `conf/local.conf` file and you can simply uncomment the relevant configuration options and assign appropriate values to them.
Build for Hosted Mender:
```auto
# To get your tenant token:
# - log in to https://hosted.mender.io
# - click your email at the top right and then "My organization"
# - press the "COPY TO CLIPBOARD"
# - assign content of clipboard to MENDER_TENANT_TOKEN
#
MENDER_SERVER_URL = "https://hosted.mender.io"
MENDER_TENANT_TOKEN = ""
```
### Building the image
You can now proceed with building an image:
```bash
MACHINE=raspberrypi4 bitbake core-image-base
```
Replace `core-image-base` with your desired image target.
### Using the build output
After a successful build, the images and build artifacts are:
- `tmp/deploy/images/raspberrypi4/core-image-base-raspberrypi4.sdimg`
- `tmp/deploy/images/raspberrypi4/core-image-base-raspberrypi4.mender`
The disk image (with `.sdimg` suffix) is used to provision the device storage for devices without Mender running already. Please proceed to [the official documentation on provisioning a new device](https://docs.mender.io/system-updates-yocto-project/provisioning-a-new-device?target=_blank) for steps to do this.
On the other hand, if you already have Mender running on your device and want to deploy a rootfs update using this build, 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 [standalone mode](https://docs.mender.io/artifact-creation/standalone-deployment).
# References
- The template files that are used by this setup can be found in [mender-mender-community](https://github.com/mendersoftware/meta-mender-community/tree/sumo/meta-mender-raspberrypi?target=_blank)
- The Mender integration layer for Raspberry Pi boards can be found in [meta-mender](https://github.com/mendersoftware/meta-mender/tree/master/meta-mender-raspberrypi?target=_blank).
- 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
## Boot firmware files
See [Updating Raspberry Pi boot firmware files using Yocto Project and Mender](https://hub.mender.io/t/updating-raspberry-pi-boot-firmware-files-using-yocto-project-and-mender/1719).
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.
## 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/mmcblk0p1`) 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 `meta-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:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [April 1, 2020, 6:58am UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/2 "2020-04-01T06:58:42Z")
2 posts were split to a new topic: [Wayland not displaying an image on Raspberry Pi 4 (Yocto)](https://hub.mender.io/t/wayland-not-displaying-an-image-on-raspberry-pi-4-yocto/1721)
---
### Author:  [@mikhailtchernychev](https://hub.mender.io/u/mikhailtchernychev)
#### Post date: [September 12, 2020, 7:31pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/3 "2020-09-12T19:31:40Z")
I tried this and got Rpi4 B and got system which is not booting. I think this is yocto problem but I am bery new to this:
Here are build messages:
```
Parsing recipes: 100% |#####################################################################################################################################| Time: 0:02:10
Parsing of 2367 .bb files complete (0 cached, 2367 parsed). 3501 targets, 123 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.44.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-18.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "raspberrypi4"
DISTRO = "poky"
DISTRO_VERSION = "3.0.4"
TUNE_FEATURES = "arm vfp cortexa7 neon vfpv4 thumb callconvention-hard"
TARGET_FPU = "hard"
meta
meta-poky
meta-yocto-bsp = "HEAD:d88d62c20d7d8da85f02edb170dae0280624ad7e"
meta-oe
meta-python
meta-networking
meta-multimedia = "HEAD:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"
meta-raspberrypi = "HEAD:0e05098853eea77032bff9cf81955679edd2f35d"
meta-mender-core
meta-mender-raspberrypi
meta-mender-demo = "HEAD:c6c580303f4149a912437fcc81ebeb107cdb5d43"
NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/2.9/x86_64-nativesdk-libc.tar.xz;sha256sum=d07916b95c419c81541a19c8ef0ed8cbd78ae18437ff28a4c8a60ef40518e423
Initialising tasks: 100% |##################################################################################################################################| Time: 0:00:09
Sstate summary: Wanted 1318 Found 0 Missed 1318 Current 0 (0% match, 0% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
WARNING: u-boot-1_2020.01-r0 do_provide_mender_defines: Found more than one dtb specified in KERNEL_DEVICETREE ( bcm2708-rpi-zero-w.dtb bcm2708-rpi-b.dtb bcm2708-rpi-b-plus.dtb bcm2709-rpi-2-b.dtb bcm2710-rpi-3-b.dtb bcm2710-rpi-3-b-plus.dtb bcm2711-rpi-4-b.dtb bcm2708-rpi-cm.dtb bcm2710-rpi-cm3.dtb overlays/at86rf233.dtbo overlays/disable-bt.dtbo overlays/dwc2.dtbo overlays/gpio-key.dtbo overlays/hifiberry-amp.dtbo overlays/hifiberry-dac.dtbo overlays/hifiberry-dacplus.dtbo overlays/hifiberry-digi.dtbo overlays/i2c-rtc.dtbo overlays/iqaudio-dac.dtbo overlays/iqaudio-dacplus.dtbo overlays/miniuart-bt.dtbo overlays/mcp2515-can0.dtbo overlays/pi3-disable-bt.dtbo overlays/pi3-miniuart-bt.dtbo overlays/pitft22.dtbo overlays/pitft28-resistive.dtbo overlays/pitft35-resistive.dtbo overlays/pps-gpio.dtbo overlays/rpi-ft5406.dtbo overlays/rpi-poe.dtbo overlays/vc4-kms-v3d.dtbo overlays/vc4-fkms-v3d.dtbo overlays/w1-gpio-pullup.dtbo overlays/w1-gpio.dtbo ). Only one should be specified. Choosing the last one: bcm2710-rpi-cm3.dtb. Set KERNEL_DEVICETREE to the desired dtb file to silence this warning.
WARNING: mender-client-2.3.0-r0 do_compile: You are building with the mender-demo layer, which is not intended for production use
WARNING: mender-client-2.3.0-r0 do_compile: You are building with the default server certificate, which is not intended for production use
NOTE: Tasks Summary: Attempted 4567 tasks of which 1 didn't need to be rerun and all succeeded.
Summary: There were 3 WARNING messages shown.
```
On the serial console I see repeated messages:
```
Partition: 0
lba: 49152 oem: 'mkfs.fat' volume: ' V ^ '
rsc 4 fat-sectors 80 c-count 20431 c-size 4 r-dir 1 r-sec 32
Read config.txt bytes 36219 hnd 0x00000097 hash '59ad8ccae9ec30f4'
recover4.elf not found (6)
recovery.elf not found (6)
Read start4.elf bytes 2776132 hnd 0x00000733 hash '02b61d4a1274a453'
Read fixup4.dat bytes 6195 hnd 0x000000ad hash 'eb639eac03f0e496'
0x00d03114 0x00000000 0x00000000
start4.elf: is not compatible
This board requires newer software
Get the latest software from https://www.raspberrypi.org/downloads/
ERROR: 00000044
Boot mode: USB-MSD (04) order f
```
---
### Author:  [@mikhailtchernychev](https://hub.mender.io/u/mikhailtchernychev)
#### Post date: [September 13, 2020, 1:59am UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/4 "2020-09-13T01:59:26Z")
Tried with MACHINE=raspberrypi4-64, the same outcome
---
### Author:  [@mirzak](https://hub.mender.io/u/mirzak)
#### Post date: [September 14, 2020, 6:54am UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/5 "2020-09-14T06:54:37Z")
On what hardware are you trying to run this? It seems to have issue in the very early boot stage (part of the RPi firmware boot)
---
### Author:  [@mikhailtchernychev](https://hub.mender.io/u/mikhailtchernychev)
#### Post date: [September 14, 2020, 4:02pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/6 "2020-09-14T16:02:45Z")
This is Raspberry Pi 4 model B 8GB.
I think the issue is the boot script. It might be trying to load wrong or non-existing kernel.
After I re-named this file (boot.scr) I was able to get into U-boot interactive prompt via UART
and the attached monitor.
Enabling UART kernel output for model 4 B is different from previous models,
it is not sufficient to change config.txt The full procedure is here
> **[Teach, Learn, and Make with Raspberry Pi – Raspberry Pi](https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md)**
I also found that sometimes I have to send few chars from host computer at the moment when
board is powered up. It is weird.
All stock images boot, minimal buildroot image boots, yocto example without mender does.
Mender downloadable image boots.
Mender compiled image (mender-convert, mender with buildroot, mender with yocto) do not.
Mender-convert image allows serial interactive u-boot if boot.scr is renamed.
---
### Author:  [@valentin.m](https://hub.mender.io/u/valentin.m)
#### Post date: [January 20, 2021, 5:02pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/7 "2021-01-20T17:02:21Z")
Hi [mikhailtchernychev](https://hub.mender.io/u/mikhailtchernychev),
did you ever find a solution for your issues? I’m facing the same right now.
Thanks,
Valentin
---
### Author:  [@mikhailtchernychev](https://hub.mender.io/u/mikhailtchernychev)
#### Post date: [January 20, 2021, 5:24pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/8 "2021-01-20T17:24:50Z")
No, we stopped evaluating Rpi4. I only could make work image from May 2020.
---
### Author:  [@QuantumLove](https://hub.mender.io/u/QuantumLove)
#### Post date: [January 28, 2021, 4:13pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/9 "2021-01-28T16:13:22Z")
Can anyone confirm of a distro + image recipe working?
When I boot my raspberrypi4 B it does not give any error but I also don’t have access to SSH nor the monitor.
I am building core-image-base on dunfell
---
### Author:  [@valentin.m](https://hub.mender.io/u/valentin.m)
#### Post date: [January 28, 2021, 8:42pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/10 "2021-01-28T20:42:24Z")
I got it to work in the meantime, I think it works because I set ENABLE\_UART = “1”.
---
### Author:  [@QuantumLove](https://hub.mender.io/u/QuantumLove)
#### Post date: [January 28, 2021, 9:21pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/11 "2021-01-28T21:21:57Z")
Could you share which other changes you made? Which Yocto Version, for example
---
### Author:  [@valentin.m](https://hub.mender.io/u/valentin.m)
#### Post date: [January 29, 2021, 10:14am UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/12 "2021-01-29T10:14:21Z")
We are using dunfell and our config roughly looks like this:
```auto
# local.conf
# --- hardware support
MACHINE = "raspberrypi4"
DISTRO ?= "poky"
INHERIT += "rpi-update-firmware"
# # --- mender stuff
MENDER_ARTIFACT_NAME="xxx"
MENDER_SERVER_URL = "https://hosted.mender.io"
MENDER_TENANT_TOKEN = "xxx"
ENABLE_UART = "1"
# for remote shell
IMAGE_INSTALL_append = " mender-connect"
MENDER_CONNECT_USER = "root"
INHERIT += "mender-full"
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
VIRTUAL-RUNTIME_initscripts = ""
RPI_USE_U_BOOT = "1"
MENDER_BOOT_PART_SIZE_MB = "40"
MENDER_STORAGE_TOTAL_SIZE_MB = "8192"
MENDER_DATA_PART_SIZE_MB = "2048"
IMAGE_INSTALL_append = " kernel-image kernel-devicetree"
IMAGE_FSTYPES_remove += " rpi-sdimg"
MENDER_FEATURES_ENABLE_append = " mender-uboot mender-image-sd"
MENDER_FEATURES_DISABLE_append = " mender-grub mender-image-uefi"
```
```auto
# layers
${TOPDIR}/../sources/poky/meta \
${TOPDIR}/../sources/poky/meta-poky \
${TOPDIR}/../sources/poky/meta-yocto-bsp \
${TOPDIR}/../sources/meta-openembedded/meta-oe \
${TOPDIR}/../sources/meta-openembedded/meta-python \
${TOPDIR}/../sources/meta-openembedded/meta-networking \
${TOPDIR}/../sources/meta-openembedded/meta-multimedia \
${TOPDIR}/../sources/meta-raspberrypi \
${TOPDIR}/../sources/meta-mender/meta-mender-core \
${TOPDIR}/../sources/meta-mender/meta-mender-raspberrypi \
```
---
### Author:  [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [January 29, 2021, 7:05pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/13 "2021-01-29T19:05:55Z")
Hi @valentin.m the ssh daemon may not be installed. What do the following commands show?
```auto
bitbake -e core-image-base 2>&1 | grep ^IMAGE_FEATURES
bitbake -e core-image-base 2>&1 | grep ^EXTRA_IMAGE_FEATURES
```
Drew
---
### Author:  [@Terence](https://hub.mender.io/u/Terence)
#### Post date: [February 12, 2021, 5:36pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/14 "2021-02-12T17:36:38Z")
Hi guys,
@mikhailtchernychev @valentin.m I wonder if you have fixed your issue but as the logs suggest, you need to set the KERNEL\_DEVICETREE to the right version for your raspberrypi.
For a raspberrypi4 B, you can add `KERNEL_DEVICETREE = "bcm2711-rpi-4-b.dtb"` in your local.conf (or a machine file).
Hope this helps!
---
### Author:  [@unicornmafia](https://hub.mender.io/u/unicornmafia)
#### Post date: [April 12, 2021, 10:34pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/15 "2021-04-12T22:34:56Z")
I suddenly can’t see anything on this page. just get a blank page under the heading.
---
### Author:  [@oleorhagen](https://hub.mender.io/u/oleorhagen)
#### Post date: [April 13, 2021, 11:02am UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/16 "2021-04-13T11:02:57Z")
Renders fine here
---
### Author:  [@unicornmafia](https://hub.mender.io/u/unicornmafia)
#### Post date: [April 13, 2021, 5:11pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/17 "2021-04-13T17:11:27Z")
I can see it now too! must have gotten fixed. 🙂
---
### Author:  [@ikkysleepy](https://hub.mender.io/u/ikkysleepy)
#### Post date: [May 2, 2021, 8:33am UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/18 "2021-05-02T08:33:47Z")
I can’t get this to work for raspberry pi 4. I get a blank screen when I burn the image. The build works fine and I left everything to default. I am not sure how to to trouble shoot this. I tried two different sd cards and still have the same issue. I am using etcher to flash the image. I have an older build and this works fine on the older pi 4 device. The ethernet lights are solid, which leads me to believe it’s not booting up correctly. This is for the dunfell branch.
---
### Author:  [@drewmoseley](https://hub.mender.io/u/drewmoseley)
#### Post date: [May 2, 2021, 3:16pm UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/19 "2021-05-02T15:16:58Z")
There was an issue related to RpI4 that I think has been fixed recently. Can you try the master branch?
Drew
---
### Author:  [@ikkysleepy](https://hub.mender.io/u/ikkysleepy)
#### Post date: [May 3, 2021, 7:25am UTC](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889/20 "2021-05-03T07:25:35Z")
I tried, didn’t work. I did git checkout master and repo sync, but still the same issue. I tried zeus branch, and the same thing.
[Next page](https://hub.mender.io/t/raspberry-pi-4-model-b-yocto-4-0-kirkstone-and-earlier/889.md?page=2)