VAR-SOM-MX6p Android M6.0.1 2.1.0

From Variscite Wiki
VAR-SOM-MX6 Android M6.0.1_2.1.0 developer guide


This Wiki describes how to build and deploy Android Marshmallow on the VAR-SOM-MX6. It is based on NXP's IMX6_M6.0.1_2.1.0_ANDROID release


The objective of this document is to guide VAR-SOM-MX6 Android developers to obtain Android Marshmallow sources, setting up host environment, compilation and deployment.

This document contains instructions for:

  • Hardware and software requirements.
  • Setup the hardware.
  • Setup the toolchain.
  • Download & build the sources.
  • Install the binaries on the VAR-SOM-MX6P SOM

Supported hardware and features

SOM support
Carrier Board support

i.MX6 Quad

NAND flash size support
128MB and up
up to 64GB
Wired Network
10/100/1000 Mbps Ethernet
Wireless Network
Support for Wilink8, 802.11abgn STA, AP, & Wi-Fi Direct Mode SmartConfig Wilink8 page
USB host
Host and Device
x3, up to 3.6 Mbps.
Display HDMI: 720P,1080P
LVDS0 (On board LVDS-to-RGB bridge, 800x480 resolution), LVDS1 external display
Audio Line IN/ Line out and Audio over HDMI
Camera ov5640 camera sensor. CB402 board can be ordered separately at :

Hardware Requirements

VAR-SOM-MX6 evaluation kit.

Host (PC) setup requirements

The host development environment for Android is based on Ubuntu and Debian, please install Ubuntu version 14.04 64bit LTS or Debian 8.4 64bit

Note: Do not use other Ubuntu or Debian releases, than recommended above.

Install required packages on host PC

$ sudo apt-get -y install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib 
$ sudo apt-get -y install libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils 
$ sudo apt-get -y install xsltproc unzip mtd-utils u-boot-tools lzop liblzo2-2 liblzo2-dev zlib1g-dev liblz-dev uuid uuid-dev android-tools-fsutils

Install the OpenJDK

$ sudo apt-get update
$ sudo apt-get install openjdk-7-jdk

Update the default Java version by running:

$ sudo update-alternatives --config java
$ sudo update-alternatives --config javac

Note: The build machine should have at least 50GB of free space to complete the build process.

Obtain source code

Variscite's Linux kernel and U-Boot are available through Github.
Required patches for the Android file system are under: in Variscite's FTP


  • android_M6.0.1_2.1.0_source.tar.gz - NXP's i.MX6 M6.0.1_2.1.0 original BSP patch files.

Get NXP's Android Release Package

$ mkdir ~/var_m_601_210
$ cd ~/var_m_601_210
$ tar xvf ~/Downloads/android_M6.0.1_2.1.0_source.tar.gz

Download Google Android M6.0.1

$ mkdir ~/var_m_601_210/m_601_210_build
$ cd  ~/var_m_601_210/m_601_210_build
$ mkdir ~/bin
$ curl > ~/bin/repo
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH
$ repo init -u -b android-6.0.1_r22
$ repo sync -j4

Clone Variscite's U-Boot and Linux kernel sources

$ mkdir -p ~/var_m_601_210/m_601_210_build/bootable/bootloader
$ cd ~/var_m_601_210/m_601_210_build/bootable/bootloader
$ git clone -b imx6p_v2015.04_4.1.15_1.1.0_ga_var02
$ cd ~/var_m_601_210/m_601_210_build
$ git clone kernel_imx -b imx6p_m6.0.1_2.1.0-ga-var01

Apply all the i.MX Android patches with Freescale i.MX6 support

$ cd ~/var_m_601_210/m_601_210_build
$ source ../android_M6.0.1_2.1.0_source/code/M6.0.1_2.1.0/
**** Invoke "." from your shell to add following functions to your environment:
****-- c_gotop:     Changes directory to the top of the tree 
****-- c_patch:     Recover working tree to base version and then applying FSL android patch

$ c_patch  ../android_M6.0.1_2.1.0_source/code/M6.0.1_2.1.0 imx_M6.0.1_2.1.0
If everything is OK, "c_patch" generates the following output to indicate the successful patch:
Success: Now you can build android code for FSL i.MX platform

Apply Variscite's i.MX6 platforms' patches

$ cd ~/var_m_601_210
$ git clone -b imx6p_m6.0.1_2.1.0-ga-var01 variscite
$ variscite/install

Build Android Images

Change to Android top level directory.

