Git Server Overview

The relevant repositories are hosted on a public GitLab server at You can find all public repositories here.

The software environment consists of several parts described below.

KED Yocto Core Repository


The Yocto core repository bundles some documentation and useful scripts to initialize and manage Yocto-builds for Kontron hardware. Cloned to your local file system, the yocto-ktn directory is used as a root directory for the build environment.

Directory Tree (summary)

├── docs          # some generic documentation sources (e.g. for this page)
├── layers        # empty directory to store meta-layers
├── scripts       # scripts to automate certain tasks
└── init-env      # this is a script to initialize the build environment

KED Yocto Build Repositories

The build repositories contain the configuration for a specific Yocto build. It defines the layers and revisions used. For a list of available build repositories, look for the projects prefixed with build- here. The build repositories are cloned to the yocto-ktn directory.

After finishing the build, the build directory also holds the tmp subdirectory with all the intermediate and final build results and products.

Directory Tree (summary)

├── ci                 # scripts and config for the KED CI builds
├── conf               # configuration directory
|   ├── local.conf     # contains local build settings (usually not tracked by git)
|   ├── bblayers.conf  # defines the directories parsed by bitbake
|   └── repo.conf      # defines the repositories handled by 'init-env' and
|                      # 'meta-*' scripts
└── docs               # build-/platform-specific documentation sources

KED Yocto Meta Layers

The KED Yocto meta layers, together with other layers provided by the SoC vendors and the OE community, contain the actual metadata for everything that is put into the resulting BSP.

In the KED build system all layers are put into the yocto-ktn/layers directory.


This layer contains configuration for the ktn distribution, generic recipes for KED applications, modifications and appends.
For all BSP versions based on the Rocko-branch and earlier, this layer is the only layer provided by KED and contains only i.MX6-based machines. Later BSP releases use a different scheme (see below).


Directory Tree (summary)

├── classes           # OE Metadata classes (.bbclass)
├── conf              # OE Metadata configuration (layer, distro, machines)
├── freescale-layer   # OE Metadata depending on the meta-freescale layer
├── networking-layer  # OE Metadata depending on the meta-networking layer
├── qt5-layer         # OE Metadata depending on the meta-qt5 layer
├── swupdate          # OE Metadata depending on the meta-swupdate layer
└── recipes-*         # OE Metadata recipes (.bb, .bbappend)

meta-ktn-* (only for BSPs based on "Thud"-branch and later)

From BSP releases based on the "Thud"-branch and later, meta-ktn is only used for platform-agnostic meta data and additional layers prefixed with meta-ktn- are used for platform-specific support (e.g. machine configurations).





Directory Tree (summary)

├── conf         # OE Metadata configuration (layer, distro, machines)
├── qt5-layer    # OE Metadata depending on the meta-qt5 layer
├── swupdate     # OE Metadata depending on the meta-swupdate layer
├── recipes-*    # OE Metadata recipes (.bb, .bbappend)
└── wic          # configuration for the OE Image Creator (Wic)

KED Customer Repositories

The default repositories to build BSPs for demo and evaluation hardware are public and require no authentication. Customer-specific repositories might be private and need an user account on the GitLab server. To gain access to such repositories please request a useraccount on the Kontron Electronics GitLab server. We recommend to use SSH and authentication with keys.


The generic public documentation can be found in the yocto-ktn repository (see above). Further platform-specific documentation are located in the docs directories inside the corresponding build repositories (see above).

All documentation is written in the Markdown markup language and is rendered to HTML by mkdocs.