i.MX8 - Custom Image

i.MX8
Introduction
SoC Overview Carrier Boards i.MX6 vs i.MX8
iMX8M Evaluation Kit (EVK)
Overview Getting Started Selecting Boot Mode System Setup Software Support Android_SD_Partitions_RidgeRun_Script Loading pre-built images Yocto Support Building Yocto Installing an Image Alternative image loading Android Support Building Android Installing an Image System Recovery
Nitrogen8M
Overview Getting Started Selecting Boot Mode System Setup Software Support Loading pre-built images Yocto Support Building Yocto Installing an Image Alternative image loading Customizing Boot Sequence Android Support Building Android Installing an image System Recovery
Multimedia
GPU OpenGL OpenCL OpenVX OpenVG Vulkan VPU Encoding System Decoding System ISP Support V4L2 Drivers Porting Guide GStreamer Support Package Installation Pipeline Examples Hardware-accelerated plugins RidgeRun Products GstRtspSink GstWebRTC GstPTZR GstQtOverlay
Reference Documentation
Contact Us

Embedded devices such as i.MX8 based boards can achieve a better performance with a custom image that allows an specific application to run with a lower energy consumption. Example images can be downloaded from manufactures' pages like Boundary Devices or Variscite. An specific image can be built with tools like Yocto that provides a set of elements to create a custom image for every supported board.

Yocto is a open source project that provides tools and template to help developers to create custom images. Every image can be customized through configuration files in order to add just the required packages. The image below shows the Yocto's Structure.

Yocto Structure

Yocto Description

Yocto has a script for initial set up, this script prepares the configuration files to match the sources for the requested build. Every package is managed by a recipe, this file (.bb files) contains the instructions for the source code (download, configure, compile and install).

Yocto's structure is the following:

• build - contains temporal files to create the requested image.
• sources - contains the recipes for every package.
• downloads - contains the downloaded packages to prepare the image.
• sstate-cache - contains shared files to be reused when different images need the same packages.