Page Comparison

...

This wiki shows how to create a custom layer in an open source Xilinx Yocto flow.  After creating the layer, it provides an example of creating your own machine based on a ZCU102 configuration.

Releases Supported

Xilinx Yocto rel-v2018.1 and later (Rocko 2.4)

Prerequisites

Yocto Supported Linux Distro

• Dedicated or virtual Linux machineBare-metal Linux or Virtual Machine
• Yocto Project Reference Manual: Supported Linux DistributionsDocumentation

Xilinx Tools Dependencies

...

Note
These dependencies are not required for rel-v2018.

...

3 and later releases.

• Install xvfb (X virtual framebuffer) see UG1144 Table 2-1
• XSDK or XSCT Installation (required for meta-xilinx-tools layer)

Xilinx Open Source Yocto Installation

• How to build images through yocto

• Install and Build with Xilinx Yocto

Creating Your Custom Layer

You may create your custom layer manually by copying an existing layer.conf, however, Yocto provides some helper scripts to automate it.  The bitbake-layers create-layer script will generate a base layer with a default priority of 6.  Once the layer is created, you can either add the layer to bblayers.conf manually or use the bitbake-layers add-layer to automate it.  Note that adding it manually will be faster, but may increase the likelihood of typos or syntax errors.  The sequence below is an example of how to apply these scripts.  You may cut-and-paste the commands below into a local script to further automate this flow.  The resulting layer.conf and bblayers.conf are shown below.

Setup the Bitbake environment.

source setupsdk
# Optional: MakeBackup alocal.conf backupand copy of bblayers.conf
cp conf/bblayerslocal.conf conf/bblayerslocal.conf.bk
# Optional: Make a backup copy of local.conf
cp conf/localbblayers.conf conf/localbblayers.conf.bk
# Add a default MACHINE in local.conf or specify on the command line for bitbake-layers
echo 'MACHINE ?= "zcu102-zynqmp"' >> conf/local.conf
# Create your layer in the sources directory
cd ../sources
bitbake-layers create-layer meta-$LAYER
# Add new layer with bitbake-layers or edit bblayers.conf manually
cd ../build
bitbake-layers add-layer ../sources/meta-$LAYER
# Create your custom layer directory structure
cd ../sources/meta-

Create your custom layer.

LAYER=$ROOT/sources/meta-example
bitbake-layers create-layer $LAYER
mkdir -p $LAYER/{conf/machine ,recipes-kernel/linux -xlnx,recipes-bsp/{u-boot/u-boot-xlnx
mkdir -p recipes-bsp/,device-tree/files}}
recipes-bsp/hdf/files recipes-bsp/fsbl/files recipes-bsp/pmu-firmware/files

bitbake-layers add-layer $LAYER

Custom Layer Directory Structure

After the directory structure is created, you can begin populating the layer with recipes, bbappends, patches, cfg fragments, machine configs, etc.  The example.bb recipe is an artifact of the create-layer and can be safely deleted.  You can continue expanding your layer to include recipes for custom BSPs, applications and other open source components or stacks.  At this point, it's pretty straight forward to put your layer under Git control.

# We have a conf and classes directory, add to BBPATH
BBPATH .= ":${LAYERDIR}"

# We have recipes-* directories, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
            ${LAYERDIR}/recipes-*/*/*.bbappend"

BBFILE_COLLECTIONS += "meta-example"
BBFILE_PATTERN_meta-example = "^${LAYERDIR}/"
BBFILE_PRIORITY_meta-example = "6"

LCONF_VERSION = "7"

BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
  /home/emil/yocto/sources/core/meta \
  /home/emil/yocto/sources/core/meta-poky \
<...>
  /home/emil/yocto/sources/core/../meta-xilinx/meta-xilinx-bsp \
  /home/emil/yocto/sources/core/../meta-xilinx/meta-xilinx-contrib \
  /home/emil/yocto/sources/core/../meta-xilinx-tools \
  /home/emil/yocto/sources/core/../meta-petalinux \
  /home/emil/yocto/sources/core/../meta-virtualization \
  /home/emil/yocto/sources/core/../meta-openamp \
  /home/emil/yocto/sources/meta-example \
  "

BBLAYERS_NON_REMOVABLE ?= " \
    /home/emil/yocto/sources/core/meta \
"

Custom Layer Directory Structure

After the directory structure is created, you can begin populating the layer with recipes, bbappends, patches, cfg fragments, machine configs, etc.  The example.bb recipe is an artifact of the create-layer and can be safely deleted.  You can continue expanding your layer to include recipes for custom BSPs, applications and other open source components or stacks.  At this point, it's pretty straight forward to put your layer under Git control.

...

$ tree meta-example
meta-example
├── conf
│   ├── layer.conf
│   └── machine
├── COPYING.MIT
├── README
├── recipes-bsp
│   ├── device-tree
│   │   └── files
│   └── u-boot
│       └── u-boot-xlnx
├── recipes-example
│   └── example
│       └── example.bb
└── recipes-kernel
    └── linux-xlnx

Verify Your Layer

You can verify that your custom layer has been properly added to the Yocto build system by running bitbake-layers show-layers as shown below.

...

require conf/machine/zcu102-zynqmp.conf

Now you can build bitbake your new machine by specifying the MACHINE variable on the bitbake command line.

$ MACHINE=example-zcu102-zynqmp bitbake petalinux-image-minimal

Related Links

Install and Build with Xilinx Yocto

Adding a Hardware Platform to a Xilinx Yocto Layer

Customizing Device Trees in Xilinx Yocto

Xilinx Yocto Builds without an Internet Connection

References

Yocto Project Mega-Manual (2.4.4)Documentation