Martin Jansa 4801ca3f03 packagegroup-rpi-test: use MACHINE_ARCH
* fixes this error reported by sstate-diff-machines.sh:
   === Comparing signatures for task do_package_write_ipk.sigdata between raspberrypi2 and raspberrypi3 ===                                                                                                                                                              |
  ERROR: packagegroup-rpi-test different signature for task do_package_write_ipk.sigdata between raspberrypi2 and raspberrypi3                                                                                                                                           |
  NOTE: Starting bitbake server...                                                                                                                                                                                                                                       |
  Hash for dependent task packagegroups/packagegroup-rpi-test.bb:do_package changed from 90d4d6b4f44b5c02560c4fd3a1d6143d7c79e75a110db351c99d393a58b5cf26 to 32d7a96f98179695ff0dce057a8501a6920ce7f053a47c3bd6bd50613bd2618b                                            |
  Unable to find matching sigdata for /OE/build/luneos-master/webos-ports/meta-raspberrypi/recipes-core/packagegroups/packagegroup-rpi-test.bb:do_package with hashes 90d4d6b4f44b5c02560c4fd3a1d6143d7c79e75a110db351c99d393a58b5cf26 or 32d7a96f98179695ff0dce057a8501a|
  6920ce7f053a47c3bd6bd50613bd2618b                                                                                                                                                                                                                                      |

* MACHINE_EXTRA_RRECOMMENDS in RRECOMMENDS_${PN} is MACHINE specific, e.g. between raspberrypi2 and raspberrypi3:

  tmp-glibc/sstate-diff/1580322520/raspberrypi2/all-webos-linux/packagegroup-rpi-test/1.0-r0.do_package.sigdata.90d4d6b4f44b5c02560c4fd3a1d6143d7c79e75a110db351c99d393a58b5cf26
  tmp-glibc/sstate-diff/1580322520/raspberrypi3/all-webos-linux/packagegroup-rpi-test/1.0-r0.do_package.sigdata.32d7a96f98179695ff0dce057a8501a6920ce7f053a47c3bd6bd50613bd2618b

  bitbake-diffsigs tmp-glibc/sstate-diff/1580322520/raspberrypi*/*/packagegroup-rpi-test*/*do_package.sig*                                                                                                    |
  NOTE: Starting bitbake server...
  basehash changed from ee2d20ddb4aa98ffefe5c4c56ba2e59833ba94ed3a4523d3e52683209626aa23 to ca3df8d8ef86b298f57c41ffba278dd0330ffb00e7e25943c272c8b3c57a6dc3
  Variable MACHINE_EXTRA_RRECOMMENDS value changed:
  "  kernel-modules udev-rules-rpi {+    linux-firmware-rpidistro-bcm43430     linux-firmware-rpidistro-bcm43455     bluez-firmware-rpidistro-bcm43430a1-hcd     bluez-firmware-rpidistro-bcm4345c0-hcd +}"

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2020-01-30 16:08:58 +00:00
2017-05-26 12:16:52 +01:00
2020-01-22 18:09:10 +00:00
2020-01-22 18:09:10 +00:00

meta-raspberrypi

Yocto BSP layer for the Raspberry Pi boards - http://www.raspberrypi.org/.

Build Status Build Status Build Status Documentation Status Matrix

Description

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).
  • Angstrom.
  • Yocto/Poky (main focus of testing).

Dependencies

This layer depends on:

  • URI: git://git.yoctoproject.org/poky

    • branch: master
    • revision: HEAD
  • URI: git://git.openembedded.org/meta-openembedded

    • layers: meta-oe, meta-multimedia, meta-networking, meta-python
    • branch: master
    • revision: HEAD

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. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is used)
  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. dd to a SD card the generated sdimg file (use xzcat if rpi-sdimg.xz is used)
  4. 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=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 read more at https://kas.readthedocs.io/en/1.0/index.html

Maintainers

  • Andrei Gherzan <andrei at gherzan.ro>
S
Description
No description provided
Readme 5.4 MiB
Languages
C 65.6%
BitBake 32.6%
Shell 1.2%
Dockerfile 0.5%