tree: 3a9b9d2795fa43fb018b8920d4b57d9885b3d215 [path history] [tgz]
  1. .github/
  2. classes/
  3. conf/
  4. docs/
  5. dynamic-layers/
  6. files/
  7. img/
  8. lib/
  9. recipes-bsp/
  10. recipes-connectivity/
  11. recipes-core/
  12. recipes-devtools/
  13. recipes-graphics/
  14. recipes-kernel/
  15. recipes-multimedia/
  16. recipes-sato/
  17. wic/
  18. .gitignore
  19. .readthedocs.yaml
  21. kas-poky-rpi.yml


Yocto BSP layer for the Raspberry Pi boards -

Documentation Status Matrix

Quick links


This is the general hardware specific BSP overlay for the RaspberryPi device.

More information can be found at: (Official Site)

The core BSP part of meta-raspberrypi should work with different OpenEmbedded/Yocto distributions and layer stacks, such as:

  • Distro-less (only with OE-Core).
  • Yoe Disto (Video and Camera Products).
  • Yocto/Poky (main focus of testing).

Yocto Project Compatible Layer

This layer is officially approved as part of the Yocto Project Compatible Layers Program. You can find details of that on the official Yocto Project website.


This layer depends on:

Quick Start

  1. source poky/oe-init-build-env rpi-build
  2. Add this layer to bblayers.conf and the dependencies above
  3. Set MACHINE in local.conf to one of the supported boards
  4. bitbake core-image-base
  5. Use bmaptool to copy the generated .wic.bz2 file to the SD card
  6. Boot your RPI

Quick Start with kas

  1. Install kas build tool from PyPi (sudo pip3 install kas)
  2. kas build meta-raspberrypi/kas-poky-rpi.yml
  3. Use bmaptool to copy the generated .wic.bz2 file to the SD card
  4. Boot your RPI

To adjust the build configuration with specific options (I2C, SPI, ...), simply add a section as follows:

  rpi-specific: |
    ENABLE_I2C = "1"
    RPI_EXTRA_CONFIG = "dtoverlay=pi3-disable-bt"

To configure the machine, you have to update the machine variable. And the same for the distro.

For further information, you can


You can send patches using the GitHub pull request process or/and through the Yocto mailing list. Refer to the documentation for more information.


  • Andrei Gherzan <andrei at>