Introduction

This document is the release notes for the FSL Community BSP 2.4, which is the result of a community effort to improve Freescale’s SoC support for OpenEmbedded and Yocto Project.

Defining the FSL Community BSP

The FSL Community BSP is a community-driven project to provide and maintain Board Support Package (BSP) metadata layers for use in OpenEmbedded and Yocto Project with Freescale’s SoCs.

The FSL Community BSP follows Yocto Project’s release schedule and branch naming (since release 1.3, denzil).

See the Yocto Project Release for details on the Yocto Project.

Motivation

The FSL Community BSP started with the goal of easing the use of OpenEmbedded and Yocto Project with Freescale’s SoCs and providing an example of how to assemble an easy-to-use platform as the basis for future products.

The FSL Community BSP provides:

  • common environment configuration;
  • multiple download layers with the use of repo;
  • common location for discussing Freescale SoCs, kernels, bootloaders, user space packages, (BSP in general), bugs, how-tos, and so on

What the FSL Community BSP is not

The FSL Community BSP does not have a paid support team. The members of this community have full-time jobs and work on the project in their spare time. Most of them are working with Freescale SoCs in their full-time job, so it means some of them can provide paid support if requested.

The provided source code is not intended to be a product in itself. It is a reference platform for people to build products with. Because of this, plan to have a development and test cycle for your product if you decide to base it on the FSL Community BSP.

The project is community-driven work, and it is NOT an official Freescale support channel.

What you can expect

  • You can expect help when you post a question, but please be patient. Wait for at least two days for a response. Most of the time, people do reply when they know an answer or have advice to offer. If you don’t receive a reply, then it may be due to no one in the community having an adequate response.
  • The stable branch is supported for six months after the release date (following the Yocto Project’s release schedule);
  • The upstreaming takes place as quickly as possible and any needed adjustment is going to be made accordingly.

What the community expects from you

The community does expect that you contribute back by:

  • replying when you know the answer to a question in the mailing list;
  • reviewing the patches sent to mailing list;
  • testing new patches that affect you directly or indirectly;
  • reporting bugs you may find;
  • upstreaming bug fixes;
  • upstreaming features that may be good for the community.

Upstreaming

The FSL Community BSP provides test images and demos in addition to the base BSP for Freescale reference boards and third-party boards. In addition to the BSP, a Linux-based operating system typically requires several other packages, such as ssh client/server, window managers, applications, and so on. These packages are not part of the BSP. In other words, the FSL Community BSP is used with applications, tools and metadata from other projects, such as OpenEmbedded and Poky.

The FSL Community BSP always offers a stable version and a development version. You may face errors that are not caused by FSL Community BSP’s layers but instead by OpenEmbedded’s or Poky’s metadata. In this case, the error must be fixed in its layer.

The following image shows the upstream levels:

Main branch names

  • master-next: this branch is used to keep the patches to be built by the autobuilder for the very first test build. Do not expect to have a clear merging schedule, or to have a stable project when working with the master-next branch;
  • master: this is the branch where development takes place. Any new feature or bug fix must be merged here first. This is the development of the next stable branch;
  • rocko: the latest stable branch. This branch only accepts bug fixes, and is supported for 6 months after the release date.

There are other branches available, and they are the previous stable branches. They are kept online for users’ convenience, and you should not expect backports or bug fixes.

Upstream cycle

In addition to the normal Yocto Project upstream process, there is also a BSP upstream cycle.

The BSP upstream cycle starts just after a Freescale Official Release is published in git.freescale.com. The patches to adapt the recipes from meta-fsl-bsp-release are sent out for review to the meta-freescale mailing list and are merged in the meta-freescale, meta-freescale-3rdparty or meta-freescale-distro layers or upstreamed to Yocto Project accordingly.

A more detailed step-by-step process is shown below:

  1. New Freescale Official Release is published;
  2. The patches are sent to meta-freescale;
  3. After the review process, the patches are merged in the proper layer’s master-next branch;
  4. Source code is built by the autobuilder;
  5. After one week in master-next, it is merged in master;
  6. Freescale internally bases the next Freescale Official Release from the community source code;
  7. Back to step 1.

The result is that Freescale uses the FSL Community BSP source code with its bug fixes, improvements, and any new features to create the next Freescale Official Release.

Freescale uses the latest stable branch from Yocto Project to base the next Freescale Official Release. When this release is published, it is rebased and reworked to be merged in the current development branch.

The differences between FSL Community BSP and Freescale Official Release

The goal for each project is different. See below for the main points of divergence.

Freescale Official Release

The Freescale Official Release is intended to provide a static base for Freescale to test and validate the BSP modules with Freescale evaluation boards, and it is developed internally by Freescale. The set of supported boards vary from release to release and is listed in the Freescale Official Release notes for the specific version. The release points to a static revision of every included layer. Therefore, the release does not receive updates and bug fixes.

FSL Community BSP

The FSL Community BSP is a reference system that can be used as a base for products and is an open project that accepts contributions from the community. It supports a wide range of boards which range from Freescale evaluation boards (meta-freescale layer) to third-party boards (meta-freescale-3rdparty). The release is a “moving target”, so there are updates on top of the released source code, such as the addition of new features and bug fixes.

Comparative between Freescale Official Release and FSL Community BSP
  Freescale Official Release FSL Community BSP
Intended use Reference system for BSP modules test and validation on Freescale Reference Boards Reference system for use as base for any project for all supported boards
Code Static. Only include any bug fixes on the upcoming release Updates. Receives bug fixes and has security issues fixed often
Contribution Indirect contribution via FSL Community BSP. After revision, contribution may be merged in upcoming release Open, everyone is welcome to contribute to the project
Board Support Limited, as it supports just the Freescale evaluation boards listed in the Release Notes Extended, as it supports both Freescale evaluation boards and 3rd party boards. See Supported Board List
Yocto Project Compatible No Yes
Support i.MX Community meta-freescale
Repository git.freescale.com github.com/Freescale

FSL Community BSP Scope

The scope of the FSL Community BSP includes the meta layers:

  • meta-freescale: provides the base support and Freescale ARM and PPC reference boards;
  • meta-freescale-3rdparty: provides support for 3rd party and partner boards;
  • meta-freescale-distro: provides distros support, images recipes, demo recipes, and packagegroups used to ease the development with Yocto Project.
  • Documentation: provides the source code for FSL Community BSP Release Notes (RN) and User Guide (UG).

Meta-freescale

Since the Yocto Project release 2.2 (Morty) the FSL Community BSP changed the meta layers names. You can see the announcement here.

The following table show the renaming upgrade path:

Krogoth Morty
meta-fsl-arm meta-freescale
meta-fsl-ppc meta-freescale
meta-fsl-arm-extra meta-freescale-3rdparty
meta-fsl-demos meta-freescale-distros

The meta-fsl-arm and meta-fsl-ppc meta layers are deprecated. The last release for these meta layers is krogoth. Do not expect any update to the layer other than critical bug-fixes. Meta-fsl-arm and meta-fsl-ppc must be replaced by meta-freescale.

