Getting Started with i.MX 6QuadPlus

Choose a Development Path:

2.1 i.MX Linux^® Board Support Package

i.MX Linux^® Board Support Package

• Long-Term Support Kernel Release
• U-Boot
• Yocto Build Tools

The i.MX Linux^® Board Support Package (BSP) is a collection of binary files, source code, and support files that can be used to create a U-Boot boot loader, a Linux^® kernel image, and a root file system for i.MX development systems. Current releases of BSP and source code can be found on imx6tools.

Overview

Before the Linux^® OS kernel can boot on an i.MX board, the Linux^® image needs to be copied to a boot device and the boot switches need to be set to boot that device.

To bring up the board and run Linux^®, four elements are needed:

• Boot loader (U-Boot)
• Linux^® kernel image (zImage)
• A device tree file (.dtb) for the board being used
• A root file system (rootfs) for the particular Linux^® image

Prepare a Linux^® BSP Image

Prebuilt Image

The release contains a prebuilt SD card image that is built specifically for the i.MX 6Quad Sabre-SD board. The SD card image is a file that is typically named and is a specially constructed disk image including partitions and all necessary files to boot the board, including all four components mentioned above.

The prebuilt NXP Linux^® Binary Demo Image provides a typical system and basic set of features for using and evaluating the processor. Without modifying the system, the users can evaluate hardware interfaces, test SoC features, and run user space applications.

Self-built Image

With the source code and documentation, the users also can customize the Linux^® image built for your own device, i.e. add or remove system components.

The Yocto Project is the framework of choice with NXP professional support to build the images that are used for booting a Linux^® kernel, although other methods can be used.

For more details, see NXP Yocto Project User’s Guide.

Download Linux^® BSP Image

There are various ways to download the Linux^® BSP image for different boards, boot devices, and results desired.

For Getting-Started, we only list the few methods to transfer the BSP image to SD card. Experienced Linux^® developer can explore other options.

The.Sdcard image (either from a prebuilt or self-built BSP image) is an SD card image that can be flashed directly. This is the simplest way to load everything needed onto the card with one command.

When more flexibility is desired, an SD card can be loaded with the individual components (boot loader, kernel, dtb file, and rootfs file) one-by-one or the.Sdcard image can be loaded and the individual parts can be overwritten with the specific components.

Copying the full SD card image

An SD/MMC card reader is required to transfer the boot loader and kernel images to initialize the partition table and copy the root file system.

Linux^® host:

The Linux^® kernel running on the Linux^® host assigns a device node to the SD/MMC card reader.

To identify the device node assigned to the SD/MMC card, carry out the following command in the host computer:

WARNING: The instructions below will permanently delete existing content on the SD card and are dangerous to your PC if run incorrectly. If you have question or would like further details, please consult the i.MX Linux^® User's Guide.

$ cat /proc/partitions

Carry out the following command to copy the SD card image to the SD/MMC card. Change sdx below to match the one used by the SD card.

$ sudo dd if= of=/dev/sd bs=1M && sync

Where is the correct board-specific SD card image

To set up the partition manually, please read 4.3.3 in i.MX Linux^® User's Guide.

To load individual component separately when the full SD card image is not used, please read 4.3.4-3.4.6 in i.MX Linux^® User's Guide

Using U-Boot

The U-Boot boot loader is able to download images over Ethernet to RAM and then writes to an SD card. For this operation. Network communications need to be configured.

For instructions about how to download U-Boot to an MMC/SD card that is not the one used to boot from, please refer to section 4.4.1

Images can be downloaded to other boot media (memory storage device) using U-Boot. To use other memory device, please refer to sections under 4.4.1

Using Manufacturing Tool

The Manufacturing Tool, named MfgTool, is a tool that runs on a Windows OS host and is used to download images to different devices on an i.MX board. The tar.gz file can be found with the prebuilt Linux^® BSP image.

Use Manufacturing Tool

2.4 Boot Switch Setup

The boot modes of the i.MX boards are controlled by the boot configuration DIP switches on the board.

