BSP platform manifest
Clone or download
Latest commit ea840f7 Oct 3, 2017
otavio Update for Yocto Project 2.4 based release
This updates the references to 'rocko' as well as the README content
so it points to the latest release.

Change-Id: I3fffd76d2b996d57e5c14960205d054188fb36c4
Signed-off-by: Otavio Salvador <>


FSL Community BSP

To get the BSP you need to have repo installed and use it as:

Install the repo utility:

$: mkdir ~/bin
$: curl > ~/bin/repo
$: chmod a+x ~/bin/repo

Download the BSP source:

$: PATH=${PATH}:~/bin
$: mkdir fsl-community-bsp
$: cd fsl-community-bsp
$: repo init -u -b rocko
$: repo sync

At the end of the commands you have every metadata you need to start work with.

To start a simple image build:

$: source ./setup-environment build
$: bitbake core-image-minimal

You can use any directory to host your build.

The source code is checked out at fsl-community-bsp/sources.


To contribute to this layer you should send the patches for review to the mailing list.

When creating patches, please use something like:

$: git format-patch -s --subject-prefix='fsl-community-bsp-platform][PATCH][rocko' origin

When sending patches, please use something like:

$: git send-email --to <generated patch>

Using Development and Testing Branches

Replace the repo init command above with one of the following:


For developers

$: repo init -u -b master

For intrepid developers and testers

Patches are typically merged into master-next and then are merged into master after a testing and comment period. It’s possible that master-next has something you want or need. But it’s also possible that using master-next breaks something that was working before. Use with caution.

$: repo init -u -b master-next