The meta-freescale meta layer goal is to integrate the ARM and PPC SoC based source code from Freescale, it includes i.MX, Vybrid, QorIQ and Layerscape BSPs.

The meta-fsl-arm-extra now is meta-freescale-3rdparty, any local copy should work as there is a mirror set.

The meta-fsl-demos now is meta-freescale-distros, any local copy should work as there is a mirror set.

License

The FSL Community BSP is a project with the same licensing of most Yocto Project layers. It means the recipe file is under a certain license, and the source code used by that recipe is under another certain license (being it equal or not).

Most of FSL Community BSP’s metadata is under MIT license, however the extensive and accurate list of package’s license provided by the Yocto Project’s metadata can be generated with few commands, for detailed information on how license is handled by Yocto Project see the Reference Manual.

End User License Agreement (EULA)

Freescale releases basically two kind of packages, the open sourced packages use regular open source licenses (GPLv2 for example).

The close sourced packages are released under the Freescale License (known as EULA). Each package has a copy of EULA inside itself and a copy of the EULA text is also included inside meta-freescale root dir (sources/meta-freescale/EULA).

The FSL Community BSP handles the EULA acceptance by prompting user to read and accept EULA text at the very first environment setup. It is user’s duty to read and understand it before accepting it. After it is accepted the first time, it is assumed accepted in any other build.

Kernel Release Notes

The FSL Community BSP includes support for several kernel providers. Each machine may have a different Linux Kernel provider.

The FSL Community BSP is not responsible for the content of those kernels. Although we as community should feel empowered to submit bug fixes and new features for those projects.

See the respective Linux Kernel provider for your machine in section Linux Kernel.

Different Product SoC Families

Currently, the FSL Community BSP includes the following Product SoC Families:

  • i.MX Application Processors (imx): Regarding the i.MX Freescale Page: i.MX applications processors are multicore ARM®-based solutions for multimedia and display applications with scalability, high performance, and low power capabilities.
  • Vybrid Controller Solutions based on ARM® Cores (vybrid): Regarding the Vybrid Freescale Page: Vybrid controller solutions are built on an asymmetrical-multiprocessing architecture using ARM® cores as the anchor for the platform, and are ideal for many industrial applications.
  • Layerscape Architecture (ls): Regarding the Layerscape Freescale Page: delivers unprecedented efficiency and scale for the smarter, more capable networks of tomorrow.

Freescale groups a set of SoCs which target different markets in product families. Those are grouped according to their SoC features and internal hardware capabilities.

The Yocto Project’s tools have the required capabilities to differentiate the architectures and BSP components for the different SoC families. In this perspective, the FSL Community BSP can support a wide range of architectures and product lines which go across several markets.

For the FSL Community BSP, the different SoCs, from all product lines manufactured by Freescale, can be seen as different machines, thus easing the use of same architecture across different markets.

Supported Board List

Please, see the next table for the complete supported board list.

Supported machines in FSL Community BSP
Machine Name SoC Layer
apalis-imx6 Toradex Apalis iMX6Q/D i.MX6Q meta-freescale-3rdparty
cfa10036 Crystalfontz CFA-10036 i.MX28 meta-freescale-3rdparty
cfa10037 Crystalfontz CFA-10037 i.MX28 meta-freescale-3rdparty
cfa10049 Crystalfontz CFA-10049 i.MX28 meta-freescale-3rdparty
cfa10055 Crystalfontz CFA-10055 i.MX28 meta-freescale-3rdparty
cfa10056 Crystalfontz CFA-10056 i.MX28 meta-freescale-3rdparty
cfa10057 Crystalfontz CFA-10057 i.MX28 meta-freescale-3rdparty
cfa10058 Crystalfontz CFA-10058 i.MX28 meta-freescale-3rdparty
cgtqmx6 Congatec QMX6 Evaluation board i.MX6 Q/DL meta-freescale-3rdparty
cm-fx6 CompuLab CM-FX6 i.MX6 Q/DL meta-freescale-3rdparty
colibri-imx6 Toradex Colibri iMX6DL/S i.MX6DL meta-freescale-3rdparty
colibri-imx7 Toradex Colibri iMX7D/S i.MX 7Dual / i.MX 7Solo meta-freescale-3rdparty
colibri-vf Toradex Colibri VF50/VF61 VF500/VF610 meta-freescale-3rdparty
cubox-i SolidRun CuBox-i and HummingBoard i.MX6 Q/DL meta-freescale-3rdparty
imx233-olinuxino-maxi OLIMEX iMX233-OLinuXino-Maxi i.MX23 meta-freescale-3rdparty
imx233-olinuxino-micro OLIMEX iMX233-OLinuXino-Micro i.MX23 meta-freescale-3rdparty
imx233-olinuxino-mini OLIMEX iMX233-OLinuXino-Mini i.MX23 meta-freescale-3rdparty
imx233-olinuxino-nano OLIMEX iMX233-OLinuXino-Nano i.MX23 meta-freescale-3rdparty
imx23evk NXP i.MX23 Evaluation Kit i.MX23 meta-freescale
imx25pdk NXP i.MX25 Evaluation Kit i.MX25 meta-freescale
imx28evk NXP i.MX28 Evaluation Kit i.MX28 meta-freescale
imx51evk NXP i.MX51 Evaluation Kit i.MX51 meta-freescale
imx53ard NXP i.MX53 SABRE Automotive Board i.MX53 meta-freescale
imx53qsb NXP i.MX53 Quick Start Board i.MX53 meta-freescale
imx6dl-riotboard RIoTboard i.MX6S meta-freescale-3rdparty
imx6q-dms-ba16 Advantech DMS BA16 i.MX6Q meta-freescale-3rdparty
imx6qdl-variscite-som Variscite i.MX6Q/DL VAR-SOM-MX6 i.MX6Q/DL meta-freescale-3rdparty
imx6qdlsabreauto NXP i.MX6QP/Q/DL SABRE Automotive i.MX6QP/Q/DL meta-freescale
imx6qdlsabresd NXP i.MX6QP/Q/DL SABRE Smart Device i.MX6QP/Q/DL meta-freescale
imx6qsabrelite Boundary Devices i.MX6Q SABRE Lite i.MX6Q meta-freescale-3rdparty
imx6sl-warp WaRP i.MX6SL meta-freescale-3rdparty
imx6slevk NXP i.MX6SL Evaluation Kit i.MX6SL meta-freescale
imx6sllevk Freescale i.MX6SLL Evaluation Kit i.MX6SLL meta-freescale
imx6sxsabreauto NXP i.MX6SoloX Sabre Automotive i.MX6SX meta-freescale
imx6sxsabresd NXP i.MX6SoloX SabreSD i.MX6SX meta-freescale
imx6ul-pico-hobbit Hobbitboard (PICO-IMX6UL) i.MX6UL meta-freescale-3rdparty
imx6ul-pico-pi PICO-PI (PICO-IMX6UL) i.MX6UL meta-freescale-3rdparty
imx6ulevk NXP i.MX6UL Evaluation Kit i.MX6UL meta-freescale
imx6ullevk Freescale i.MX6ULL Evaluation Kit i.MX6ULL meta-freescale
imx7d-pico IMX7D-PICO i.MX7D meta-freescale-3rdparty
imx7dsabresd NXP i.MX7D SABRE Smart Device i.MX7D meta-freescale
imx7s-warp WaRP7 i.MX7S meta-freescale-3rdparty
imx7ulpevk NXP i.MX7ULP Evaluation Kit i.MX7ULP meta-freescale
ls1012afrdm NXP LS1012AFRDM board LSCH2 meta-freescale
ls1012afrdm-32b NXP LS1012AFRDM board LSCH2 meta-freescale
ls1012ardb NXP LS1012ARDB board LSCH2 meta-freescale
ls1012ardb-32b NXP LS1012ARDB board LSCH2 meta-freescale
ls1021atwr NXP LS1021ATWR board ls102xa meta-freescale
ls1043ardb NXP LS1043ARDB board LSCH2 meta-freescale
ls1043ardb-32b NXP LS1043ARDB-32B LSCH2 meta-freescale
ls1046ardb NXP LS1046ARDB LSCH2 meta-freescale
ls1046ardb-32b NXP LS1046ARDB LSCH2 meta-freescale
ls1088ardb NXP LS1088ARDB LSCH3 meta-freescale
ls2080ardb NXP LS2080ARDB board LSCH3 meta-freescale
ls2088ardb NXP LS2088ARDB LSCH3 meta-freescale
m28evk DENX M28 SoM Evaluation Kit i.MX28 meta-freescale-3rdparty
m53evk DENX M53 SoM Evaluation Kit i.MX53 meta-freescale-3rdparty
nitrogen6sx Boundary Devices Nitrogen6SX i.MX6SX meta-freescale-3rdparty
nitrogen6x Boundary Devices Nitrogen6X i.MX6 Q/DL meta-freescale-3rdparty
nitrogen6x-lite Boundary Devices Nitrogen6X Lite i.MX6S meta-freescale-3rdparty
nitrogen7 Boundary Devices Nitrogen7 i.MX7D meta-freescale-3rdparty
pcm052 Phytec phyCORE Vybrid Development Kit vf60 meta-freescale-3rdparty
tx6q-10x0 Ka-Ro electronics i.MX6Q TX6Q Computer-On-Module i.MX6Q meta-freescale-3rdparty
tx6q-11x0 Ka-Ro electronics i.MX6Q TX6Q Computer-On-Module i.MX6Q meta-freescale-3rdparty
tx6s-8034 Ka-Ro electronics i.MX6S TX6S Computer-On-Module i.MX6S meta-freescale-3rdparty
tx6s-8035 Ka-Ro electronics i.MX6S TX6S Computer-On-Module i.MX6S meta-freescale-3rdparty
tx6u-8033 Ka-Ro electronics i.MX6DL TX6DL Computer-On-Module i.MX6DL meta-freescale-3rdparty
tx6u-80x0 Ka-Ro electronics i.MX6DL TX6DL Computer-On-Module i.MX6DL meta-freescale-3rdparty
tx6u-81x0 Ka-Ro electronics i.MX6DL TX6DL Computer-On-Module i.MX6DL meta-freescale-3rdparty
ventana i.MX6Q/DL Ventana Platform i.MX6Q/DL meta-freescale-3rdparty
wandboard Wandboard i.MX6 Wandboard QuadPlus/Quad/Dual/Solo i.MX6QP/Q/DL meta-freescale-3rdparty