$ cd ~/var_m_601_210/m_601_210_build
$ source build/
$ lunch var_mx6-eng
$ lunch var_mx6-user

Note: var_mx6-user creates a production version of the Android Marshmallow. var_mx6-eng creates an engineering version of the Android Marshmallow. Development mode enable and development tools are available on target.

Build Android for on-SOM eMMC

$ rm out/target/product/var_mx6/recovery/root/fstab* out/target/product/var_mx6/root/fstab*
**The files may not exist**

$ make -j4 BUILD_TARGET_DEVICE=emmc 2>&1 | tee build1-1.log

Images created by the Android build for Variscite MX6 system

If you do ls out/target/product/var_mx6/

system.img Android system image file for VAR-SOM-MX6QP with Capacitive touch on MX6CustomBoard
u-boot-var-imx6p-nand.imx U-Boot for nand used in eMMC boot for VAR-SOM-MX6QP with Capacitive touch on MX6CustomBoard
boot-som-mx6qp-c.img Boot image for VAR-SOM-MX6QP with Capacitive touch on MX6CustomBoard
recovery-som-mx6qp-c.img Recovery image for VAR-SOM-MX6QP with Capacitive touch on MX6CustomBoard

Flashing Android from Linux shell (when the primary installation android)

An example of flashing eMMC, can be found here :

Follow the following steps instructions above:

1. Preparing a rescue SD card;

2. Flash from command line (use the script)

Further follow the steps described in paragraph "Flashing Android with USB Fastboot"

Flashing Android with USB Fastboot

Install tools on host

$ sudo apt-get install android-tools-adb android-tools-fastboot

Connect the target with host PC at fastboot mode:

  1. Connect a USB OTG cable from the target board OTG port to a your host machine USB HOST port.
  2. Power up the board and hit return/space to stop the boot at U-Boot.
  3. type fastboot in the U-Boot command line.

On the Host PC:

$ sudo `which fastboot` flash boot out/target/product/var_mx6/boot-som-mx6qp-c.img
$ sudo `which fastboot` flash recovery out/target/product/var_mx6/recovery-som-mx6qp-c.img
$ sudo `which fastboot` flash system out/target/product/var_mx6/system.img
$ sudo `which fastboot` reboot

Android recovery mode

Enter board in Android Recovery mode

Turn on the device by holding down the "back" button must be held until the end of the boot and logged in "Android Recovery" mode.

Control menu in Android Recovery Mode

  1. To switch between menu items, use a short press of any button (except RESET) or a short touch touchscreen;
  2. To select an item, use long press any button (except RESET) or long touch the touchscreen;

Update Android firmware

Generate OTA packages For generating "OTA" packages, use the following commands:

$ cd ~/var_m_601_210/m_601_210_build
# if Android for SD card
$ make -j4 BUILD_TARGET_DEVICE=sd otapackage 2>&1 | tee build1-1.log
# if Android for eMMC
$ make -j4 BUILD_TARGET_DEVICE=emmc otapackage 2>&1 | tee build1-1.log

Install OTA package to device

  1. Enter to Android Recovery mode
  2. Select menu item "apply update from ADB"
  3. To the host system, perform the following command:
    $ out/host/linux-x86/bin/adb sideload out/target/product/var_mx6/var_mx6-ota-<date>-<image-id>.zip
  4. reboot this device

Note: Real example name for OTA package: out/target/product/var_mx6/

Manual operations

Build boot.img

When you perform changes to the kernel, you may build boot.img solely instead of building the whole Android.

$ cd ~/var_m_601_210/m_601_210_build
$ source build/
$ lunch var_mx6-user
$ make bootimage

Toolchain setup for manual build kernel and U-Boot

Setup the toolchain path to point to arm-eabi- tools in prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin

$ export ARCH=arm
$ export CROSS_COMPILE=~/var_m_601_210/m_601_210_build/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-

Manual build Bootloader 

Change directory to U-Boot

$ cd ~/var_m_601_210/m_601_210_build/bootable/bootloader/uboot-imx

Execute following commands:

Clean tree:
$ make mrproper

Select configuration
$ make mx6p_var_som_android_nand_defconfig

Build U-Boot:
$ make -j4

This command will generate the U-Boot image 'u-boot.imx'.

Manual build Android Linux Kernel and modules

$ cd ~/var_m_601_210/m_601_210_build/kernel_imx 
$ make distclean
$ make imx_v7_var_android_defconfig
$ make -j4 uImage LOADADDR=0x10008000
$ make -j4 modules

This will generate the uImage (kernel image) in the kernel/arch/arm/boot folder