Android NXP Guide: Difference between revisions

From Variscite Wiki
No edit summary
No edit summary
(34 intermediate revisions by 3 users not shown)
Line 2: Line 2:
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!--
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!--
--> {{#lst:Android_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_O8.1.0_1.3.0_8M_DART-MX8M}}}} <!--
--> {{#lst:Android_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_O8.1.0_1.3.0_8M_DART-MX8M}}}} <!--
--> {{PageHeader|{{#var:HARDWARE_NAME}} - {{#switch: {{#var:ANDROID_NAME}} | Android 10 = Android {{#var:ANDROID_VERSION}} | Android 11 = Android {{#var:ANDROID_VERSION}} | Android {{#var:ANDROID_NAME}} {{#var:ANDROID_VERSION}} }} Developer Guide}} {{DocImage|category1=Android|category2={{#var:HARDWARE_NAME}}}} __toc__
--> {{PageHeader|{{#var:HARDWARE_NAME}} - {{#var:ANDROID_VERSION}} Developer Guide}} {{DocImage|category1=Android|category2={{#var:HARDWARE_NAME}}}} __toc__


= Introduction<br/> =
= Introduction<br/> =
Line 81: Line 81:
  $ tar xvf ~/Downloads/{{#var:ANDROID_VARFTP_BASE_PATCH_FILE}}
  $ tar xvf ~/Downloads/{{#var:ANDROID_VARFTP_BASE_PATCH_FILE}}


== Download Google Android {{#var:ANDROID_VERSION}} ==
== Download Google {{#var:ANDROID_VERSION}} ==
  $ mkdir -p ~/bin
  $ mkdir -p ~/bin
  $ curl -o ~/bin/repo https://commondatastorage.googleapis.com/git-repo-downloads/repo
  $ curl -o ~/bin/repo https://commondatastorage.googleapis.com/git-repo-downloads/repo
Line 89: Line 89:
  $ source {{#var:ANDROID_FOLDER_ID}}/imx_android_setup.sh
  $ source {{#var:ANDROID_FOLDER_ID}}/imx_android_setup.sh
* Note : Since Oreo the distribution of Android Source code is partially hosted on Linux Foundation https://source.codeaurora.org/*
* Note : Since Oreo the distribution of Android Source code is partially hosted on Linux Foundation https://source.codeaurora.org/*
{{#ifeq: {{#var:ANDROID_NAME}} | Android 11 |
Wait for the script to finish running, and it should create following folders
$ {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/device/variscite/
$ {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/vendor/variscite/kernel_imx and
$ {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/vendor/variscite/uboot-imx
== Apply Variscite's i.MX platforms patches ==
$ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/device
$ variscite/scripts/install.sh {{#var:ANDROID_SCFW_INSTALL_ARGS}}
|
Wait for the script to finish running, and it should create a "{{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}" folder
Wait for the script to finish running, and it should create a "{{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}" folder
  $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}; mkdir -p vendor/variscite/
  $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}; mkdir -p vendor/variscite/
Line 101: Line 112:
  $ git clone {{#var:ANDROID_VARISCITE_GIT}} -b {{#var:ANDROID_VARISCITE_BRANCH}} variscite
  $ git clone {{#var:ANDROID_VARISCITE_GIT}} -b {{#var:ANDROID_VARISCITE_BRANCH}} variscite
  $ variscite/scripts/install.sh {{#var:ANDROID_SCFW_INSTALL_ARGS}}
  $ variscite/scripts/install.sh {{#var:ANDROID_SCFW_INSTALL_ARGS}}
 
}}
= Build Android Images =
= Build Android Images =


Line 159: Line 170:


=== Preparing images ===
=== Preparing images ===
 
{{#ifeq:{{#var:ANDROID_NAME}}|Android 11 |
The default super.img, vendor_boot.img format is suitable for flashing using fastboot, and must be modified for flashing using 'dd'.
$ cd out/target/product/{{#if: {{#var:ANDROID_PRODUCT_NAME}} | {{#var:ANDROID_PRODUCT_NAME}} | {{#var:ANDROID_MACHINE_NAME}} }}
$ simg2img super.img super_raw.img
$ simg2img vendor_boot.img vendor_boot_raw.img
|
{{#ifeq:{{#var:ANDROID_DYNAMIC_PARTITION}}|true |
{{#ifeq:{{#var:ANDROID_DYNAMIC_PARTITION}}|true |
The default super.img, format is suitable for flashing using fastboot, and must be modified for flashing using 'dd'.
The default super.img, format is suitable for flashing using fastboot, and must be modified for flashing using 'dd'.
Line 176: Line 192:
  $ simg2img vendor.img vendor_raw.img
  $ simg2img vendor.img vendor_raw.img
  {{#ifeq:{{#var:ANDROID_NAME}}|Android 10| $ simg2img product.img product_raw.img}}
  {{#ifeq:{{#var:ANDROID_NAME}}|Android 10| $ simg2img product.img product_raw.img}}
  }}
  }}}}


=== Flashing Android from Linux shell (when the primary installation android) ===
=== Flashing Android from Linux shell (when the primary installation android) ===
Line 232: Line 248:
For generating "OTA" packages, use the following commands:
For generating "OTA" packages, use the following commands:
  $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
  $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
{{#ifeq: {{#var:ANDROID_NAME}} | Android 11 |
$ source build/envsetup.sh
$ lunch PRODUCT={{#var:ANDROID_MACHINE_NAME}}-userdebug
$ ./imx-make.sh bootloader kernel -j4
$ make otapackage -j4
|
  {{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
  {{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
  $ source build/envsetup.sh  
  $ source build/envsetup.sh  
Line 239: Line 261:
  |
  |
  $ make PRODUCT={{#var:ANDROID_MACHINE_NAME}}-eng otapackage -j4 2>&1 | tee build1-1.log
  $ make PRODUCT={{#var:ANDROID_MACHINE_NAME}}-eng otapackage -j4 2>&1 | tee build1-1.log
  }}
  }}}}


===== Install OTA package to device =====
===== Install OTA package to device =====
* extract payload.bin and payload_properties.txt from OTA zip file
* extract payload.bin and payload_properties.txt from OTA zip file
  {{#ifeq: {{#var:ANDROID_NAME}} | Android 11 |
* Push payload.bin to board's /data/ota_package dir: adb push payload.bin /data/ota_package/ .
  |
   {{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
   {{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
* Push payload.bin to board's /sdcard dir: adb push payload.bin /sdcard/ .
* Push payload.bin to board's /sdcard dir: adb push payload.bin /sdcard/ .
   |
   |
* push file payload.bin to somewhere on the device (typically /cache folder)
* push file payload.bin to somewhere on the device (typically /cache folder)
   }}
   }}}}
* open payload_properties.txt on an editor to copy its content, lets suppose it's like in the NXP manual:
* open payload_properties.txt on an editor to copy its content, lets suppose it's like in the NXP manual:
   FILE_HASH=0fSBbXonyTjaAzMpwTBgM9AVtlBeyOigpCCgkoOfHKY=
   FILE_HASH=0fSBbXonyTjaAzMpwTBgM9AVtlBeyOigpCCgkoOfHKY=
Line 257: Line 282:
   }}
   }}
   METADATA_SIZE=46866
   METADATA_SIZE=46866
  {{#ifeq: {{#var:ANDROID_NAME}} | Android 11 |
* Input the following command on the board's console to update:
  su
  update_engine_client --payload=file:///data/ota_package/payload.bin --update --headers="FILE_HASH=0fSBbXonyTjaAzMpwTBgM9AVtlBeyOigpCCgkoOfHKY=
  |
   {{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
   {{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
* Input the following command on the board's console to update:
* Input the following command on the board's console to update:
Line 264: Line 294:
* Issue the following command on adb shell:
* Issue the following command on adb shell:
   update_engine_client --payload=file:///cache/payload.bin --update --headers="FILE_HASH=0fSBbXonyTjaAzMpwTBgM9AVtlBeyOigpCCgkoOfHKY=
   update_engine_client --payload=file:///cache/payload.bin --update --headers="FILE_HASH=0fSBbXonyTjaAzMpwTBgM9AVtlBeyOigpCCgkoOfHKY=
   }}
   }}}}
   FILE_SIZE=379074366
   FILE_SIZE=379074366
   {{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
   {{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
Line 273: Line 303:
   METADATA_SIZE=46866"
   METADATA_SIZE=46866"


{{#ifeq: {{#var:ANDROID_NAME}} | Android 11 |
Make sure that the -- header equals to the exact content of payload_properties.txt without "space" or "return"
character.
|
{{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
{{#ifeq: {{#var:ANDROID_NAME}} | Android 10 |
Make sure that the -- header equals to the exact content of payload_properties.txt without "space" or "return"
Make sure that the -- header equals to the exact content of payload_properties.txt without "space" or "return"
Line 278: Line 312:
|
|
Note that the command argument --headers="..." contains the exact (4-line) content of the payload_properties.txt file between quotes (you can copy and paste it), including 3 newline characters.
Note that the command argument --headers="..." contains the exact (4-line) content of the payload_properties.txt file between quotes (you can copy and paste it), including 3 newline characters.
}}
}}}}
   
   
After issuing the command, nothing seems to happen on the device, but you can monit logcat for operation progress. After a successful update you can reboot into the updated version.
After issuing the command, nothing seems to happen on the device, but you can monit logcat for operation progress. After a successful update you can reboot into the updated version.
Line 314: Line 348:
* proceed for flashing
* proceed for flashing


}}
{{#ifeq:{{#var:ANDROID_UUU_SUPPORT}}|true |
= Flashing Using NXP MFGTools - UUU (Universal Update Utility) =
To flash Android OS without using a recovery SD card, UUU (MFG Tools 3.0) can be used.<br>
Please refer to {{Varlink|Android_UUU_IMX8|{{#var:RELEASE_PARAM|RELEASE_O8.1.0_1.3.0_8M_DART-MX8M}}|Flashing Android OS using UUU - USB Boot}}.
}}
{{#ifeq:{{#var:ANDROID_M4_SUPPORTED}}|true |
= Running a M4 demo =
Please choose one of the below options while flashing Android from Linux shell
imx8mm-var-dart-dt8mcustomboard-legacy-m4 - Supports LVDS / SD / WiFi (DART-MX8M-MINI-M4 on DT8MCustomBoard 1.x)
imx8mm-var-dart-dt8mcustomboard-m4 - Supports LVDS / SD / WiFi (DART-MX8M-MINI-M4 on DT8MCustomBoard 2.x)
imx8mm-var-som-symphony-legacy-m4 - Supports LVDS / SD / WiFi (VAR-SOM-MX8M-MINI-M4 on a Symphony-Board V1.4 and below)
imx8mm-var-som-symphony-m4 - Supports LVDS / SD / WiFi (VAR-SOM-MX8M-MINI-M4 on a Symphony-Board V1.4A and above)
=== Running a demo from Linux ===
Boot Android to the shell
Increase kernel loglevel while debugging:
  sysctl kernel.printk=7;
 
Check the state of the m4, it should be running already by U-Boot
cat /sys/class/remoteproc/remoteproc0/state
If the state is 'running', stop the m4
echo stop > /sys/class/remoteproc/remoteproc0/state
Load new firmware (.elf file must already exist in /lib/firmware directory)
echo rpmsg_lite_pingpong_rtos_linux_remote.elf > /sys/class/remoteproc/remoteproc0/firmware
Change the state to running
echo start > /sys/class/remoteproc/remoteproc0/state
Copy and run demo module
From Host PC
$ adb root
$ adb push {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/out/target/product/dart_mx8mm/obj/KERNEL_OBJ/drivers/rpmsg/imx_rpmsg_pingpong.ko /data
From device shell
$ su
$ cd /data
$ insmod imx_rpmsg_pingpong.ko
=== Running a demo from U-Boot ===
Enable below node in -m4.dtsi and re-build images as per "Build Android Images" section and follow the steps described in paragraph "Flashing Android with USB Fastboot" to flash the images
  &rpmsg{
        status = "okay";
  };
From U-Boot shell execute below commands
u-boot=> bootmcu
run command: 'bootaux 0x7e0000'
## Starting auxiliary core stack = 0x20020000, pc = 0x1FFE035D...
u-boot=> run bootcmd
Follow steps as described in "Copy and run demo module"
}}
{{#ifeq:{{#var:ANDROID_8MP_M7_SUPPORTED}}|true |
= Running a M7 demo =
Please choose one of the below options while flashing Android from Linux shell
imx8mp-var-dart-dt8mcustomboard-legacy-m7.img (Variscite DART-MX8M-PLUS M7 LVDS on DT8MCustomBoard 1.x)
imx8mp-var-dart-dt8mcustomboard-m7.img (Variscite DART-MX8M-PLUS M7 LVDS on DT8MCustomBoard 2.x)
imx8mp-var-som-symphony-2nd-ov5640-m7.img (Variscite VAR-SOM-MX8M-PLUS M7 with 2nd OV5640 on Symphony-Board)
imx8mp-var-som-symphony-m7.img (VAR-SOM-MX8M-PLUS M7 LVDS on Symphony-Board)
=== Running a demo from Linux ===
Boot Android to the shell
Increase kernel loglevel while debugging:
  sysctl kernel.printk=7;
 
Check the state of the m7, it should be running already by U-Boot
cat /sys/class/remoteproc/remoteproc0/state
If the state is 'running', stop the m7
echo stop > /sys/class/remoteproc/remoteproc0/state
Load new firmware (.elf file must already exist in /lib/firmware directory)
echo rpmsg_lite_pingpong_rtos_linux_remote.elf.dart > /sys/class/remoteproc/remoteproc0/firmware OR
echo rpmsg_lite_pingpong_rtos_linux_remote.elf.som > /sys/class/remoteproc/remoteproc0/firmware
Change the state to running
echo start > /sys/class/remoteproc/remoteproc0/state
Copy and run demo module
From Host PC
$ adb root
$ adb push {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/out/target/product/dart_mx8mp/obj/KERNEL_OBJ/drivers/rpmsg/imx_rpmsg_pingpong.ko /data
From device shell
$ su
$ cd /data
$ insmod imx_rpmsg_pingpong.ko
=== Running a demo from U-Boot ===
Enable below node in -m7.dtsi and re-build images as per "Build Android Images" section and follow the steps described in paragraph "Flashing Android with USB Fastboot" to flash the images
  &rpmsg{
        status = "okay";
  };
From U-Boot shell execute below commands
u-boot=> bootmcu
run command: 'bootaux 0x7e0000'
## Starting auxiliary core stack = 0x20020000, pc = 0x0000051D...
u-boot=> run bootcmd
Follow steps as described in "Copy and run demo module"
}}
{{#ifeq:{{#var:ANDROID_8M_M4_SUPPORTED}}|true |
= Running a M4 demo =
Please choose one of the below options while flashing Android from Linux shell
imx8mq-var-dart-dt8mcustomboard-legacy-m4-wifi-dp - Variscite DART-MX8M on DT8MCustomBoard 1.x M4+WIFI+DP
imx8mq-var-dart-dt8mcustomboard-legacy-m4-wifi-hdmi - Variscite DART-MX8M on DT8MCustomBoard 1.x M4+WIFI+HDMI
imx8mq-var-dart-dt8mcustomboard-legacy-m4-wifi-lvds-dp - Variscite DART-MX8M on DT8MCustomBoard 1.x M4+WIFI+LVDS
imx8mq-var-dart-dt8mcustomboard-legacy-m4-wifi-lvds-hdmi - Variscite DART-MX8M on DT8MCustomBoard 1.x M4+WIFI+LVDS+HDMI
imx8mq-var-dart-dt8mcustomboard-legacy-m4-wifi-lvds - Variscite DART-MX8M on DT8MCustomBoard 1.x M4+WIFI+LVDS
imx8mq-var-dart-dt8mcustomboard-m4-wifi-hdmi - Variscite DART-MX8M on DT8MCustomBoard 2.x M4+WIFI+HDMI
imx8mq-var-dart-dt8mcustomboard-m4-wifi-lvds-hdmi - Variscite DART-MX8M on DT8MCustomBoard 2.x M4+WIFI+LVDS+HDMI
imx8mq-var-dart-dt8mcustomboard-m4-wifi-lvds - Variscite DART-MX8M on DT8MCustomBoard 2.x M4+WIFI+LVDS
=== Running a demo from Linux ===
Boot Android to the shell
Increase kernel loglevel while debugging:
  sysctl kernel.printk=7;
 
Check the state of the m4, it should be running already by U-Boot
cat /sys/class/remoteproc/remoteproc0/state
If the state is 'running', stop the m4
echo stop > /sys/class/remoteproc/remoteproc0/state
Load new firmware (.elf file must already exist in /lib/firmware directory)
echo cm_rpmsg_lite_pingpong_rtos_linux_remote.elf > /sys/class/remoteproc/remoteproc0/firmware
Change the state to running
echo start > /sys/class/remoteproc/remoteproc0/state
Copy and run demo module
From Host PC
$ adb root
$ adb push {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/out/target/product/dart_mx8mq/obj/KERNEL_OBJ/drivers/rpmsg/imx_rpmsg_pingpong.ko /data
From device shell
$ su
$ cd /data
$ insmod imx_rpmsg_pingpong.ko
=== Running a demo from U-Boot ===
Enable below node in -m4.dtsi and re-build images as per "Build Android Images" section and follow the steps described in paragraph "Flashing Android with USB Fastboot" to flash the images
  &rpmsg{
        status = "okay";
  };
From U-Boot shell execute below commands
u-boot=> bootmcu
run command: 'bootaux 0x7e0000'
## Starting auxiliary core stack = 0x20020000, pc = 0x1FFE035D...
u-boot=> run bootcmd
Follow steps as described in "Copy and run demo module"
}}
{{#ifeq:{{#var:ANDROID_8X_M4_SUPPORTED}}|true |
= Running a M4 demo =
Please choose one of the below options while flashing Android from Linux shell
imx8qxp-var-som-symphony-wifi-m4 - Variscite M4 LVDS / WiFi
imx8qxp-var-som-symphony-sd-m4 - Variscite M4 LVDS / SD
=== Running a demo from Linux ===
Boot Android to the shell
Increase kernel loglevel while debugging:
  sysctl kernel.printk=7;
 
Check the state of the m4, it should be running already by U-Boot
cat /sys/class/remoteproc/remoteproc0/state
If the state is 'running', stop the m4
echo stop > /sys/class/remoteproc/remoteproc0/state
Load new firmware (.elf file must already exist in /lib/firmware directory)
echo cm_rpmsg_lite_pingpong_rtos_linux_remote.elf > /sys/class/remoteproc/remoteproc0/firmware
Change the state to running
echo start > /sys/class/remoteproc/remoteproc0/state
Copy and run demo module
From Host PC
$ adb root
$ adb push {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/out/target/product/som_mx8q/obj/KERNEL_OBJ/drivers/rpmsg/imx_rpmsg_pingpong.ko /data
From device shell
$ su
$ cd /data
$ insmod imx_rpmsg_pingpong.ko
}}
}}

Revision as of 20:19, 14 July 2021

DART-MX8M - Android O8.1.0_r14 Developer Guide

Introduction

This page describes how to build and deploy Android Oreo on the DART-MX8M. It is based on NXP's imx_8.1.0_1.3.0_8m_ANDROID release

Overview

The objective of this document is to guide DART-MX8M Android developers to obtain Android Oreo 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 DART-MX8M SOM and variants.

Supported hardware and features

Feature
Description
SOM support
DART-MX8M
Carrier Board support
VAR-DT8MCustomBoard
CPU

i.MX8M

eMMC
up to 64GB
DDR size support configuration
up to 4GB
SD card
+
Wired Network
10/100/1000 Mbps Ethernet
Wireless Network
Support for LWB5, 802.11 ac/a/b/g/n STA, AP, & Wi-Fi Direct Mode SmartConfig
Bluetooth
4.2 / BLE
SPI
+
I2C
+
USB host
+
USB OTG
Host and Device
Uarts
x4, up to 4 Mbps.
RTC
+
Display HDMI: V2.0a up to 4Kp60
LVDS Dual 1920×1080 24-bit
MIPI-DSI 1920×1080 24-bit
Audio Line IN / HP
Camera 2x MIPI-CSI2
PCIE +


Hardware Requirements

You will need the Variscite DART-MX8M based evaluation kit.

Host (PC) setup requirements

The host development environment for Android is based on Ubuntu, please install Ubuntu version 16.04/18.04 64bit LTS http://www.ubuntu.com/download/desktop

If you are running Linux in a virtual machine you need at least 16GB of RAM/swap.

Note: Do not use other Ubuntu releases other than the ones recommended above.

Install required packages on host PC

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

Configure Git

$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"

Install the OpenJDK

To install it:

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


If your Ubuntu version is missing the package (which shouldn't happen), add the PPA repository and run the previous commands again:

$ sudo add-apt-repository ppa:openjdk-r/ppa


Update the default Java version by running:

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

Note: The build process requires about 500GB of free space.

Obtain source code

Variscite's Linux kernel and U-Boot are available through Github.
Required patches for the Android file system are under: https://variscite-public.nyc3.cdn.digitaloceanspaces.com/DART-MX8M/Software/Android/Android_iMX8M_O810_130/ in Variscite's FTP

Files:

  • imx-o8.1.0_1.3.0_8m.tar.gz - NXP's Android O8.1.0_1.3.0 original BSP patch files.

Get NXP's Android Release Package

$ mkdir ~/var_imx-o8.1.0_1.3.0_8m
$ cd ~/var_imx-o8.1.0_1.3.0_8m
$ curl -o ~/Downloads/imx-o8.1.0_1.3.0_8m.tar.gz https://variscite-public.nyc3.cdn.digitaloceanspaces.com/DART-MX8M/Software/Android/Android_iMX8M_O810_130/imx-o8.1.0_1.3.0_8m.tar.gz
$ tar xvf ~/Downloads/imx-o8.1.0_1.3.0_8m.tar.gz

Download Google Android O8.1.0_r14

$ mkdir -p ~/bin
$ curl -o ~/bin/repo https://commondatastorage.googleapis.com/git-repo-downloads/repo
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH
$ cd ~/var_imx-o8.1.0_1.3.0_8m
$ source imx-o8.1.0_1.3.0_8m/imx_android_setup.sh

Wait for the script to finish running, and it should create a "~/var_imx-o8.1.0_1.3.0_8m/android_build" folder

$ cd ~/var_imx-o8.1.0_1.3.0_8m/android_build; mkdir -p vendor/variscite/

Clone Variscite's U-Boot and Linux kernel sources

$ cd ~/var_imx-o8.1.0_1.3.0_8m/android_build/vendor/variscite/
$ git clone https://github.com/varigit/uboot-imx.git -b imx_v2017.03_4.9.51_imx8m_ga_var01
$ git clone https://github.com/varigit/linux-imx kernel_imx -b o8.1.0_1.3.0_8m-ga_var01

Apply Variscite's i.MX platforms patches

$ cd ~/var_imx-o8.1.0_1.3.0_8m/android_build/device
$ git clone https://github.com/varigit/MX6x-android.git -b o8.1.0_1.3.0_8m-ga-var01 variscite
$ variscite/scripts/install.sh

Build Android Images

Change to Android top level directory.

$ cd ~/var_imx-o8.1.0_1.3.0_8m/android_build
$ source build/envsetup.sh
$ lunch dart_mx8m-eng
 or
$ lunch dart_mx8m-userdebug

Note: userdebug build creates a debuggable version of Android. eng build creates an engineering version of Android. Development mode enable and development tools are available on target.

$ export PATH=/usr/lib/jvm/java-8-openjdk-amd64/bin:$PATH

Switching from eMMC build to SD card build and vice versa

Unlike previous Android BSPs, the boot media is autodetected at boot time.

Build Android

make -j4 2>&1 | tee build1-1.log

Images created by the Android build

The resulted images are located in out/target/product/dart_mx8m.


Image
Description
u-boot-imx8m-var-dart.imx U-Boot for eMMC/SD card boot.
SOM agnostics.
system.img Android system image file.
SOM agnostics.
vendor.img Android vendor image file.
SOM agnostics.
boot-<name>.img
vbmeta-<name>.img
configuration dependent
<name> is one of: imx8m-var-dart-emmc-wifi-dcss-lvds - Supports LVDS (via DCSS) / WiFi
imx8m-var-dart-emmc-wifi-dual-display - Supports HDMI (via DCSS) / LVDS (via LCDIF) / WiFi
imx8m-var-dart-emmc-wifi-hdmi-4k - Supports HDMI-4k / WiFi
imx8m-var-dart-emmc-wifi-hdmi - Supports HDMI / WiFi
imx8m-var-dart-emmc-wifi-lcdif-lvds - Supports LVDS (via LCDIF) / WiFi
imx8m-var-dart-sd-emmc-dcss-lvds - Supports LVDS (via DCSS) / SD
imx8m-var-dart-sd-emmc-dual-display - Supports HDMI (via DCSS) / LVDS (via LCDIF) / SD
imx8m-var-dart-sd-emmc-hdmi-4k - Supports HDMI-4k (via DCSS) / SD
imx8m-var-dart-sd-emmc-hdmi - Supports HDMI (via DCSS) / SD
imx8m-var-dart-sd-emmc-lcdif-lvds - Supports LVDS (via LCDIF) / SD


Boot options

Boot options of the Android:
1. Directly from SD card
2. U-Boot boots from on-SOM eMMC

Flash and boot Android from SD card

Create a bootable SD card

Partition and format SD card, and copy all images

$ sudo ./var-mksdcard.sh -f <name> /dev/sdX;sync

Boot From SD card

  • Power-off the board.
  • Insert the SD card into the SD card slot of the carrier board (DVK)
  • Make sure the Boot Mode is set to SD card: see Setting the Boot Mode section
  • Power up the board - it will boot into Linux from the SD card


Flash and boot Android from eMMC

Preparing images

The default system.img and vendor.img format is suitable for flashing using fastboot, and must be modified for flashing using 'dd'.

$ cd out/target/product/dart_mx8m
$ simg2img system.img system_raw.img
$ simg2img vendor.img vendor_raw.img

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 install_android.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:

  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 0 in the U-Boot command line.

On the Host PC:

$ sudo `which fastboot` flash boot_a out/target/product/dart_mx8m/boot-<name>.img
$ sudo `which fastboot` flash boot_b out/target/product/dart_mx8m/boot-<name>.img
$ sudo `which fastboot` flash system_a out/target/product/dart_mx8m/system.img
$ sudo `which fastboot` flash system_b out/target/product/dart_mx8m/system.img
$ sudo `which fastboot` flash vendor_a out/target/product/dart_mx8m/vendor.img
$ sudo `which fastboot` flash vendor_b out/target/product/dart_mx8m/vendor.img
$ sudo `which fastboot` flash vbmeta_a out/target/product/dart_mx8m/vbmeta-<name>.img
$ sudo `which fastboot` flash vbmeta_b out/target/product/dart_mx8m/vbmeta-<name>.img
$ sudo `which fastboot` reboot

Replace <name> with the actual desired setup name according to the table in the "Images created by the Android build" section.

Android recovery mode

Enter board in Android Recovery mode

If you are using DT8MCustomBoard or you implemented any recovery key detection in uboot, the device can powered on in recovery mode by holding down the "back" (or any other recovery key) button until the end of the boot, showing the "Android Recovery" menu.

Alternatively you can issue the command reboot recovery from the Android console (or using adb shell).

Control menu in Android Recovery Mode

If the board has UP, DOWN keys (like DT8MCustomBoard)

  1. To cycle between menu items, use a short press of UP or DOWN buttons
  2. To highlight an item, use a long press of BACK or HOME buttons or long touch the touchscreen
  3. To activate an item, use a short press of ON/OFF button

If the board has no UP and DOWN keys (like SymphonyBoard)

  1. To cycle between menu items, use a short press of any buttons or select the item with the touchscreen
  2. To activate an item, use a long press of any buttons or of the touchscreen

Update Android firmware

Generate OTA packages

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

$ cd ~/var_imx-o8.1.0_1.3.0_8m/android_build
$ make PRODUCT=dart_mx8m-eng otapackage -j4 2>&1
Install OTA package to device
  • extract payload.bin and payload_properties.txt from OTA zip file
  • push file payload.bin to somewhere on the device (typically /cache folder)
  • open payload_properties.txt on an editor to copy its content, lets suppose it's like in the NXP manual:
 FILE_HASH=0fSBbXonyTjaAzMpwTBgM9AVtlBeyOigpCCgkoOfHKY=
 FILE_SIZE=379074366
 METADATA_HASH=Icrs3NqoglzyppyCZouWKbo5f08IPokhlUfHDmz77WQ/de8Dgp9zFXt8Fo+Hxccp465uTOvKNsteWU=
 METADATA_SIZE=46866
 
  • Issue the following command on adb shell:
 update_engine_client --payload=file:///cache/payload.bin --update --headers="FILE_HASH=0fSBbXonyTjaAzMpwTBgM9AVtlBeyOigpCCgkoOfHKY=
 FILE_SIZE=379074366
 METADATA_HASH=Icrs3NqoglzyppyCZouWKbo5f08IPokhlUfHDmz77WQ/de8Dgp9zFXt8Fo+Hxccp465uTOvKNsteWU=
 METADATA_SIZE=46866"

Note that the command argument --headers="..." contains the exact (4-line) content of the payload_properties.txt file between quotes (you can copy and paste it), including 3 newline characters.

After issuing the command, nothing seems to happen on the device, but you can monit logcat for operation progress. After a successful update you can reboot into the updated version.

You can check chapter 7 of official NXP "Android User Guide" for further "Over-The-Air (OTA) Update" examples.

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_imx-o8.1.0_1.3.0_8m/android_build
$ source build/envsetup.sh
$ lunch dart_mx8m-userdebug
$ make bootimage

Toolchain setup for manual build

Setup the toolchain path to point to arm-linux-androideabi- tools in prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin

$ export ARCH=arm64
$ export CROSS_COMPILE=~/var_imx-o8.1.0_1.3.0_8m/android_build/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-

Unlock device for fastboot

Our build behaves like any other standard Android device.

To use fastboot, you should go through the following steps

  • Settings => System => About Tablet => Build number
  • keep on tapping until you see a prompt that says "You are now a developer!"
  • Settings => System => Advanced => Developer options => OEM unlocking
  • reboot to bootloader
  • type "fastboot 0" in the U-Boot command line
  • run "sudo `which fastboot` oem unlock" from the Host PC
  • wait until the unlock process is complete
  • proceed for flashing