Machine Maintainers

Since FSL Community BSP Release 1.6 (Daisy), the maintainer field in machine configuration files of meta-freescale and meta-freescale-3rdparty is mandatory for any new board to be added.

So now on, every new board must have someone assigned as maintainer. This ensures, in long term, all boards with a maintainer assigned. Current orphan boards are not going to be removed unless it causes maintenance problem and the fix is not straightforward.

The maintainer duties:
  • The one with casting vote when a deadlock is faced.
  • Responsible to keep that machine working (that means, booting and with some stability) Keep kernel, u-boot updated/tested/working.
  • Keep release notes updated
  • Keep test cycle updated
  • Keep the most usual images building and booting

When a build error is detected, the maintainer will “fix” it. For those maintainers with kernel control (meta-freescale-3rdparty), it is expected that they properly fix the kernel issue (when it’s a kernel issue). However, anything out of community control should be worked around anyway.

Machines with maintainers

Machines with maintainers
Machine Name
apalis-imx6 Toradex Apalis iMX6Q/D
cfa10036 Crystalfontz CFA-10036
cfa10037 Crystalfontz CFA-10037
cfa10049 Crystalfontz CFA-10049
cfa10055 Crystalfontz CFA-10055
cfa10056 Crystalfontz CFA-10056
cfa10057 Crystalfontz CFA-10057
cfa10058 Crystalfontz CFA-10058
cgtqmx6 Congatec QMX6 Evaluation board
cm-fx6 CompuLab CM-FX6
colibri-imx6 Toradex Colibri iMX6DL/S
colibri-imx7 Toradex Colibri iMX7D/S
colibri-vf Toradex Colibri VF50/VF61
cubox-i SolidRun CuBox-i and HummingBoard
imx23evk NXP i.MX23 Evaluation Kit
imx25pdk NXP i.MX25 Evaluation Kit
imx28evk NXP i.MX28 Evaluation Kit
imx51evk NXP i.MX51 Evaluation Kit
imx53ard NXP i.MX53 SABRE Automotive Board
imx53qsb NXP i.MX53 Quick Start Board
imx6dl-riotboard RIoTboard
imx6q-dms-ba16 Advantech DMS BA16
imx6qdl-variscite-som Variscite i.MX6Q/DL VAR-SOM-MX6
imx6qdlsabreauto NXP i.MX6QP/Q/DL SABRE Automotive
imx6qdlsabresd NXP i.MX6QP/Q/DL SABRE Smart Device
imx6qsabrelite Boundary Devices i.MX6Q SABRE Lite
imx6sl-warp WaRP
imx6slevk NXP i.MX6SL Evaluation Kit
imx6sllevk Freescale i.MX6SLL Evaluation Kit
imx6sxsabreauto NXP i.MX6SoloX Sabre Automotive
imx6sxsabresd NXP i.MX6SoloX SabreSD
imx6ul-pico-hobbit Hobbitboard (PICO-IMX6UL)
imx6ulevk NXP i.MX6UL Evaluation Kit
imx6ullevk Freescale i.MX6ULL Evaluation Kit
imx7d-pico IMX7D-PICO
imx7dsabresd NXP i.MX7D SABRE Smart Device
imx7s-warp WaRP7
imx7ulpevk NXP i.MX7ULP Evaluation Kit
ls1012afrdm-32b NXP LS1012AFRDM board
ls1012ardb NXP LS1012ARDB board
ls1021atwr NXP LS1021ATWR board
ls1043ardb NXP LS1043ARDB board
ls1043ardb-32b NXP LS1043ARDB-32B
ls1046ardb NXP LS1046ARDB
ls1088ardb NXP LS1088ARDB
ls2080ardb NXP LS2080ARDB board
ls2088ardb NXP LS2088ARDB
nitrogen6sx Boundary Devices Nitrogen6SX
nitrogen6x Boundary Devices Nitrogen6X
nitrogen6x-lite Boundary Devices Nitrogen6X Lite
nitrogen7 Boundary Devices Nitrogen7
pcm052 Phytec phyCORE Vybrid Development Kit
tx6q-11x0 Ka-Ro electronics i.MX6Q TX6Q Computer-On-Module
tx6s-8035 Ka-Ro electronics i.MX6S TX6S Computer-On-Module
tx6u-8033 Ka-Ro electronics i.MX6DL TX6DL Computer-On-Module
ventana i.MX6Q/DL Ventana Platform
wandboard Wandboard i.MX6 Wandboard QuadPlus/Quad/Dual/Solo

