VAR-SOM-MX6 Android M6.0.1 1.0.0 R0
Introduction
This WIKI describes how to build and deploy Android d Marshmallow on the VAR-SOM-MX6. It is based on NXP's IMX6_M6.0.1_1.0.0_ANDROID release
Overview
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-MX6 SOM and SOM-SOLO/SOM-DUAL SOM.
Supported hardware and features
| Feature |
Description |
|---|---|
| SOM support |
VAR-SOM-MX6 V2 VAR-SOM-SOLO VAR-SOM-DUAL DART-MX6 |
| Carrier Board support |
VAR-MX6CustomBoard VAR-SOLOCustomBoard VAR-DVK-DT6 |
| CPU |
|
| NAND Flash size support |
128MB and up |
| eMMC |
up to 64GB |
| DDR size support configuration |
Solo:up to 1GB. DualLite, Dual, Quad: up to 4GB |
| SD-Card |
+ |
| Wired Network |
10/100/1000 Mbps Ethernet |
| Wireless Network |
Support for Wilink8, 802.11abgn STA, AP, & Wi-Fi Direct Mode SmartConfig Wilink8 page |
| Bluetooth |
+ |
| SPI |
+ |
| I2C |
+ |
| Canbus |
+ |
| USB host |
+ |
| USB OTG |
Host and Device |
| Uarts |
x3, up to 3.6 Mbps. |
| RTC |
+ |
| 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 : sales@variscite.com |
| PCIE | + |
| SATA | + |
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 http://www.ubuntu.com/download/desktop or Debian 8.4 64bit https://www.debian.org/releases
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
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: ftp://customerv:Variscite1@ftp.variscite.com/VAR-SOM-MX6/Software/Android_IMX6_M601_100 in Variscite's FTP
Files:
- android_M6.0.1_1.0.0_core_source.tar.gz - NXP's i.MX6 M6.0.1_1.0.0 original BSP patch files.
- android_M6.0.1_1.0.0_omxplayer_source.tar.gz - Freescale i.MX6 M6.0.1_1.0.0 omxplayer
Get NXP's Android Release Package
$ mkdir ~/var_m_601_100 $ cd ~/var_m_601_100 $ tar xvf ./android_M6.0.1_1.0.0_core_source.tar.gz
Download Google Android M6.0.1
$ cd ~/var_m_601_100 $ mkdir m_601_100_build $ cd m_601_100_build $ mkdir ~/bin $ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo $ chmod a+x ~/bin/repo $ export PATH=~/bin:$PATH $ repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.1_r3 $ repo sync
Clone Variscite's U-Boot and Linux kernel sources
$ mkdir -p ~/var_m_601_100/m_601_100_build/bootable/bootloader $ cd ~/var_m_601_100/m_601_100_build/bootable/bootloader $ git clone https://github.com/varigit/uboot-imx.git uboot-imx $ cd ~/var_m_601_100/m_601_100_build $ git clone https://github.com/varigit/linux-2.6-imx.git kernel_imx $ cd kernel_imx $ git checkout -b m6.0.1_1.0.0_variscite remotes/origin/m6.0.1_1.0.0_variscite
Apply all the i.MX Android patches with Freescale i.MX6 support
$ cd ~/var_m_601_100/m_601_100_build $ source ../android_M6.0.1_1.0.0_core_source/code/M6.0.1_1.0.0/and_patch.sh **** Invoke ". and_patch.sh" 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_1.0.0_core_source/code/M6.0.1_1.0.0 imx_M6.0.1_1.0.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_100 $ git clone https://github.com/varigit/MX6x-android.git -b m6.0.1_1.0.0_variscite variscite $ variscite/install
Install Freescale i.MX6 omxplayer support
The patch script (and_patch.sh) requires some basic utilities like awk/sed.
Apply all Android patches by using the following steps:
$ cd ~/var_m_601_100/m_601_100_build $ cp ~/Downloads/android_M6.0.1_1.0.0_omxplayer_source.tar.gz ./ $ tar xzvf android_M6.0.1_1.0.0_omxplayer_source.tar.gz $ rm android_M6.0.1_1.0.0_omxplayer_source.tar.gz
Build Android Images
Change to Android top level directory.
$ cd ~/var_m_601_100/m_601_100_build $ source build/envsetup.sh $ lunch var_mx6-eng or $ 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.
Switching from eMMC build to SD card build and vice versa
When you switch your target MMC device you need to remove the fstab file. This will guarantee that the make system will copy the right one into target.
$ rm out/target/product/var_mx6/root/fstab*
Build Android for SD card
$ make -j4 BUILD_TARGET_DEVICE=sd 2>&1 | tee build1-1.log
Build Android for on-SOM eMMC
$ make -j4 BUILD_TARGET_DEVICE=emmc 2>&1 | tee build1-1.log
Build for NAND
Note: Due to android file system size, Android should use SD-Card or eMMC only
Images created by the Android build for Variscite MX6 system
If you do ls out/target/product/var_mx6/
| Image |
Description | |||
|---|---|---|---|---|
| system.img | Android system image file. SOM agnostics. | |||
| u-boot-var-imx6-nand.img | u-boot for nand used in eMMC boot. SOM agnostics. | |||
| u-boot-var-imx6-sd.img | u-boot for SD card boot. SOM agnostics. | |||
| boot-<name>-<touch>.img recovery-<name>-<touch>.img |
||||
| <name> is one of: | som-mx6q - Supports VAR-SOM-MX6Q and VAR-SOM-MX6D som-mx6dl - Supports VAR-SOM-MX6DL and VAR-SOM-MX6S som-solo - Supports VAR-SOM-SOLO and VAR-SOM-DUAL | |||
| <touch> - is "r" or "c" | r = resistive touch display c = capacitive touch dispaly | |||
| Image Name |
SOM type |
Carrier Board type |
LCD Type |
Evaluation Kit name |
| boot-som-mx6q-c.img, recovery-som-mx6q-c.img | VAR-SOM-MX6_V2 (Quad / Dual) | VAR-MX6CustomBoard | Capacitive touch | VAR-DVK-MX6_V2-PRO VAR-STK-MX6_V2 |
| boot-som-mx6q-r.img, recovery-som-mx6q-r.img | VAR-SOM-MX6_V2 (Quad / Dual) | VAR-MX6CustomBoard | Resistive touch | VAR-DVK-MX6_V2 VAR-STK-MX6_V2 |
| boot-som-mx6q-vsc.img, recovery-som-mx6q-vsc.img | VAR-SOM-MX6_V2 (Quad / Dual) | VAR-SOLOCustomBoard | Capacitive LVDS touch | N/A |
| boot-som-mx6dl-c.img, recovery-som-mx6dl-c.img | VAR-SOM-MX6_V2 (DualLite/ Solo) | VAR-MX6CustomBoard | Capacitive touch | N/A |
| boot-som-mx6dl-r.img, recovery-som-mx6dl-r.img | VAR-SOM-MX6_V2 (DualLite/ Solo) | VAR-MX6CustomBoard | Resistive touch | N/A |
| boot-som-solo-vsc.img, recovery-som-solo-vsc.img | VAR-SOM-SOLO / VAR-SOM-DUAL | VAR-SOLOCustomBoard | Capacitive LVDS touch | VAR-DVK-SOLO/DUAL VAR-STK-SOLO/DUAL |
| boot-som-solo-c.img, recovery-som-solo-c.img | VAR-SOM-SOLO / VAR-SOM-DUAL | VAR-MX6CustomBoard | Capacitive touch | N/A |
| boot-imx6q-var-dart.img, recovery-imx6q-var-dart.img | DART-MX6 | VAR-DT6CustomBoard | Capacitive touch | VAR-STK-DT6 VAR-DVK-DT6 |
Boot options
Boot options of the Android:
1. Directly from SD-Card
2. Uboot boots from NAND flash, and the rest of the Android images from on-SOM eMMC (when available)
Flash and boot Android from SD-card
Create a bootable SD-Card
Partition and format SD-Card, and copy all images for a capacitive touch panel (VAR-SOM-MX6_V2 (Quad / Dual))
$ sudo ./var-mksdcard.sh -f som-mx6q-c /dev/sdX;sync
Partition and format SD-Card, and copy all images for a resistive touch panel (VAR-SOM-MX6_V2 (Quad/Dual))
$ sudo ./var-mksdcard.sh -f som-mx6q-r /dev/sdX;sync
- Replace /dev/sdX with your true device, You can identify it with dmesg.
Boot From SD-Card
After following the above steps for creating a bootable SD-Card:
- Power-off board
- Insert the newly created SD-Card into the SD-Card socket of the evaluation kit.
- Press and hold the boot-select button or menu buttom (for VAR-SOLOCustomBoard), and power-on the kit.
Flash and boot Android from eMMC
eMMC based system consist of:
- SPL and U-boot on NAND-Flash
- Rest of Android images in eMMC
Preparing images
All Android built images but system.img are ready for flashing out of the default build. system.img must be modified:
$ cd out/target/product/var_mx6 $ simg2img system.img system_raw.img $ mv system_raw.img system.img
Note: Make sure you built Android for emmc
Flashing Android from Linux shell (when the primary installation android)
An example of flashing eMMC, can be found here : http://variwiki.com/index.php?title=VAR-SOM-MX6_Yocto_NAND_Recovery_V50plus
Follow the following steps instructions above:
1. Preparing a rescue SD card;
2. Flash from command line (use the android-emmc.sh 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
Note: Make sure you built Android for emmc
Connect the target with host PC at fastboot mode:
- Connect a USB OTG cable from the target board OTG port to a your host machine USB HOST port.
- Power up the board and hit return/space to stop the boot at u-boot
- type fastboot in the u-boot prompt.
On the Host PC:
$ sudo `which fastboot` flash boot out/target/product/var_mx6/boot-som-mx6q-c.img $ sudo `which fastboot` flash recovery out/target/product/var_mx6/recovery-som-mx6q-c.img $ sudo `which fastboot` flash system out/target/product/var_mx6/system.img $ sudo `which fastboot` reboot
boot-som-mx6q-c.img and recovery-som-mx6q-c.img are for VAR-SOM-MX6 with a capacitive display. You should pick and choose the right file for you see the table above.
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.
- To switch between menu items, use a short press of any button (except RESET) or a short touch touchscreen;
- 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_100/m_601_100_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
- Enter to Android Recovery mode
- Select menu item "apply update from ADB"
- To the host system, perform the following command:
$ out/host/linux-x86/bin/adb sideload out/target/product/var_mx6/var_mx6-ota-<data>-<image-id>.zip
- reboot this device
Note: Real example name for OTA package: out/target/product/var_mx6/var_mx6-ota-20160331-som-mx6q-c.zip
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_100/m_601_100_build $ source build/envsetup.sh $ 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_100/m_601_100_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_100/m_601_100_build/bootable/bootloader/uboot-imx
Execute following commands:
clean tree: $ make mrproper Choose build for SD card or NAND Flash: $ make mx6var_som_sd_android_defconfig or $ make mx6var_som_nand_android_defconfig Build U-Boot: $ make -j4
This command will generate the U-Boot images 'SPL' and 'u-boot.img'.
Manual build Android Linux Kernel and modules
$ cd ~/var_m_601_100/m_601_100_build/kernel_imx $ make distclean $ make imx_v7_var_android_defconfig $ make -j4 uImage LOADADDR=0x10008000 $ make -j4 modules
This will generate uImage(kernel image) in kernel/arch/arm/boot folder