BSP 5

Introduction

Warning: Device Tree Overlays were introduced in BSP 5. Therefore, this information does not apply to earlier BSPs.

Device Tree Overlays (DTO) provide a way to modify the overall device tree without re-compiling the complete device tree.

Overlays are small pieces, or fragments of a complete device tree, and can be added or removed as needed, often enabling/disabling hardware components in the system.

Because of this flexible nature, overlays provide an advantageous way of describing peripheral hardware that can be added or removed from the system. It is also useful for tweaking the parameters of existing hardware before committing it to a complete device tree.

In a very brief description, the process of designing a Device Tree Overlay comprises three macro steps:

1. Write a Device Tree Overlay (.dts) file.
2. Compile the .dts file to generate a .dtbo file.
3. Enable the overlay (using the .dtbo file)

This article will explore these steps for the Toradex BSP Layers and Reference Images for Yocto Project. For information specific to Torizon, see the Device Tree Overlays on Torizon article.

Stages of Development

The development cycle of a device tree overlay, much like many other software components that you plan to integrate into your custom Yocto Project build might have three phases. You are of course free to do it differently, but here's how this article suggests:

• Evaluation: enable pre-built overlays that are included in our Reference Images, making it possible to evaluate some hardware peripherals in a few minutes.
• Development: for faster iteration cycles, build the overlays manually, copy them over to the device and enable them. We do provide a Makefile to ease this process.
• Production: after you are happy with the overlays you have developed:
  • Either integrate them into your custom Yocto Project build.
  • Or integrate them into your final device tree and then integrate your final device tree into your custom Yocto Project build.

Evaluation: Pre-built Device Tree Overlays for Add-on Products Provided by Toradex

To reduce complexity and also to provide you with example implementations, Toradex provides pre-built Device Tree Overlays for the add-on products (Display and Touch Controllers) available in the webshop. Notice that only for the BSP 5.0 onwards, our reference images offer these Overlays as binaries (.dtbo files).

On a Toradex SoM with the Linux BSP > 5.0 installed, you can list these files available on the boot partition. As an example, using the the terminal of a Apalis iMX8:

$ ls /boot/overlays
apalis-imx8_ar0521_overlay.dtbo   apalis-imx8_atmel-mxt_overlay.dtbo apalis-imx8_hdmi_overlay.dtbo
apalis-imx8_lvds_overlay.dtbo     apalis-imx8_ov5640-2_overlay.dtbo  apalis-imx8_ov5640_overlay.dtbo
display-dpi-lt170410_overlay.dtbo display-edt5.7_overlay.dtbo        display-edt7_overlay.dtbo
display-fullhd-imx6_overlay.dtbo  display-fullhd_overlay.dtbo        display-lt161010_overlay.dtbo
display-lt170410_overlay.dtbo     display-vga_overlay.dtbo

To enable these overlays, see the Enable/Disable a Device Tree Overlay section. Some overlays are pre-enabled by default, refer to the Pre-enabled Device Tree Overlays section for this.

If you want to obtain the source code of the Device Tree Overlays provided by Toradex for the products available in the webshop, see the Build U-Boot and Linux Kernel from Source Code article.

Displays

Attention: the migration to device tree overlays is currently a work-in-progress. There are some overlays listed in the table below that are missing. For more information, please consult the BSP Layers and Reference Images for Yocto Project Issue Tracker.

• Capacitive Touch Display 7" Parallel
• Capacitive Touch Display 10.1" LVDS
• Resistive Touch Display 7" Parallel
• HDMI
• VGA
• EDT 7.0" (EOL)

Pre-enabled Device Tree Overlays

Toradex turns on a pre-set of Device Tree Overlays to support the default display interfaces and panels.

• Apalis
• Colibri
• Verdin

Enable/Disable a Device Tree Overlay

To enable or disable applying a pre-built overlay on a Toradex SoM just add/remove it to/from the file overlays.txt located on the boot partition, and reboot the system.

For example, one wants to disable a parallel RGB interface and display on Colibri-iMX8X and enable an HDMI interface (using DSI-to-HDMI adapter). The initial overlays.txt file looks like:

# cat /boot/overlays.txt 
fdt_overlays=colibri-imx8x_parallel-rgb_overlay.dtbo colibri-imx8x_ad7879_overlay.dtbo display-edt7_overlay.dtbo

Steps to disable a parallel RGB and enable an HDMI:

1. Open the overlays.txt file with any text editor, e.g. vi:

# vi /boot/overlays.txt 

2. Remove overlays, that is needed for Resistive Touch Display 7" Parallel and add one for DSI-to-HDMI adapter. The file should look like:

# cat /boot/overlays.txt 
fdt_overlays=colibri-imx8x_dsihdmi_overlay.dtbo

3. Synchronize them filesystems:

# sync

4. Reboot the system:

# reboot

Note: In case you find yourself with a non-working kernel after applying the overlays, see the Removing a conflicting DTO section.