Machines without a maintainer

Machines without a maintainer
Machine Name
imx233-olinuxino-maxi OLIMEX iMX233-OLinuXino-Maxi
imx233-olinuxino-micro OLIMEX iMX233-OLinuXino-Micro
imx233-olinuxino-mini OLIMEX iMX233-OLinuXino-Mini
imx233-olinuxino-nano OLIMEX iMX233-OLinuXino-Nano
imx6ul-pico-pi PICO-PI (PICO-IMX6UL)
m28evk DENX M28 SoM Evaluation Kit
m53evk DENX M53 SoM Evaluation Kit

Software Architecture

SoC Hierarchy

The following tree shows the SoC hierarchy:

Linux Kernel

FSL Community BSP supports the following sources for Linux Kernel:

  • linux-advantech: linux-advantech version 4.1-r0.
  • linux-boundary: Linux kernel for Boundary Devices boards.
  • linux-cfa: Linux kernel for Crystalfontz boards.
  • linux-compulab: Linux kernel for CompuLab cm-fx6 boards.
  • linux-congatec: linux-congatec version 4.1.15-r0.
  • linux-denx: DENX mainline based Linux kernel.
  • linux-fslc: Linux kernel based on mainline kernel used by FSL Community BSP in order to provide support for some backported features and fixes, or because it was applied in linux-next and takes some time to become part of a stable version, or because it is not applicable for upstreaming.
  • linux-fslc-imx: Linux kernel based on NXP 4.1.15-1.2.0 GA release, used by FSL Community BSP in order to provide support for i.MX based platforms and include official Linux kernel stable updates, backported features and fixes coming from the vendors, kernel community or FSL Community itself.
  • linux-gateworks-imx: linux-gateworks-imx version 3.14-r0.
  • linux-imx: Linux Kernel provided and supported by NXP with focus on i.MX Family Reference Boards. It includes support for many IPs such as GPU, VPU and IPU.
  • linux-karo: Linux Kernel for Ka-Ro electronics TX Computer-On-Modules.
  • linux-qoriq: Linux Kernel for Freescale QorIQ platforms.
  • linux-timesys: Linux Kernel with added drivers and board support for Vybrid-based platforms.
  • linux-toradex: Linux kernel for Toradex Freescale i.MX based modules.
  • linux-variscite: linux-variscite version 4.1.15-r0.
  • linux-wandboard: Linux kernel for Wandboard.
  • linux-warp7: Linux kernel based on linux-fsl-imx branch 4.1-1.0.x-imx from FSL Community BSP with additional patches to cover devices specific on WaRP7 board.

As stated in Kernel Release Notes, FSL Community BSP is not responsible for the Linux Kernel content in any kernel provider. If you are looking for the feature list, supported devices, official way to get a support channel or how to report bug, please, see above where to get help, for each kernel provider.

  • linux-imx: provider, Freescale has a release notes document for each version released. This document has a list of known issues, new features, list of kernel arguments, and the linux-imx kernel scope for each Freescale Reference Board. This document is present into the Document Bundle provided by Freescale.

Default Linux Providers

The following table shows the default version of Linux Kernel provided by FSL Community BSP for each supported machine.

Default Linux kernel version for each supported machine
Board Kernel Provider Kernel Version
apalis-imx6 linux-toradex 4.1-2.0.x+git
cfa10036 linux-cfa 4.1.13
cfa10037 linux-cfa 4.1.13
cfa10049 linux-cfa 4.1.13
cfa10055 linux-cfa 4.1.13
cfa10056 linux-cfa 4.1.13
cfa10057 linux-cfa 4.1.13
cfa10058 linux-cfa 4.1.13
cgtqmx6 linux-congatec 4.1.15
cm-fx6 linux-compulab 3.14.28-cm-fx6
colibri-imx6 linux-toradex 4.1-2.0.x+git
colibri-imx7 linux-toradex 4.1-2.0.x+git
colibri-vf linux-toradex 4.4+git
cubox-i linux-fslc 4.14+git
imx233-olinuxino-maxi linux-fslc 4.14+git
imx233-olinuxino-micro linux-fslc 4.14+git
imx233-olinuxino-mini linux-fslc 4.14+git
imx233-olinuxino-nano linux-fslc 4.14+git
imx23evk linux-fslc 4.14+git
imx25pdk linux-fslc 4.14+git
imx28evk linux-fslc 4.14+git
imx51evk linux-fslc 4.14+git
imx53ard linux-fslc 4.14+git
imx53qsb linux-fslc 4.14+git
imx6dl-riotboard linux-fslc 4.14+git
imx6q-dms-ba16 linux-advantech 4.1-4.1-1.0.x-imx-dms-ba16
imx6qdl-variscite-som linux-variscite 4.1.15-1.1.0
imx6qdlsabreauto linux-fslc-imx 4.1-2.0.x+git
imx6qdlsabresd linux-fslc-imx 4.1-2.0.x+git
imx6qsabrelite linux-boundary 4.1.15-2.0.0-ga+yocto
imx6sl-warp linux-fslc-imx 4.1-2.0.x+git
imx6slevk linux-fslc-imx 4.1-2.0.x+git
imx6sllevk linux-imx 4.9.11-1.0.0
imx6sxsabreauto linux-fslc-imx 4.1-2.0.x+git
imx6sxsabresd linux-fslc-imx 4.1-2.0.x+git
imx6ul-pico-hobbit linux-fslc 4.14+git
imx6ul-pico-pi linux-fslc 4.14+git
imx6ulevk linux-fslc-imx 4.1-2.0.x+git
imx6ullevk linux-imx 4.9.11-1.0.0
imx7d-pico linux-fslc 4.14+git
imx7dsabresd linux-fslc-imx 4.1-2.0.x+git
imx7s-warp linux-warp7 4.1-4.1-1.0.x-imx-warp7
imx7ulpevk linux-imx 4.9.11-1.0.0
ls1012afrdm linux-qoriq 4.9
ls1012afrdm-32b linux-qoriq 4.9
ls1012ardb linux-qoriq 4.9
ls1012ardb-32b linux-qoriq 4.9
ls1021atwr linux-qoriq 4.9
ls1043ardb linux-qoriq 4.9
ls1043ardb-32b linux-qoriq 4.9
ls1046ardb linux-qoriq 4.9
ls1046ardb-32b linux-qoriq 4.9
ls1088ardb linux-qoriq 4.9
ls2080ardb linux-qoriq 4.9
ls2088ardb linux-qoriq 4.9
m28evk linux-fslc 4.14+git
m53evk linux-denx 3.9-master
nitrogen6sx linux-boundary 4.1.15-2.0.0-ga+yocto
nitrogen6x linux-boundary 4.1.15-2.0.0-ga+yocto
nitrogen6x-lite linux-boundary 4.1.15-2.0.0-ga+yocto
nitrogen7 linux-boundary 4.1.15-2.0.0-ga+yocto
pcm052 linux-timesys 3.13
tx6q-10x0 linux-karo 3.16-2015-09-18
tx6q-11x0 linux-karo 3.16-2015-09-18
tx6s-8034 linux-karo 3.16-2015-09-18
tx6s-8035 linux-karo 3.16-2015-09-18
tx6u-8033 linux-karo 3.16-2015-09-18
tx6u-80x0 linux-karo 3.16-2015-09-18
tx6u-81x0 linux-karo 3.16-2015-09-18
ventana linux-gateworks-imx 3.14-1.0.x-ga+yocto
wandboard linux-wandboard 4.1-2.0.x

