i.MX release layer
• meta-fsl-bsp-release
• meta-bsp - updates for meta-freescale, poky, and meta-openembedded layers
• meta-sdk - updates for meta-freescale-distros
Yocto Project community layers
• meta-freescale: provides support for the base and for i.MX Arm
®
reference boards.
• meta-freescale-3rdparty: provides support for 3rd party and partner boards.
• meta-freescale-distro: additional items to aid in development and exercise board capabilities.
• fsl-community-bsp-base: often renamed to base. Provides base configuration for FSL Community BSP.
• meta-openembedded: Collection of layers for the OE-core universe. See layers.openembedded.org/.
• poky: basic Yocto Project items in Poky. See the Poky README for details.
• meta-browser: provides several browsers.
• meta-qt5: provides Qt5.
References to community layers in this document are for all the layers in Yocto Project except meta-fsl-bsp-release. i.MX
boards are configured in the meta-fsl-bsp-release and meta-freescale layers. This includes U-Boot, the Linux kernel, and
reference board-specific details.
i.MX provides an additional layer called the i.MX BSP Release, named meta-fsl-bsp-release, to integrate a new i.MX release
with the FSL Yocto Project Community BSP. The meta-fsl-bsp-release layer aims to release the updated and new Yocto
Project recipes and machine configurations for new releases that are not yet available on the existing meta-freescale and
meta-freescale-distro layers in the Yocto Project. The contents of the i.MX BSP Release layer are recipes and machine
configurations. In many test cases, other layers implement recipes or include files and the i.MX release layer provides
updates to the recipes by either appending to a current recipe, or including a component and updating with patches or source
locations. Most i.MX release layer recipes are very small because they use what the community has provided and update
what is needed for each new package version that is unavailable in the other layers.
The i.MX BSP Release layer also provides image recipes that include all the components needed for a system image to boot,
making it easier for the user. Components can be built individually or through an image recipe, which pulls in all the
components required in an image into one build process.
The i.MX kernel and U-Boot releases are accessed through i.MX public git servers. However, several components are
released as packages on the i.MX mirror. The package-based recipes pull files from the i.MX mirror instead of a git location
and generate the package needed.
All packages which are released as binary are built with hardware floating point enabled as specified by the
DEFAULTTUNE defined in each machine configuration file. Software floating point packages are not provided starting with
the jethro releases.
Release L4.14.98-2.0.0_ga is released for Yocto Project 2.5 (Sumo). The same recipes for Yocto Project 2.5 are going to be
upstreamed and made available on the next release of the Yocto Project release. The Yocto Project release cycle lasts roughly
six months.
The recipes and patches in meta-fsl-bsp-release are upstreamed to the community layers. After that is done for a particular
component, the files in meta-fsl-bsp-release are no longer needed and the FSL Yocto Project Community BSP will provide
support. The community supports i.MX reference boards, community boards, and third-party boards. A complete list can be
found at freescale.github.io/doc/release-notes/2.2/index.html#document-bsp-scope. All board references in this document are
related to the i.MX machine configuration files only.
1.1
End user licence agreement
During the setup environment process of the Freescale Yocto Project Community BSP, the NXP End User License
Agreement (EULA) is displayed. To continue to use the i.MX Proprietary software, users must agree to the conditions of this
license. The agreement to the terms allows the Yocto Project build to untar packages from the i.MX mirror.
Overview
i.MX Yocto Project User's Guide, Rev. L4.14.98-2.0.0_ga, 04/2019
2 NXP Semiconductors