The following table shows the DIP switch settings for booting from the SD card slot labeled SD2 and J500 on the i.MX 6 SABRE-SD boards. The SD2 card slot is located beside the LVDS1 connection on the back of the board.

Booting from SD2 (J500) on i.MX 6 SABRE-SD

Switch	D1	D2	D3	D4	D5	D6	D7	D8
SW6	On	OFF	OFF	OFF	OFF	OFF	ON	OFF

For boot switch setup to boot from other device (SD3 and SATA), please refer to 4.5 in i.MX Linux^® User Guide.

2.2 i.MX Android^™ Board Support Package

• Android^™ Compatibility Test Suite (CTS) compatible Release
• Extended Multimedia Features

This section walks through the booting process of the i.MX 6QuadPlus SABRE board with the Android^™ system image and briefly introduce how to build the software components that create your own system image. For more information about building the Android^™ platform, see Android .

Current releases of Demo Images and source code can be found on imx6tools .

Overview

The storage devices on the development system (MMC/SD or NAND) must be programmed with the U-Boot boot loader. The i.MX 6 series boot process determines what storage device to access based on the switch settings. When the boot loader is loaded and begins execution, the U-Boot environment space is then read to determine how to proceed with the boot process.

The images from the prebuilt release package or created from source code contain:

• U-Boot image: u-boot.imx
• boot image: boot.img
• Android^™ system root image: system.img
• Recovery root image: recovery.img

Prepare an Android^™ BSP Image

The images needed to create an Android^™ system can either be obtained from the release package or be built from source.

Prebuilt Image

The prebuilt NXP Android^™ demo image will provide a default system with certain features for purpose of evaluation. Without modifying the system, the users can perform some basic operations, and interact wit the system to test hardware interfaces and develop software application in the user space.

The latest prebuilt demo files can be found in Android^™ section at imx6tools .

Self-built Image

Preparation

To build the Android^™ source files, use a computer running Linux^® OS. Ubuntu 14.04 (64-bit) versions are the ones we have tested the most for Android^™ Marshmallow 6.0 build.

After installing the computer running Linux^® OS, check whether you have all the necessary packages installed for an Android^™ build. See "Setting up your machine" on the Android^™ website .

In addition to the packages requested on the Android^™ website, please refer to Android^™ User Guide to install the additional packages.

Get the source code

Get the Android^™ source code from Google repo.

Get the kernel source code and U-Boot from Freescale open source Git.

Patch

Apply all the i.MX Android^™ patches. For details, please refer to Android^™ User Guide.

Build

The build configuration command lunch can be issued with an argument - strings.

Here is an example to build the Android^™ image with user type for the i.MX 6Quadplus SABRE Board:

$ cd ~/myandroid

$ source build/envsetup.sh

$ lunch sabresd_6dq-user

$ make 2>&1 | tee build-log.txt

When the make command is complete, the build-log.txt file contains the execution output. Check for any errors.

To create Android^™ platform over-the-air, OTA, and package, the following make target is specified:

$ make otapackage

Note: U-Boot mage, kernel uImage, boot.img can be built separately.

Download Android^™ BSP Image

Download Image using Linux^® Utility

The Linux^® utility "dd" on the computer running Linux^® OS can be used to download the images into the SD card.

Before downloading, ensure that your partitions are created as described in Storage partitions.

Download Image using Manufacturing Tool

The Manufacturing Tool, named MfgTool, is a tool that runs on a Windows OS host and is used to download images to target devices on an i.MX board. The tar.gz file can be downloaded in Manufacturing Tools section at imx6tools .

Use Manufacturing Tool

Boot Switch Setupe

The boot modes of the i.MX boards are controlled by the boot configuration switches on the board.

The following table lists the boot switch settings for different boot methods:

eMMC 4-bit (MMC2) boot	(SW6) 11100110 (from 1-8 bit)
eMMC 8-bit (MMC2) boot	(SW6) 11010110 (from 1-8 bit)
SD boot	(SW6) 01000010 (from 1-8 bit)

For boot switch setup to boot from NAND/TFTP/NFS, please refer to 6.2-6.3 in i.MX Android^™ User's Guide.