Bootloaders

FSL Community BSP supports barebox and u-boot as bootloaders.

  • barebox: Barebox - a bootloader that inherits the best of U-Boot and the Linux kernel
  • u-boot-congatec: u-boot which includes support for Congatec Boards.
  • u-boot-fslc: U-Boot based on mainline U-Boot used by FSL Community BSP in order to provide support for some backported features and fixes, or because it was submitted for revision and it takes some time to become part of a stable version, or because it is not applicable for upstreaming.
  • u-boot-imx: i.MX U-Boot suppporting i.MX reference boards.
  • u-boot-karo: u-boot for Ka-Ro electronics TX Computer-On-Modules.
  • u-boot-qoriq: U-Boot provided by Freescale with focus on QorIQ boards
  • u-boot-toradex: U-Boot bootloader with support for Toradex Computer on Modules.
  • u-boot-variscite: U-Boot for Variscite i.MX6Q/DL VAR-SOM-MX6.

The following table shows the default bootloaders (and their versions) for the supported boards.

Default bootloader version for each supported machine
Board Bootloader Bootloader version
apalis-imx6 u-boot-toradex 2016.11+git
cfa10036 barebox 2015.10.0
cfa10037 barebox 2015.10.0
cfa10049 barebox 2015.10.0
cfa10055 barebox 2015.10.0
cfa10056 barebox 2015.10.0
cfa10057 barebox 2015.10.0
cfa10058 barebox 2015.10.0
cgtqmx6 u-boot-congatec 2016.01
cm-fx6 u-boot-fslc v2017.11+git
colibri-imx6 u-boot-toradex 2016.11+git
colibri-imx7 u-boot-toradex 2016.11+git
colibri-vf u-boot-toradex 2016.11+git
cubox-i u-boot-fslc v2017.11+git
imx233-olinuxino-maxi u-boot-fslc v2017.11+git
imx233-olinuxino-micro u-boot-fslc v2017.11+git
imx233-olinuxino-mini u-boot-fslc v2017.11+git
imx233-olinuxino-nano u-boot-fslc v2017.11+git
imx23evk u-boot-fslc v2017.11+git
imx25pdk u-boot-fslc v2017.11+git
imx28evk u-boot-fslc v2017.11+git
imx51evk u-boot-fslc v2017.11+git
imx53ard u-boot-fslc v2017.11+git
imx53qsb u-boot-fslc v2017.11+git
imx6dl-riotboard u-boot-fslc v2017.11+git
imx6q-dms-ba16 u-boot-fslc v2017.11+git
imx6qdl-variscite-som u-boot-variscite 2015.04
imx6qdlsabreauto u-boot-fslc v2017.11+git
imx6qdlsabresd u-boot-fslc v2017.11+git
imx6qsabrelite u-boot-fslc v2017.11+git
imx6sl-warp u-boot-fslc v2017.11+git
imx6slevk u-boot-fslc v2017.11+git
imx6sllevk u-boot-imx 2017.03-nxp/imx_v2017.03_4.9.11_1.0.0_ga
imx6sxsabreauto u-boot-imx 2017.03-nxp/imx_v2017.03_4.9.11_1.0.0_ga
imx6sxsabresd u-boot-fslc v2017.11+git
imx6ul-pico-hobbit u-boot-fslc v2017.11+git
imx6ul-pico-pi u-boot-fslc v2017.11+git
imx6ulevk u-boot-fslc v2017.11+git
imx6ullevk u-boot-imx 2017.03-nxp/imx_v2017.03_4.9.11_1.0.0_ga
imx7d-pico u-boot-fslc v2017.11+git
imx7dsabresd u-boot-fslc v2017.11+git
imx7s-warp u-boot-fslc v2017.11+git
imx7ulpevk u-boot-fslc v2017.11+git
ls1012afrdm u-boot-qoriq 2017.09+fslgit+fsl
ls1012afrdm-32b u-boot-qoriq 2017.09+fslgit+fsl
ls1012ardb u-boot-qoriq 2017.09+fslgit+fsl
ls1012ardb-32b u-boot-qoriq 2017.09+fslgit+fsl
ls1021atwr u-boot-qoriq 2017.09+fslgit+fsl
ls1043ardb u-boot-qoriq 2017.09+fslgit+fsl
ls1043ardb-32b u-boot-qoriq 2017.09+fslgit+fsl
ls1046ardb u-boot-qoriq 2017.09+fslgit+fsl
ls1046ardb-32b u-boot-qoriq 2017.09+fslgit+fsl
ls1088ardb u-boot-qoriq 2017.09+fslgit+fsl
ls2080ardb u-boot-qoriq 2017.09+fslgit+fsl
ls2088ardb u-boot-qoriq 2017.09+fslgit+fsl
m28evk u-boot-fslc v2017.11+git
m53evk u-boot-fslc v2017.11+git
nitrogen6sx u-boot-fslc v2017.11+git
nitrogen6x u-boot-fslc v2017.11+git
nitrogen6x-lite u-boot-fslc v2017.11+git
nitrogen7 u-boot-fslc v2017.11+git
pcm052 u-boot-fslc v2017.11+git
tx6q-10x0 u-boot-karo v2015.10-rc2+git
tx6q-11x0 u-boot-karo v2015.10-rc2+git
tx6s-8034 u-boot-karo v2015.10-rc2+git
tx6s-8035 u-boot-karo v2015.10-rc2+git
tx6u-8033 u-boot-karo v2015.10-rc2+git
tx6u-80x0 u-boot-karo v2015.10-rc2+git
tx6u-81x0 u-boot-karo v2015.10-rc2+git
ventana u-boot-gateworks-imx v2015.04+git
wandboard u-boot-fslc v2017.11+git

User Space Packages

There is a huge number of user space packages provided by the Yocto Project. The following table shows some version for few highlighted packages.

Main user space package versions
Package Board/SoC Family Version
gstreamer1.0 All 1.12.2
udev All 3.2.2

Freescale User Space Packages

