View source for VAR-SOM-MX6 Android

<!-- Set release according to "release" parameter in URL and use RELEASE_N7.1.1_1.0.0_VAR-SOM-MX6 as default
--> {{#vardefine:RELEASE_PARAM|{{#urlget:release}}}} <!--
--> {{#lst:Android_Platform_Customization|{{#var:RELEASE_PARAM|RELEASE_N7.1.1_1.0.0_VAR-SOM-MX6}}}} <!--
--> {{PageHeader|{{#var:HARDWARE_NAME}} - Android {{#var:ANDROID_NAME}} {{#var:ANDROID_VERSION}} Developer Guide}} {{DocImage|category1={{#var:HARDWARE_NAME}}|category2=Android}} __toc__

= Introduction<br/> =

This Wiki describes how to build and deploy Android {{#var:ANDROID_NAME}} on the {{#var:HARDWARE_NAME}}. It is based on NXP's {{#var:NXP_BSP_VERSION}} release

= Overview =

The objective of this document is to guide {{#var:HARDWARE_NAME}} Android developers to obtain Android {{#var:ANDROID_NAME}} 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:HARDWARE_NAME}} SOM and variants.

= Supported hardware and features =
{{#lst:Android_Platform_Customization|{{#var:ANDROID_SUPPORTED_HARDWARE_SECTION}}}}

= Hardware Requirements =

* You will need the Variscite {{#var:HARDWARE_NAME}} based evaluation kit.
* Debug UART cable - For serial Debugging

*  OTG {{#ifeq: {{#var:HARDWARE_NAME}} | VAR-SOM-MX6 | Micro B |  (Type C) }} to A - For adb and fastboot

== Host (PC) setup requirements ==

The host development environment for Android is based on Ubuntu and Debian, please install 
Ubuntu version 14.04/16.04 64bit LTS [http://www.ubuntu.com/download/desktop http://www.ubuntu.com/download/desktop]
or
Debian 8.4 64bit [https://www.debian.org/releases https://www.debian.org/releases]

We recommend to have Physical Build machine, but if you are running Linux in a virtual machine, please make sure you allocate at least 16GB of RAM and 32 GB swap to virtual machine.

<span style="color:red">Note: </span>Do not use other Ubuntu or Debian releases, than the ones recommended above.

=== Install required packages on host PC ===
<pre>
$ sudo apt-get -y install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev gcc-multilib g++-multilib \
libc6-dev-i386 lib32ncurses5-dev x11proto-core-dev libx11-dev lib32z-dev ccache libgl1-mesa-dev libxml2-utils xsltproc \
unzip mtd-utils u-boot-tools lzop liblzo2-2 liblzo2-dev zlib1g-dev liblz-dev uuid uuid-dev android-tools-fsutils bc
</pre>

=== Configure GIT account ===
<pre>
$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"
</pre>

=== Install the OpenJDK ===
Android Nougat requires OpenJDK 8.

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

<span style="color:red">Note: </span>The build process requires about 135GB of free space.

= <span style="line-height: 1.5em;">Obtain source code</span> =

<span style="line-height: 1.5em;">Variscite's Linux kernel and U-Boot are available through Github.<br>
Required patches for the Android file system are under: {{#var:ANDROID_VARFTP_PATCH_DIR}} in Variscite's FTP<br>
<br>
Files:<br>
* {{#var:ANDROID_VARFTP_BASE_PATCH_FILE}} - NXP's i.MX6 {{#var:ANDROID_NXP_VERSION}} original BSP patch files.<br>


== <span style="line-height: 1.5em;">Get NXP's Android Release Package</span> ==
 $ mkdir {{#var:BUILD_FOLDER}}
 $ cd {{#var:BUILD_FOLDER}}
 $ curl -o ~/Downloads/{{#var:ANDROID_VARFTP_BASE_PATCH_FILE}} {{#var:ANDROID_VARFTP_PATCH_DIR}}{{#var:ANDROID_VARFTP_BASE_PATCH_FILE}}
 $ tar xvf ~/Downloads/{{#var:ANDROID_VARFTP_BASE_PATCH_FILE}}

== Download Google Android {{#var:ANDROID_VERSION}} ==
 $ mkdir -p ~/bin
 $ curl -o ~/bin/repo http://commondatastorage.googleapis.com/git-repo-downloads/repo
 $ chmod a+x ~/bin/repo
 $ export PATH=~/bin:$PATH
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ cd {{#var:BUILD_FOLDER}}
 $ sed -i '/repo sync/ised -i "s+git.freescale.com/proprietary/+github.com/NXP+g" .repo/manifests/*' imx-o8.0.0_1.0.0_ga/imx_android_setup.sh
 $ WORKSPACE=`pwd` android_builddir=`pwd`/imx-o8.0.0_1.0.0_ga/android_build/ imx-o8.0.0_1.0.0_ga/imx_android_setup.sh
* Note: Since Oreo the distribution of Android Source code is partially hosted on Linux Foundation https://source.codeaurora.org/
Let the script finish and it should create "android_build" folder
 $ cd imx-o8.0.0_1.0.0_ga/android_build; mkdir -p vendor/variscite/
| 
 $ mkdir {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
 $ cd  {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
 $ repo init -u https://android.googlesource.com/platform/manifest -b {{#var:ANDROID_MANIFEST_BRANCH}}
 $ repo sync -j4
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | N7.1.2_2.0.0 |
 $ cd system/tools
 $ git clone https://android.googlesource.com/platform/system/tools/bpt
 $ cd bpt
 $ git checkout -b n7.1.2_2.0.0-ga b7c3059e5d8c408f60222edc898ef1c229d8fc2d
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
 ||}}
|}}

== Clone Variscite's U-Boot and Linux kernel sources ==
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ cd vendor/variscite/
 $ git clone {{#var:U-BOOT_GIT}} -b {{#var:U-BOOT_BRANCH}}
 $ git clone {{#var:KERNEL_GIT}} kernel_imx -b {{#var:KERNEL_BRANCH}}
|
 $ mkdir -p {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/bootable/bootloader
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/bootable/bootloader
 $ git clone {{#var:U-BOOT_GIT}} -b {{#var:U-BOOT_BRANCH}}
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
 $ git clone {{#var:KERNEL_GIT}} kernel_imx -b {{#var:KERNEL_BRANCH}}
}}

{{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 ||
== <span style="line-height: 1.5em;">Apply all the i.MX Android patches with Freescale i.MX6 support</span> ==
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
 $ source ../{{#var:ANDROID_BASE_SRC_DIR}}/code/{{#var:ANDROID_NXP_VERSION}}/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  ../{{#var:ANDROID_BASE_SRC_DIR}}/code/{{#var:ANDROID_NXP_VERSION}} {{#var:ANDROID_NXP_LOCAL_BRANCH}}
 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
 *************************************************************
}}

== <span style="line-height: 1.5em;">Apply Variscite's i.MX6 platforms' patches</span> ==
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ cd {{#var:BUILD_FOLDER_ANDROID}}/device
| 
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/device
|}}
 $ git clone {{#var:ANDROID_VARISCITE_GIT}} -b {{#var:ANDROID_VARISCITE_BRANCH}} variscite
 $ variscite/scripts/install.sh

= Build Android Images =

Change to Android top level directory.
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ cd {{#var:BUILD_FOLDER_ANDROID}}
| 
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
|}}
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ source build/envsetup.sh
 $ lunch var_mx6-eng
 or
 $ lunch var_mx6-userdebug
<span style="color:red">Note: </span> var_mx6-userdebug creates a debuggable version of Android.
var_mx6-eng creates an engineering version of Android. Development mode enable and development tools are available on target.
|
 $ source build/envsetup.sh
 $ lunch var_mx6-eng
 or
 $ lunch var_mx6-user
<span style="color:red">Note: </span> var_mx6-user creates a production version of Android.
var_mx6-eng 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 ==
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/recovery/root/fstab* out/target/product/var_mx6/root/fstab*

== Build Android for SD card ==
 $ make -j4 BUILD_TARGET_DEVICE=sd 2>&1 | tee build1-1.log

*Note: When running Android from an SD card, the eMMC will be detected and presented as an SD card storage.

== Build Android for on-SOM eMMC ==
 $ make -j4 BUILD_TARGET_DEVICE=emmc 2>&1 | tee build1-1.log

=== Special notes for DART-MX6: user builds for eMMC ===
Due to HW specific features, dm-verity feature has been disabled on user builds for eMMC on DART-MX6.

To enable this feature, follow next steps:

* correctly set PRODUCT_SYSTEM_VERITY_PARTITION in device/variscite/imx6/var_mx6.mk
* enable verify in device/variscite/var_mx6/fstab_emmc_dart.freescale

The comments in the files will suggest the detailed actions.

== Build for NAND ==
<span style="color:red">Note: </span> 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/<br/>
{| class="wikitable"
|-
! scope="col" | Image<br/>
! scope="col" | Description<br/>
|-
| system.img
| Android system image file.<br/>SOM agnostics.
|-
| u-boot-var-imx6-nand.img
| U-Boot for nand used in eMMC boot.<br/>SOM agnostics.
|-
| u-boot-var-imx6-sd.img
| U-Boot for SD card boot.<br/>SOM agnostics.
|-
| boot-<name>-<touch>.img<br>recovery-<name>-<touch>.img
| 
|-
| <name> is one of:
| som-mx6q - Supports VAR-SOM-MX6Q and VAR-SOM-MX6D<br>som-mx6dl - Supports VAR-SOM-MX6DL and VAR-SOM-MX6S<br>som-solo - Supports VAR-SOM-SOLO and VAR-SOM-DUAL
|-
| <touch> - is "r" or "c"
| r = resistive touch display<br>c = capacitive touch dispaly
|-
|}

{| class="wikitable"
|-
! scope="col" | Setup Name<br/>
! scope="col" | Images Names<br/>
! scope="col" | SOM type<br/>
! scope="col" | Carrier Board type<br/>
! scope="col" | LCD Type<br/>
! scope="col" | Evaluation Kit name<br/>
|-
| style="padding: 5px;"| som-mx6qp-c
| style="padding: 5px;"| boot-som-mx6qp-c.img,<br>recovery-som-mx6qp-c.img
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad Plus)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Capacitive touch
| style="padding: 5px;"| VAR-DVK-MX6_V2-PRO,<br>VAR-STK-MX6_V2
|-
| style="padding: 5px;"| som-mx6qp-r
| style="padding: 5px;"| boot-som-mx6qp-r.img,<br>recovery-som-mx6qp-r.img
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad Plus)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Resistive touch
| style="padding: 5px;"| VAR-DVK-MX6_V2,<br>VAR-STK-MX6_V2
|-
| style="padding: 5px;"| som-mx6qp-vsc
| style="padding: 5px;"| boot-som-mx6qp-vsc.img,<br>recovery-som-mx6qp-vsc.img
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad Plus)
| style="padding: 5px;"| VAR-SOLOCustomBoard
| style="padding: 5px;"| Capacitive LVDS touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| som-mx6q-c
| style="padding: 5px;"| boot-som-mx6q-c.img,<br>recovery-som-mx6q-c.img
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad / Dual)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Capacitive touch
| style="padding: 5px;"| VAR-DVK-MX6_V2-PRO,<br>VAR-STK-MX6_V2
|-
| style="padding: 5px;"| som-mx6q-r
| style="padding: 5px;"| boot-som-mx6q-r.img,<br>recovery-som-mx6q-r.img
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad / Dual)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Resistive touch
| style="padding: 5px;"| VAR-DVK-MX6_V2,<br>VAR-STK-MX6_V2
|-
| style="padding: 5px;"| som-mx6q-vsc
| style="padding: 5px;"| boot-som-mx6q-vsc.img,<br>recovery-som-mx6q-vsc.img
| style="padding: 5px;"| VAR-SOM-MX6_V2 (Quad / Dual)
| style="padding: 5px;"| VAR-SOLOCustomBoard
| style="padding: 5px;"| Capacitive LVDS touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| som-mx6dl-c
| style="padding: 5px;"| boot-som-mx6dl-c.img,<br>recovery-som-mx6dl-c.img
| style="padding: 5px;"| VAR-SOM-MX6_V2 (DualLite/ Solo)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Capacitive touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| som-mx6dl-r
| style="padding: 5px;"| boot-som-mx6dl-r.img,<br>recovery-som-mx6dl-r.img
| style="padding: 5px;"| VAR-SOM-MX6_V2 (DualLite/ Solo)
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Resistive touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| som-solo-vsc
| style="padding: 5px;"| boot-som-solo-vsc.img,<br>recovery-som-solo-vsc.img
| style="padding: 5px;"| VAR-SOM-SOLO / VAR-SOM-DUAL
| style="padding: 5px;"| VAR-SOLOCustomBoard
| style="padding: 5px;"| Capacitive LVDS touch
| style="padding: 5px;"| VAR-DVK-SOLO/DUAL,<br>VAR-STK-SOLO/DUAL
|-
| style="padding: 5px;"| som-solo-c
| style="padding: 5px;"| boot-som-solo-c.img,<br>recovery-som-solo-c.img
| style="padding: 5px;"| VAR-SOM-SOLO / VAR-SOM-DUAL
| style="padding: 5px;"| VAR-MX6CustomBoard
| style="padding: 5px;"| Capacitive touch
| style="padding: 5px;"| N/A
|-
| style="padding: 5px;"| imx6q-var-dart
| style="padding: 5px;"| boot-imx6q-var-dart.img,<br>recovery-imx6q-var-dart.img
| style="padding: 5px;"| DART-MX6
| style="padding: 5px;"| VAR-DT6CustomBoard
| style="padding: 5px;"| Capacitive touch
| style="padding: 5px;"| VAR-STK-DT6,<br>VAR-DVK-DT6
|-
|}

= Boot options=

The Android boot options are:<br>
1. Directly from an SD card<br>
2. U-Boot boots from NAND flash, and the rest of the Android images from the 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
<pre>
$ sudo ./var-mksdcard.sh -f SETUP_NAME /dev/sdX;sync
</pre>
* Replace SETUP_NAME with the actual desired setup name accrding to the second table in the [[#Images_created_by_the_Android_build_for_Variscite_MX6_system|"images created" section]].
* Replace /dev/sdX with your true device, You can identify it with dmesg.

=== Boot From SD card ===
{{#lst:Android_Recovery_SD_card|BOOT_FROM_SD_CARD}}

== Flash and boot Android from eMMC ==
eMMC based system consist of:<br>
#SPL and U-Boot on NAND flash<br>
#Rest of Android images in eMMC<br>

=== Preparing images ===

All Android built images but system.img are ready for flashing out of the default build.<br>

The default system.img  {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 | and vendor.img |}} format is suitable for flashing using fastboot, and must be modified for flashing using 'dd'.

 $ cd out/target/product/var_mx6
 $ simg2img system.img system_raw.img
{{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
<pre>
 $ simg2img vendor.img vendor_raw.img
</pre>
|}}
{{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 {{Varlink|Android Recovery SD card|RELEASE_N7.1.1_1.0.0_VAR-SOM-MX6|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 ====
<pre>
$ sudo apt-get install android-tools-adb android-tools-fastboot
</pre>

<span style="color:red">Note: </span> Make sure you built Android for eMMC
<br>
'''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 usb0''' in the U-Boot command line.

'''On the Host PC:'''
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 | 
 $ sudo `which fastboot` flash boot out/target/product/var_mx6/boot-''SETUP_NAME''.img
 $ sudo `which fastboot` flash recovery out/target/product/var_mx6/recovery-''SETUP_NAME''.img
 $ sudo `which fastboot` flash system out/target/product/var_mx6/system.img
 $ sudo `which fastboot` flash vendor out/target/product/var_mx6/vendor.img
|
 $ sudo `which fastboot` flash boot out/target/product/var_mx6/boot-''SETUP_NAME''.img
 $ sudo `which fastboot` flash recovery out/target/product/var_mx6/recovery-''SETUP_NAME''.img
 $ sudo `which fastboot` flash system out/target/product/var_mx6/system.img
}}
 $ sudo `which fastboot` reboot
Replace ''SETUP_NAME'' with the actual desired setup name accrding to the second table in the [[#Images_created_by_the_Android_build_for_Variscite_MX6_system|"images created" section]].

=== 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 ====

# 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:
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ cd {{#var:BUILD_FOLDER_ANDROID}}/device
| 
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
|}}

 # 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:<pre>$ out/host/linux-x86/bin/adb sideload out/target/product/var_mx6/var_mx6-ota-<data>-<image-id>.zip</pre>
#reboot this device
<span style="color:red">Note: </span>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.
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ cd {{#var:BUILD_FOLDER_ANDROID}}
 $ source build/envsetup.sh
 $ lunch var_mx6-eng
 or
 $ lunch var_mx6-userdebug
|
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}} 
 $ source build/envsetup.sh
 $ lunch var_mx6-eng
 or
 $ lunch var_mx6-user
}}
 $ make bootimage

== Toolchain setup for manual build kernel and U-Boot ==
 $ export ARCH=arm
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ export CROSS_COMPILE={{#var:BUILD_FOLDER_ANDROID}}/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/arm-linux-androideabi-
|
{{#ifeq: {{#var:ANDROID_NXP_VERSION}} | N7.1.2_2.0.0 |
Setup the toolchain path to point to arm-linux-androideabi- tools in prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin
|
Setup the toolchain path to point to arm-eabi- tools in prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin
 $ export CROSS_COMPILE={{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi-
| }}
||}}

== Manual build Bootloader&nbsp; ==

Change directory to U-Boot
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ cd {{#var:BUILD_FOLDER_ANDROID}}/vendor/variscite/uboot-imx
|
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/bootable/bootloader/uboot-imx
||}}
Execute following commands:
<pre>
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
</pre>
<br/>This command will generate the U-Boot images 'SPL' and 'u-boot.img'.

== Manual build Android Linux Kernel and modules ==
 {{#ifeq: {{#var:ANDROID_NXP_VERSION}} | O8.0.0_1.0.0 |
 $ cd {{#var:BUILD_FOLDER_ANDROID}}/vendor/variscite/kernel_imx
|
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}/kernel_imx 
 ||}}
 $ make mrproper
 $ make imx_v7_var_android_defconfig
 $ make -j4
 $ make -j4 uImage LOADADDR=0x10008000
 
This will generate the uImage (kernel image) in the kernel/arch/arm/boot folder


{{#ifeq: {{#var:ANDROID_PARTITION_TYPE}} | image |
== Changing Partition structure of Android eMMC / SD card ==
 $ cd {{#var:BUILD_FOLDER}}/{{#var:BUILD_FOLDER_ANDROID}}
 Open device/fsl/common/partition/device-partitions.bpt
<br/>
Modify the partition size as you want, compile the image partition-table.img
<br/>
If you change partition order don't forget to change mount options in following files 
<br/>
For eMMC : 
 device/variscite/var_mx6/fstab_emmc_dart-f2fs.freescale
 device/variscite/var_mx6/fstab_emmc_dart.freescale
 device/variscite/var_mx6/fstab_emmc-f2fs.freescale
 device/variscite/var_mx6/fstab_emmc.freescale
For SD : 
 device/variscite/var_mx6/fstab_sd_dart-f2fs.freescale
 device/variscite/var_mx6/fstab_sd_dart.freescale
 device/variscite/var_mx6/fstab_sd-f2fs.freescale
 device/variscite/var_mx6/fstab_sd.freescale

By default below partition scheme is used.
 
 Number  Start (sector)    End (sector)  Size       Code  Name
    1            2048           67583   32.0 MiB    FFFF  boot
    2           67584          133119   32.0 MiB    8300  recovery
    3          133120         3278847   1.5 GiB     FFFF  system
    4         3278848         4327423   512.0 MiB   FFFF  cache
    5         4327424         4343807   8.0 MiB     FFFF  device
    6         4343808         4351999   4.0 MiB     FFFF  misc
    7         4352000         4356095   2.0 MiB     FFFF  datafooter
    8         4356096         4360191   2.0 MiB     FFFF  metadata
    9         4360192         4362239   1024.0 KiB  FFFF  presistdata
   10         4362240        14675967   4.9 GiB     FFFF  userdata
   11        14675968        14678015   1024.0 KiB  0700  fbmisc
||}}