Need help with balena-raspberrypi?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

balena-os
130 Stars 41 Forks Apache License 2.0 1.3K Commits 63 Opened issues

Description

Balena support for RaspberryPI boards

Services available

!
?

Need anything else?

Contributors list

balena-raspberrypi repository

Clone/Initialize the repository

There are two ways of initializing this repository: * Clone this repository with "git clone --recursive".

or

  • Run "git clone" and then "git submodule update --init --recursive". This will bring in all the needed dependencies.

Build information

Build flags

  • Consult layers/meta-balena/README.md for info on various build flags (setting up serial console support for example) and build prerequisites. Build flags can be set by using the build script (barys) or by manually modifying
    local.conf
    .

See below for using the build script.

Build this repository

  • Run the build script:

    ./balena-yocto-scripts/build/barys
  • You can also run barys with the -h switch to inspect the available options

Custom build using this repository

  • Run the build script in dry run mode to setup an empty

    build
    directory
    ./balena-yocto-scripts/build/barys --remove-build --dry-run
  • Edit the

    local.conf
    in the
    build/conf
    directory
  • Prepare build's shell environment

    source layers/poky/oe-init-build-env
  • Run bitbake (see message outputted when you sourced above for examples)

Contributing

Issues

For issues we use an aggregated github repository available here. When you create issue make sure you select the right labels.

Pull requests

To contribute send github pull requests targeting this repository.

Please refer to: Yocto Contribution Guidelines and try to use the commit log format as stated there. Example: ```

: Short description

I'm going to explain here what my commit does in a way that history would be useful.

Changelog-entry: User facing description of the issue Signed-off-by: Joe Developer [email protected] ```

The header of each commit must not exceed 72 characters in length and must be in 1 line only.

The header and the subject of each commit must be separated by an empty line.

The subject of each commit must not exceed 72 characters in length but can be wrapped to several lines.

The subject and the footer of each commit must be separated by an empty line.

Every pull request must contain at least one commit annotated with the

Changelog-entry
footer. The messages contained in these footers will be used to automatically fill the changelog on every new version.

Also, every update to

meta-balena
should be separated into its own commit, if the body of that commit contains the following line
Updated meta-balena from X to Y
the generated changelog will include a button to show all the updates in
meta-balena
from the version after
X
to
Y
.

An example of a valid commit updating

meta-balena
is:
layers/meta-balena: Update to v2.24.0

Update meta-balena from 2.19.0 to 2.24.0

Changelog-entry: Update the meta-balena submodule from v2.19.0 to v2.24.0

Make sure you mention the issue addressed by a PR. See: * https://help.github.com/articles/autolinked-references-and-urls/#issues-and-pull-requests * https://help.github.com/articles/closing-issues-via-commit-messages/#closing-an-issue-in-a-different-repository

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.