Customizing the BSP

This page describes how to add a custom layer to our NXP BSP. You will also get an idea how Yocto recipes work and how you can create your own image.

Your possibilities with Yocto are endless - if you know how to use it. The sections below shall just give common examples and an easier entry.

Further information can be found in the Yocto Project Documentation.

Hint

All below commands are examples and have to be fitted to your needs.

Setup your build-directory with the desired machine and distro like explained in Bitbake Setup.

DISTRO=karo-minimal MACHINE=tx8m-1610 source karo-setup-release.sh -b build-tx8m-1610

Kernel & Devicetree

The following steps describe how Kernel and Devicetree can be modified.
You can use these steps to develop Kernel and Devicetree fitted to your needs.
Once you’re done you can read further to persist your changes.

Note

Devshell is just for development purpose. To be able to get your changes into the well-known files bitbake produces, you will have to persist them into recipes.

After leaving devshell and executing any bitbake command all your changes might be lost!

Entering Devshell

  1. Configure Kernel with the current defconfig
bitbake linux-imx -c configure
  1. Enter Devshell
bitbake linux-imx -c devshell

In the devshell you are inside the already patched and configured Kernel source, with a working cross-compile environment.

Building Kernel

Building the Kernel inside the devshell:

make Image

The console output will tell you the build directory it left. Inside it at arch/arm64/boot/Image you’ll find your Kernel.

Devicetree

.dts(i) files are located in arch/arm64/boot/dts/freescale/.

Note

For your own hardware add your own *.dts files.

To compile a specific devicetree run:

make freescale/<dts-file-name>.dtb

The console output will tell you the build directory it left. Inside it at arch/arm64/boot/dts/freescale/ you’ll find the compiled dtb files.

Create Custom Layer

To persist your developed changes and extend our BSP the best way is to create your own layer.

Use bitbake-layers to create a new layer.

bitbake-layers create-layer ../sources/meta-custom

This creates an empty example layer for you:

../sources/meta-custom/
├── conf
│   └── layer.conf
├── COPYING.MIT
├── README
└── recipes-example
    └── example
        └── example_0.1.bb

3 directories, 4 files

To make your layer available, add it to conf/bblayers.conf inside your build-directory.

(...)
BBLAYERS += "${BSPDIR}/sources/meta-karo-nxp"
BBLAYERS += "${BSPDIR}/sources/meta-karo-nxp-distro"
BBLAYERS += "${BSPDIR}/sources/meta-custom"

Append Kernel Recipe

You can remove the recipes-example folder inside your custom layer. Instead add a folder recipes-kernel with different subdirectories.

rm -rf ../sources/meta-custom/recipes-example/
mkdir -p ../sources/meta-custom/recipes-kernel/linux/linux-imx/patches
mkdir ../sources/meta-custom/recipes-kernel/linux/linux-imx/mx8

Now create the *.bbappend file to extend the kernel recipe.

touch ../layers/meta-custom/recipes-kernel/linux/linux-imx_%.bbappend

The content of linux-imx_%.bbappend could be something like this:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}/patches:${THISDIR}/${PN}:"
SRC_URI_append = " \
    file://custom_defconfig;subdir=git/arch/arm64/configs \
      file://0001-custom-magic-kernel-source.patch \
"

SRC_URI_append_mx8 = " \
      file://dts/freescale/imx8mm-tx8m-1610-customboard.dts;subdir=git/arch/arm64/boot \
"

KBUILD_DEFCONFIG_tx8m-1610 = "custom_defconfig"

KERNEL_DEVICETREE_append_tx8m-1610 = " \
    freescale/imx8mm-tx8m-1610-customboard.dtb \
"

The files in your custom-layer then would look like this:

../sources/meta-custom/
├── conf
│   └── layer.conf
├── COPYING.MIT
├── README
└── recipes-kernel
    └── linux
        ├── linux-imx
        │   ├── mx8
        │   │   ├── custom_defconfig
        │   │   └── dts
        │   │       └── freescale
        │   │           └── imx8mm-tx8m-1610-customboard.dts
        │   └── patches
        │       └── 0001-custom-magic-kernel-source.patch
        └── linux-imx_%.bbappend

8 directories, 7 files

Tip

Build your modified Kernel Recipe.

bitbake linux-imx

This will compile and deploy your modified Kernel and additionally the Devicetree you added.

Note

The way you expanded our kernel recipe, you can customize any recipe inside the BSP. You can use our layers as a reference if unsure what you can do.

You can also add new recipes.

Create Custom Image

To add a custom image you can add a new recipe under recipes-core/images. Your custom layer will then look like this:

../sources/meta-custom/
├── conf
│   └── layer.conf
├── COPYING.MIT
├── README
├── recipes-core
│   └── images
│       └── custom-image.bb
└── recipes-kernel
    └── linux
        ├── linux-imx
        │   ├── mx8
        │   │   ├── custom_defconfig
        │   │   └── dts
        │   │       └── freescale
        │   │           └── imx8mm-tx8m-1610-customboard.dts
        │   └── patches
        │       └── 0001-custom-magic-kernel-source.patch
        └── linux-imx_%.bbappend

10 directories, 8 files

The custom-image.bb below would include the karo-image-weston as basis and additionally add the pip3 python package manager.

1
2
3
4
5
6
7
SUMMARY = "A custom image with Weston desktop"

require recipes-core/images/karo-image-weston.bb

IMAGE_INSTALL_append = " \
                       python3-pip \
"

Tip

Build your custom image.

bitbake custom-image

With this example you would get the desired weston desktop image with included pip3.