To boot with HDMI displays, please refer to section 3.4 for more instructions.

3.1 Key Features Demo in Linux^®

With Linux^® running on the i.MX platform, you can evaluate special features that i.MX SoCs provide:

Power Management

There are three main power management techniques on i.MX boards:

• Suspend and resume commands
• CPU frequency scaling
• Bus frequency scaling

After Linux^® setup, for more details about developing applications in user space. Please see i.MX6 Linux^® Reference Manual.

Multimedia

After Linux^® setup, for more details about developing applications in user space. Please see i.MX6 Linux^® Reference Manual.

Graphics

• For more details, go to Chapter 8 of i.MX Linux^® User’s Guide
• For more details of graphic APIs and driver support, see i.MX6 Graphics User’s Guide
  • The purpose of this document is to provide information on graphic APIs and driver support. Each chapter describes a specific set of APIs or driver integration as well as specific hardware acceleration customization. The target audiences for this document are developers writing graphics applications or video drivers
  • i.MX G2D API
  • i.MX 6 EGL and OGL Extension Support
• For more details of Video Processing Unit, see i.MX VPU programming interface Linux^® Reference Manual

Security

• For more details, go to Chapter 9 of i.MX Linux^® User’s Guide
• For details of secure system upgrade, read i.MX Linux^® High Assurance Boot User’s Guide

Connectivity

• Bluetooth support works best with a USB dongle with either BlueZ4 or BlueZ5
• Broadcom Wi-Fi and Bluetooth wireless technology support require the Broadcom firmware package download from imx6tools. The Broadcom device drivers are integrated into the kernel but to function require the firmware package download and integration
• For more details, go to Chapter 10 of i.MX Linux^® User’s Guide

3.2 Application development

After Linux^® setup, for more details about developing applications in user space. Please see i.MX6 Linux^® Reference Manual.

3.3 Yocto Project

NXP Yocto Project User’s Guide covers how to set up the Linux^® host machine, how to run and configure a Yocto Project, generate an image, and generate a rootfs.

For more details, see NXP Yocto Project User’s Guide.

3.4 Extended Features in Android^™

Wi-Fi Display Sink API

The Sensor Demo i.MX 7Dual is a simple demonstration program that uses the FreeRTOS and a set of drivers Provided by NXP. It can get the current gravitational acceleration, temperature, altitude, and magnetic field strength of the board. The purpose of this demo is to show how to use the I2C driver as a Master to communication with other I2C Slaves.

In the second terminal emulator for M4 core, you should see text indicating the sensor example is running (e.g., below). Choose one of the sensor demos and affect the given sensor by moving the board or moving something magnetic near it.

-------------- iMX7D SDB on board sensor example --------------

Please select the sensor demo you want to run:

[1].FXAS21002 3-axes Gyro sensor

[2].FXOS8700 6-axes Acc+Mag sensor

[3].MPL3115 Pressure sensor

Extended codec

The features described in the release notes are supported by NXP implemented media framework OMXPlayer. They are only available after applied android_L5.1.1_2.0.0-ga_omxplayer_source.tar.gz software package.

Only codecs that have no license restriction are included in OMXPlayer package.

For the i.MX 6Dual/Quad, the enhanced features nclude the following:

• Local Playback
  • Enhanced and extended formats and codecs
  • Trick mode playback
  • Multiple audio track selections
• Recording
• Streaming playback
• Audio pass through
• Subtitle

For the i.MX 6SoloX, the enhanced features include the following:

• Local Playback
• Enhanced and extended formats and codecs
• HTTP streaming playback

Check Video/Audio decoder/encoder in i.MX Android^™ Extended codec Releae Notes.

To install the OMXPlayer package, perform the following steps:

1. Copy the OMXPlayer package to the Android^™ root directory
2. Go to the Android^™ root directory and decompress the OMXPlayer package

This step generates the device/fsl-codec, external/fsl_imx_omx, lean_obj_before_building.sh, and switch_build_to.sh.

$ source build/envsetup.sh

$ lunch # e.g., sabresd_6dq-user

$./switch_build_to.sh full

$./clean_obj_before_building.sh

$make