Note: If you want to obtain the source code of the Device Tree Overlays provided by Toradex for the products available in the webshop, see the Build U-Boot and Linux Kernel from Source Code article.

Development: Writing a Custom DTO

The most recommended way to create a new overlay is to start looking at our evaluation boards' overlays and then adapt to your project's needs. You can find those overlays in the device-tree-overlays repository.

As with normal device trees, overlays must get explicitly written for the correct kernel version. This depends on the BSP you are using from Toradex and can be checked on Build U-Boot and Linux Kernel from Source Code article.

As an example, here is the device tree overlay for parallel RGB on a Colibri iMX8X (colibri-imx8x_parallel-rgb_overlay.dts):

// Enable the parallel RGB interface on Colibri iMX8X

/dts-v1/;
/plugin/;
/ {
    compatible = "toradex,colibri-imx8x";
};

&adma_pwm {
        status = "okay";
};

&backlight {
        status = "okay";
};

&display_lcdif {
        status = "okay";
};

&panel_dpi {
        status = "okay";
};

This overlay, if loaded, is directly appended to imx8qxp-colibri-eval-v3.dts. This device tree, however, includes the "System on Module Level" device tree imx8qxp-colibri.dtsi which contains most of the device tree nodes.

If the overlay gets loaded, it gets integrated into the already loaded device tree. To add or overwrite properties can be achieved with the ampersand character the same way as described in section Overwriting_properties.

Devicetree overlays have to be denoted with /plugin/; in the header.

For further reading on this topic, we refer to the kernel documentation: https://www.kernel.org/doc/html/latest/devicetree/overlay-notes.html?highlight=overlays

Building a DTO

To build the Device Tree Overlay, see the Build U-Boot and Linux Kernel from Source Code article.

Deploying a Device Tree Overlay

To deploy a custom overlay on a Toradex SoM with the Linux BSP >= 5.0 installed:

• copy the .dtbo file to the overlays/ directory in the boot partition;
• add the overlay binary .dtbo to the overlays.txt file. This file contains a space separated list of overlays. For example:

$ cat /boot/overlays.txt 
fdt_overlays=verdin-imx8mm_lt8912_overlay.dtbo verdin-imx8mm_ov5640_overlay.dtbo

After changing the overlays.txt, run the command sync and reboot the board. Do not power-cycle because the edits done may not sync to the file system.

Note: In case you find yourself with a non-working kernel after applying the overlay, see the Removing a conflicting DTO section

Removing a conflicting DTO

In case you find yourself with a non-working kernel (normally, stuck at the "Loading kernel..." message), you can choose the way to solve this issue:

1. Disable loading all overlays by setting the special u-boot variable:

> setenv skip_fdt_overlays 1
> boot

2. Delete your custom overlays easily directly from your PC. You would need to set up a USB-OTG connection with your PC and run the UMS functionality of U-Boot by simply stopping the autoboot at U-boot and running the following commands:

ums 0 mmc 0

After this command, you should see a BOOT partition show up on your PC. Delete the conflicting .dtbo and the corresponding item in the overlays.txt file.

Note: Check your carrier board datasheet to what ports and jumper configurations work with USB-OTG. With Toradex carrier boards, it requires using the correct port or a small jumper removal (like Ixora's JP2).

Production: Add Your Overlays to a Custom Yocto Project Build

It is expected that you have some knowledge of Yocto Project/OpenEmbedded. The minimum prerequisite is being able to Build a Reference Image with Yocto Project.

If you decide to integrate your final changes into full device trees, read the article Custom meta layers, recipes and images in Yocto Project (hello-world examples).

If you decide to deploy the overlays, two steps are required and explained below:

• Add your overlays, making sure they are compiled and deployed to the image.
• Have the overlays listed in overlays.txt, making sure they are enabled.

Add Your Overlays to the Yocto Project

There are currently two recipes that handle device tree overlays:

• meta-toradex-bsp-common/recipes-kernel/linux/device-tree-overlays-mainline_git.bb: for mainline kernel-based builds.
• meta-toradex-nxp/recipes-kernel/linux/device-tree-overlays_git.bb: for downstream kernel-based builds.

You can, for instance, write your own bbappends to add your device tree overlays repository instead of ours.

Enable Your Overlays in the Yocto Project

The class meta-toradex-bsp-common/classes/image_type_tezi.bbclass is responsible for adding overlays that will be applied during boot time. It uses the variable TEZI_EXTERNAL_KERNEL_DEVICETREE_BOOT that is set by default in our machine configuration files, either machine.conf or machine.inc.

You can find them using e.g. grep inside the layers directory:

$ cd <yocto projet setup>
$ grep -nre "TEZI_EXTERNAL_KERNEL_DEVICETREE_BOOT" layers/*

Then you need to either append to or override the variable. One possibility is to use a <machine>-extra.conf file. You can find an example on Custom meta layers, recipes and images in Yocto Project (hello-world examples).