This section shows the version package for each board. Those packages provide hardware acceleration for GPU or VPU, hardware optimization or some hardware test tools.

  • Hardware acceleration is achieved using a different core for processing some specific task. In this case, GPU or VPU.
  • Hardware optimization is achieved with some changes in source code in order to get a better performance for a specific task on a specific hardware. For example, audio decode made by software, but with optimizations for ARM.
  • Hardware-specific is applicable when the package was designed to be executed on a specific hardware, and it does not make sense on other hardware. For example, imx-test is a test package for imx boards. It can be cross-compiled for any other core, although it will only behave as expect if executed on imx boards.

The package version and variety varies on SoC Hierarchy. For example, machines with i.MX28 SoC does not have VPU, the recipe imx-vpu is not needed. There are differences, as well, in GPU support recipes.

Version by SoC Hierarchy

The following table shows the version of each package depending on the SoC Hierarchy.

User space package version by SoC hierarchy
Package name ls102xa mx28 mx5 mx6q / mx6dl mx6sl vf60
apptrk git
cst git git git git git git
devregs 1.0+AUTOINC+34ed402b92 1.0+AUTOINC+34ed402b92 1.0+AUTOINC+34ed402b92 1.0+AUTOINC+34ed402b92 1.0+AUTOINC+34ed402b92 1.0+AUTOINC+34ed402b92
directfb 1.7.7 1.7.7 1.7.7 1.7.7 1.7.7 1.7.7
directfb-examples 1.7.0 1.7.0 1.7.0 1.7.0 1.7.0 1.7.0
elftosb 10.12.01 10.12.01 10.12.01 10.12.01 10.12.01 10.12.01
firmware-imx 5.4 5.4 5.4 5.4 5.4 5.4
fsl-alsa-plugins 1.0.26 1.0.26
gpu-viv-bin-mx6q
gpu-viv-g2d
gst1.0-fsl-plugin
gstreamer1.0-plugins-imx 0.13.0 0.13.0
imx-kobs 5.5+git 5.5+git 5.5+git 5.5+git 5.5+git
imx-lib 5.8+AUTOINC+f5f14fc245 5.8+AUTOINC+f5f14fc245
imx-test 00.00.00 00.00.00 6.0+AUTOINC+fb250a795c 6.0+AUTOINC+fb250a795c 00.00.00
imx-uuc 0.5.1+git 0.5.1+git 0.5.1+git 0.5.1+git 0.5.1+git 0.5.1+git
imx-vpu 5.4.37 5.4.37
libfslcodec 4.2.1 4.2.1
libfslparser 4.2.1 4.2.1
libfslvpuwrap 1.0.68
libmcc 1.05.1
mqxboot 1.0.1
mxsldr 0.0.0+git 0.0.0+git 0.0.0+git 0.0.0+git 0.0.0+git 0.0.0+git
qe-ucode git
qemu-fsl
rcw git
xf86-video-imxfb
xf86-video-imxfb-vivante

Hardware relation by SoC Hierarchy

The following table shows how packages interact with hardware depending on the SoC Hierarchy

Hardware dependent packages
Package Name mx28 mx5 mx6 vf60
imx-test HW-specific HW-specific HW-specific
gst-fsl-plugin HW-specific HW-specific HW-specific
libfslcodec HW optimization HW acceleration HW acceleration
libfslparser HW optimization HW optimization HW optimization
imx-vpu HW acceleration HW acceleration
imx-lib HW acceleration HW acceleration
firmware-imx HW-specific HW-specific
mxsldr HW-specific
gpu-viv-g2d HW acceleration
xf86-video-imxfb-vivante HW acceleration
gpu-viv-bin-mx6q HW acceleration
directfb HW acceleration
directfb-examples HW acceleration
xf86-video-imxfb HW acceleration
amd-gpu-bin-mx51 HW acceleration
libz160 HW acceleration
amd-gpu-x11-bin-mx51 HW acceleration
libfslvpuwrap HW acceleration
fsl-alsa-plugins HW-specific
gstreamer1.0-plugins-imx HW acceleration
imx-uuc HW-specific HW-specific HW-specific
libmcc  
mqxboot HW-specific

PackageGroups and Images

The FSL Community BSP provides a list of PACKAGEGROUPS and images intended to ease the initial development of custom applications.

The main goal is not to provide a production solution, on the contrary, it should be seen as an example of package set for a specific IP development, and an example of initial generic development and test images.

PACKAGEGROUPS

The following list shows the current PACKAGEGROUPs available in Rocko when using FSL Community BSP.

You can understand what a PACKAGEGROUPS is and learn how to use it in Yocto Project Development Manual

  • packagegroup-fsl-gstreamer1.0: Package group used by FSL Community to provide audio, video, networking and debug GStreamer plugins with the required hardware acceleration (if supported by the SoC).
  • packagegroup-fsl-gstreamer1.0-full: Package group used by FSL Community to provide all GStreamer plugins from the base, good, and bad packages, as well as the ugly and libav ones if commercial packages are whitelisted, and plugins for the required hardware acceleration (if supported by the SoC).
  • packagegroup-fsl-mfgtool: Freescale Manufacturing Tool requirements.
  • packagegroup-fsl-tools-benchmark: Package group used by FSL Community to provide a set of benchmark applications.
  • packagegroup-fsl-tools-gpu: Package group used by FSL Community to add the packages which provide GPU support.
  • packagegroup-fsl-tools-gpu-external: Package group used by FSL Community to provide graphic packages used to test the several hardware accelerated graphics APIs including packages not provided by Freescale.
  • packagegroup-fsl-tools-testapps: Packagegroup used by FSL Community to provide a set of packages and utilities for hardware test.
  • packagegroup-imx-tools-audio: Set of audio tools for inclusion on images.

Images

The following images are provided by FSL Community BSP only. See the list of Yocto Project’s reference images in Yocto Project Reference Manual

  • fsl-image-machine-test: A console-only image that includes gstreamer packages, Freescale’s multimedia packages (VPU and GPU) when available, and test and benchmark applications.
  • fsl-image-mfgtool-initramfs: Small image to be used with Manufacturing Tool (mfg-tool) in a production environment.
  • fsl-image-multimedia: A console-only image that includes gstreamer packages and Freescale’s multimedia packages (VPU and GPU) when available for the specific machine.
  • fsl-image-multimedia-full: A console-only image that includes gstreamer packages and Freescale’s multimedia packages (VPU and GPU) when available for the specific machine.

Distros

The following distros are supported by FSL Community BSP.

  • fslc-framebuffer: Distro for Framebuffer graphical backend. This distro doesn’t include x11 and wayland features.
  • fslc-wayland: Distro for Wayland without X11. This distro include wayland feature but doesn’t has x11 support.
  • fslc-x11: Distro for X11 without wayland. This distro include x11 feature and doesn’ has wayland support.
  • fslc-xwayland: Distro for Wayland with X11. This distro include both wayland and x11 features.

NOTE: Poky’s distros are still available to use.

Test results

Freescale has a complete test cycle for the BSP released. It includes tests for Linux Kernel for the GPU package and for the VPU package (and all other package needed by the BSP, such as imx-lib).

