Yocto BSP layer for the Raspberry Pi boards - http://www.raspberrypi.org/.
|
Sponsored by: |
- Git repository web frontend: https://github.com/agherzan/meta-raspberrypi
- Mailing list (yocto mailing list): yocto@lists.yoctoproject.org
- Issues management (Github Issues): https://github.com/agherzan/meta-raspberrypi/issues
- Documentation: http://meta-raspberrypi.readthedocs.io/en/latest/
This is the general hardware specific BSP overlay for the RaspberryPi device.
More information can be found at: http://www.raspberrypi.org/ (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).
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:
- URI: git://git.yoctoproject.org/poky
- branch: master
- revision: HEAD
- source poky/oe-init-build-env rpi-build
- Add this layer to bblayers.conf and the dependencies above
- Set MACHINE in local.conf to one of the supported boards
- bitbake core-image-base
- Use bmaptool to copy the generated .wic.bz2 file to the SD card
- Boot your RPI
- Install kas build tool from PyPi (sudo pip3 install kas)
- kas build meta-raspberrypi/kas-poky-rpi.yml
- Use bmaptool to copy the generated .wic.bz2 file to the SD card
- Boot your RPI
To adjust the build configuration with specific options (I2C, SPI, ...), simply add a section as follows:
local_conf_header:
rpi-specific: |
ENABLE_I2C = "1"
RPI_EXTRA_CONFIG = "dtoverlay=disable-bt"
To configure the machine, you have to update the machine
variable.
And the same for the distro
.
For further information, you can read more at https://kas.readthedocs.io/en/latest/index.html
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 gherzan.com>