The results and known issues, from Linux Kernel, GPU and VPU packages can be found in the Freescale Release Notes (Download tab of freescale.com/imx).

For boards from meta-freescale-3rdparty, the test cycle is performed by each mantainer.

Acknowledgements

The FSL BSP Community is a community effort of keeping and mantaining a Freescale boards/chips layer for the Yocto Project.

Rocko Source Code

The following people helped to construct the source code for the release:

Statistics for meta-freescale
-----------------------------

Processed 440 csets from 36 developers
7 employers found
A total of 14584 lines added, 47092 removed (delta -32508)

Developers with the most changesets
Chunrong Guo               165 (37.5%)
Fabio Berton                65 (14.8%)
Otavio Salvador             51 (11.6%)
Ting Liu                    25 (5.7%)
Zhenhua Luo                 20 (4.5%)
Tom Hochstein               19 (4.3%)
Yuqing Zhu                  16 (3.6%)
Daiane Angolini             11 (2.5%)
Jun Zhu                      9 (2.0%)
Max Krummenacher             7 (1.6%)
alexandra-ioana.safta@nxp.com    7 (1.6%)
Trevor Woerner               6 (1.4%)
Zongchun Yu                  5 (1.1%)
Oliver Graute                4 (0.9%)
Khem Raj                     3 (0.7%)
Bob Cochran                  3 (0.7%)
Dominic Sacré               3 (0.7%)
Gianfranco Costamagna        2 (0.5%)
Andreas Müller              2 (0.5%)
texierp                      1 (0.2%)
Ming Liu                     1 (0.2%)
Fabio Estevam                1 (0.2%)
Carlos Rafael Giani          1 (0.2%)
Hiraku Toyooka               1 (0.2%)
Vanessa Maegima              1 (0.2%)
Stefan Agner                 1 (0.2%)
Gary Bisson                  1 (0.2%)
Denis Pynkin                 1 (0.2%)
Ricardo Salveti              1 (0.2%)
Matt Madison                 1 (0.2%)
Mats Karrman                 1 (0.2%)
Mircea Pop                   1 (0.2%)
Gary Thomas                  1 (0.2%)
Neena Busireddy              1 (0.2%)
Mirza Krak                   1 (0.2%)
Thomas Perrot                1 (0.2%)

Developers with the most changed lines
Chunrong Guo              39902 (67.7%)
Tom Hochstein             6933 (11.8%)
Fabio Berton              5442 (9.2%)
Yuqing Zhu                3862 (6.6%)
Otavio Salvador           1034 (1.8%)
Jun Zhu                    387 (0.7%)
Ting Liu                   356 (0.6%)
Zhenhua Luo                193 (0.3%)
Bob Cochran                153 (0.3%)
Daiane Angolini            126 (0.2%)
Trevor Woerner              98 (0.2%)
Gianfranco Costamagna       84 (0.1%)
alexandra-ioana.safta@nxp.com   81 (0.1%)
Max Krummenacher            59 (0.1%)
Khem Raj                    43 (0.1%)
Neena Busireddy             38 (0.1%)
Ricardo Salveti             25 (0.0%)
Oliver Graute               20 (0.0%)
Hiraku Toyooka              15 (0.0%)
Dominic Sacré               9 (0.0%)
Andreas Müller              8 (0.0%)
Zongchun Yu                  7 (0.0%)
Carlos Rafael Giani          6 (0.0%)
Ming Liu                     5 (0.0%)
Matt Madison                 3 (0.0%)
texierp                      1 (0.0%)
Fabio Estevam                1 (0.0%)
Vanessa Maegima              1 (0.0%)
Stefan Agner                 1 (0.0%)
Gary Bisson                  1 (0.0%)
Denis Pynkin                 1 (0.0%)
Mats Karrman                 1 (0.0%)
Mircea Pop                   1 (0.0%)
Mirza Krak                   1 (0.0%)

Developers with the most lines removed
Chunrong Guo              24275 (51.5%)
Tom Hochstein             5765 (12.2%)
Yuqing Zhu                2078 (4.4%)
Fabio Berton               938 (2.0%)
Jun Zhu                    153 (0.3%)
Max Krummenacher            49 (0.1%)
Ting Liu                    43 (0.1%)
Matt Madison                 1 (0.0%)

Developers with the most signoffs (total 413)
Otavio Salvador            389 (94.2%)
Ting Liu                    19 (4.6%)
Tom Hochstein                1 (0.2%)
Cristian Stoica              1 (0.2%)
Yong Gan                     1 (0.2%)
Lauren Post                  1 (0.2%)
Zhenhua Luo                  1 (0.2%)

Developers with the most reviews (total 1)
Laszlo Agocs                 1 (100.0%)

Developers with the most test credits (total 0)

Developers who gave the most tested-by credits (total 0)

Developers with the most report credits (total 2)
Bertrand Jacquin             1 (50.0%)
Daiane Angolini              1 (50.0%)

Developers who gave the most report credits (total 2)
Otavio Salvador              1 (50.0%)
Chunrong Guo                 1 (50.0%)

Top changeset contributors by employer
NXP                        281 (63.9%)
O.S. Systems               116 (26.4%)
(Unknown)                   31 (7.0%)
(None)                       9 (2.0%)
Toradex                      1 (0.2%)
Boundary Devices             1 (0.2%)
(Consultant)                 1 (0.2%)

Top lines changed by employer
NXP                       51888 (88.1%)
O.S. Systems              6476 (11.0%)
(Unknown)                  391 (0.7%)
(None)                     141 (0.2%)
Toradex                      1 (0.0%)
Boundary Devices             1 (0.0%)

Employers with the most signoffs (total 413)
O.S. Systems               389 (94.2%)
NXP                         24 (5.8%)

Employers with the most hackers (total 36)
(Unknown)                   16 (44.4%)
NXP                         13 (36.1%)
O.S. Systems                 2 (5.6%)
(None)                       2 (5.6%)
Toradex                      1 (2.8%)
Boundary Devices             1 (2.8%)
(Consultant)                 1 (2.8%)


Statistics for meta-freescale-3rdparty
--------------------------------------

Processed 78 csets from 15 developers
7 employers found
A total of 1919 lines added, 2093 removed (delta -174)

Developers with the most changesets
Fabio Berton                19 (24.4%)
Max Krummenacher            15 (19.2%)
Otavio Salvador             10 (12.8%)
Gary Bisson                  8 (10.3%)
Tim Harvey                   7 (9.0%)
texierp                      4 (5.1%)
Trevor Woerner               3 (3.8%)
Alex de Cabo                 3 (3.8%)
Stefan Agner                 2 (2.6%)
Ian Coolidge                 2 (2.6%)
Ricardo Salveti              1 (1.3%)
Vanessa Maegima              1 (1.3%)
Ken Lin                      1 (1.3%)
Eric Nelson                  1 (1.3%)
Bhuvanchandra DV             1 (1.3%)

Developers with the most changed lines
Otavio Salvador           1272 (35.8%)
Ian Coolidge               766 (21.5%)
Max Krummenacher           492 (13.8%)
Fabio Berton               273 (7.7%)
Tim Harvey                 252 (7.1%)
Alex de Cabo               215 (6.0%)
Gary Bisson                106 (3.0%)
Ken Lin                     65 (1.8%)
Trevor Woerner              43 (1.2%)
Stefan Agner                34 (1.0%)
Vanessa Maegima             27 (0.8%)
texierp                      9 (0.3%)
Ricardo Salveti              1 (0.0%)
Eric Nelson                  1 (0.0%)
Bhuvanchandra DV             1 (0.0%)

Developers with the most lines removed
Otavio Salvador           1142 (54.6%)
Max Krummenacher           243 (11.6%)

Developers with the most signoffs (total 67)
Otavio Salvador             67 (100.0%)

Developers with the most reviews (total 0)

Developers with the most test credits (total 1)
Eric Nelson                  1 (100.0%)

Developers who gave the most tested-by credits (total 1)
Fabio Berton                 1 (100.0%)

Developers with the most report credits (total 0)

Developers who gave the most report credits (total 0)

Top changeset contributors by employer
O.S. Systems                29 (37.2%)
(Unknown)                   29 (37.2%)
Boundary Devices            10 (12.8%)
Toradex                      3 (3.8%)
Congatec AG                  3 (3.8%)
(None)                       3 (3.8%)
NXP                          1 (1.3%)

Top lines changed by employer
O.S. Systems              1545 (43.4%)
Boundary Devices           872 (24.5%)
(Unknown)                  820 (23.1%)
Congatec AG                215 (6.0%)
(None)                      43 (1.2%)
Toradex                     35 (1.0%)
NXP                         27 (0.8%)

Employers with the most signoffs (total 67)
O.S. Systems                67 (100.0%)

Employers with the most hackers (total 15)
(Unknown)                    6 (40.0%)
O.S. Systems                 2 (13.3%)
Boundary Devices             2 (13.3%)
Toradex                      2 (13.3%)
Congatec AG                  1 (6.7%)
(None)                       1 (6.7%)
NXP                          1 (6.7%)


Statistics for meta-freescale-distro
------------------------------------

Processed 8 csets from 3 developers
2 employers found
A total of 32 lines added, 7 removed (delta 25)

Developers with the most changesets
Fabio Berton                 4 (50.0%)
Otavio Salvador              3 (37.5%)
Vanessa Maegima              1 (12.5%)

Developers with the most changed lines
Vanessa Maegima             26 (74.3%)
Fabio Berton                 5 (14.3%)
Otavio Salvador              4 (11.4%)

Developers with the most lines removed
Otavio Salvador              3 (42.9%)

Developers with the most signoffs (total 5)
Otavio Salvador              5 (100.0%)

Developers with the most reviews (total 0)

Developers with the most test credits (total 0)

Developers who gave the most tested-by credits (total 0)

Developers with the most report credits (total 0)

Developers who gave the most report credits (total 0)

Top changeset contributors by employer
O.S. Systems                 7 (87.5%)
NXP                          1 (12.5%)

Top lines changed by employer
NXP                         26 (74.3%)
O.S. Systems                 9 (25.7%)

Employers with the most signoffs (total 5)
O.S. Systems                 5 (100.0%)

Employers with the most hackers (total 3)
O.S. Systems                 2 (66.7%)
NXP                          1 (33.3%)


Statistics for base
-------------------

Processed 3 csets from 2 developers
1 employers found
A total of 3 lines added, 3 removed (delta 0)

Developers with the most changesets
Kursad Oney                  2 (66.7%)
Daiane Angolini              1 (33.3%)

Developers with the most changed lines
Kursad Oney                  2 (66.7%)
Daiane Angolini              1 (33.3%)

Developers with the most lines removed

Developers with the most signoffs (total 0)

Developers with the most reviews (total 0)

Developers with the most test credits (total 0)

Developers who gave the most tested-by credits (total 0)

Developers with the most report credits (total 0)

Developers who gave the most report credits (total 0)

Top changeset contributors by employer
(Unknown)                    3 (100.0%)

Top lines changed by employer
(Unknown)                    3 (100.0%)

Employers with the most signoffs (total 0)

Employers with the most hackers (total 2)
(Unknown)                    2 (100.0%)


Statistics for Documentation
----------------------------

Processed 5 csets from 1 developers
1 employers found
A total of 368 lines added, 553 removed (delta -185)

Developers with the most changesets
Fabio Berton                 5 (100.0%)

Developers with the most changed lines
Fabio Berton               553 (100.0%)

Developers with the most lines removed
Fabio Berton               185 (33.5%)

Developers with the most signoffs (total 0)

Developers with the most reviews (total 0)

Developers with the most test credits (total 0)

Developers who gave the most tested-by credits (total 0)

Developers with the most report credits (total 0)

Developers who gave the most report credits (total 0)

Top changeset contributors by employer
O.S. Systems                 5 (100.0%)

Top lines changed by employer
O.S. Systems               553 (100.0%)

Employers with the most signoffs (total 0)

Employers with the most hackers (total 1)
O.S. Systems                 1 (100.0%)


Known Issues

ALL

  1. Fail to build imx-lib/imx-vpu/imx-test/gst-fsl-plugin when building against linux-fslc
  2. Weston/Wayland/Directb for SOC_FAMILY: imx5 or mxs or imx3 is not hardware accelerated and has not been tested.
  3. Hob is known to not work with with FSL Community BSP. Some of known issues are problems generating the SD Card images and handling the GPU drivers.

IMX28

  1. Touch screen (with x11 at least) is not completely calibrated
  2. mfgtools supported n FSL Community BSP does not include support for i.mx28 (but it´s easy to be included and your patch is appreciated)
  3. Pendrive is not automatically mounted, but once you mount it everything works fine

IMX6

  1. perf and oprofile are not supposed to work due to hardware issue (YOCTO5148 and YOCTO4511)

Bugzilla

The list of open bugs on Bugzilla Yocto Project on time of the writing of this document is on next table.

Open

In order to see the current bug list, please use following URL: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=meta-freescale

List of open bugs
Bug ID Status Summary
11125 NEW freescale GPU driver imx-gpu-viv is incompatible with kernel linux-fscl
11881 NEW add infrastructure to allow BSPs to switch between set of configurations
12151 NEW Packages tslib-conf, tslib-tests and tslib-calibrate do not get installed in root filesystem without X11
6428 IN PROGRESS DESIGN Improve the ability to isolate changes that have caused a rebuild

Closed

See the list of issues closed in latest development release in the following table:

List of closed bugs
Bug ID Resolution Summary
10287 INVALID gst-play is broken
10602 FIXED meta-freescale layer inclusion breaks other machines
11139 NOTABUG Locale settings does not have effects
11153 NOTABUG Generated locales does not support UTF-8 encoding
5098 WONTFIX gpu-viv-bin-mx6q-3.5.7-1.0.0-alpha.2-sfp.bin and gpu-viv-bin-mx6q-3.5.7-1.0.0-alpha.2-hfp.bin are missing OpenGL headers
6690 FIXED qemu fails during configuration task
6703 FIXED Kernel hangs on boot when HDMI cable is plugged