[[PageOutline]]

= Gateworks Ventana Android Board Support Package =

Gateworks supports the following Android versions:
 * Android 5.1.1 (Aka 'Lollipop')
 * Android 4.4 (Aka '!KitKat')
 * Android 4.3 (Aka 'Jelly Bean-MR2')

For a feature list please see [wiki:Android Gateworks Android]

[=#variants]
= Android Build Variants =
The Android build system supports different build variants. The two that we build and support are:
 * eng - used for development and hacking
  - installs modules tagged with 'eng', 'debug', 'user', and/or 'development'
  - installs non-APK modules that have no tags specified
  - installs APKs according to the product definition files, in addition to tagged APKs
  - default.prop disables security and allows debugging:
{{{#!bash
ro.secure=0
ro.debuggable=1
}}}
  - {{{adb}}} runs as user 'root' is enabled by default (this allows commands such as {{{adb remount}}} and {{{adb push}}})
 * user - intended for final release
  - installs modules tagged with 'user'
  - installs non-APK modules that have no tags specified
  - installs APKs according to the product definition files; tags are ignored for APK modules.
  - default.prop disables security and allows debugging:
{{{#!bash
ro.secure=1
ro.debuggable=0
}}}
  - {{{adb}}} runs as user 'shell' and is disabled by default ({{{adb}}} running as non-root dis-allows commands such as {{{adb remount}}} and {{{adb push}}} but allows {{{adb install}}}


[=#prebuilt]
= Gateworks Precompiled Android Binary =
Gateworks provides pre-built Android images that you can evaluate without building the source if needed. You have the following options:
 * purchase a pre-installed USB stick from the [http://shop.gateworks.com/index.php?route=product/product&path=70_82&product_id=133 Gateworks Online Shop]
 * download UBI image if you have a board with 2GB of NAND flash and want to boot Android from flash
 * download tarball and image a removable block storage device (mSATA / USB / uSD)

Latest images:
 * Android 5.1.1 (Lollipop):
  * Built on 2016-12-01 from Gateworks Android BSP:
   * Source: ​https://github.com/Gateworks/imx_android/tree/gateworks_l5.1.1_2.1.0-ga
   * Tarball containing UBI and binaries for block storage imaging: [http://blog.gateworks.com/?wpdmpro=gateworks-l5.1.1_2.1.0-ga-eng-20161201.tar.bz2 gateworks-l5.1.1_2.1.0-ga-eng-20161201.tar.bz2] (sha256sum:4c7951b3c0bbcf3806b5cd524d92fc42a6b221c73160f4361267940f0bd7ea7d). Use {{{tar -xvf <file.tar.gz> imx_l5.1.1_2.1.0-ga/android.ubi}}} to only extract the ubi.
   * [wiki:Android Android Wiki]
   * Based on Freescale l5.1.1_2.1.0-ga source
 * Android 4.4 (!KitKat):
  * Built on 2016-02-10 from Gateworks Android BSP:
   * Source: https://github.com/Gateworks/imx_android/tree/gateworks_kk4.4.3_2.0.0-ga
   * [wiki:Android Android Wiki]
   * Based on Freescale kk4.4.3_2.0.0-ga source
  * ubi images ('''requires 2GB NAND'''):
   * [http://blog.gateworks.com/?wpdmpro=gateworks-kk4.4.3_2.0.0-ga-user-20160210.ubi] (sha256sum:1575480f030afa1cad42fe7cb719a1318367092abe9c523a2e8bf13397c8b4a9)
   * [http://blog.gateworks.com/?wpdmpro=gateworks-kk4.4.3_2.0.0-ga-eng-20160210.ubi] (sha256sum:ed0b090bf446049e9442e9bbe342e1750bae581bcf3a82d3d595a2212dd90e18)
  * tarballs (for imaging onto removable block storage devices):
   * [http://blog.gateworks.com/?wpdmpro=gateworks-kk4.4.3_2.0.0-ga-user-20160210.tar.bz2] (sha256sum:243fa226df7d4c973e36d3310793594feb10ede2c813c6bd5603d1544a70259e)
   * [http://blog.gateworks.com/?wpdmpro=gateworks-kk4.4.3_2.0.0-ga-eng-20160210.tar.bz2] (sha256sum:f95428b42e8c40c420b00d63d1dc2b40c46b1950f47f0db996929561dd14308b)

See [#variants above] for differences on the {{{eng}}} vs {{{user}}} build variant

Once you have installed the pre-built image using one of the methods below please see [wiki:Android#BootingAndroid here] for important instructions on booting Android


== Install on 2GB NAND Flash via ubi file ==
To install Android in flash for boards with 2GB of NAND from a downloaded ubi image:
 1. Download Binary ubi (see above for options)
 2. Place ubi on tftp server or removable storage
 3. Boot target and break into the bootloader
 4. Update NAND flash with image.ubi served from a tftp server (modify the ip addrs below for your network):
{{{#!bash
setenv ipaddr 192.168.1.1
setenv serverip 192.168.1.254
tftp ${loadaddr} android.ubi && nand erase.part rootfs && nand write ${loadaddr} rootfs ${filesize}
}}}
  * For more examples of loading images into uboot from network/mmc/usb see [wiki:linux/ubi#WorkingwithUBIinu-bootBootloader here]


== Install on a 2GB+ removable block storage device (USB/SATA/MMC) ==
The partitioning scheme Gateworks uses for Android on block storage is the following:
||= Partition =||= Size =||= Name     =||= Filesystem =||= Description =||
|| N/A         || 1MB    ||  -         || -            || SPL, bootloader, env ||
|| /dev/sdc1   || 20MB   || BOOT       || ext4         || Android boot partition (bootscript, kernel, dtbs, ramdisk) ||
|| /dev/sdc2   || 20MB   || RECOVERY   || ext4         || Android's recovery partition ||
|| /dev/sdc3   || -      || extended   || -            || extended partition ||
|| /dev/sdc4   || -      || DATA       || ext4         || userdata ||
|| /dev/sdc5   || 512MB  || SYSTEM     || ext4         || Android's /system partition (ROM) ||
|| /dev/sdc6   || 50MB   || CACHE      || ext4         || cache ||
|| /dev/sdc7   || 10MB   || VENDOR     || ext4         || vendor ||
|| /dev/sdc8   || 10MB   || MISC       || ext4         || misc  ||


To install on a 2GB+ removable block storage device (USB/SATA/MMC) from a downloaded tarball you first need to know the Linux device name of the storage device (use the Disks tool, or look at {{{/var/log/messages}}} for this info). Assuming {{{/dev/sdc}}} you can:
 1. Download Binary tarball (see above for options)
 2. extract the binary (example using gateworks-kk4.4.3_2.0.0-ga-user-20150327.tar.gz)
{{{#!bash
tar xvf gateworks-kk4.4.3_2.0.0-ga-user-20150327.tar.gz
}}}
 3. cd into the directory with the build artifacts and run the mksdcard.sh script:
{{{#!bash
cd kk4.4.3_2.0.0-ga_user
sudo ./mksdcard.sh /dev/sdc
}}}

Note that the partition layout above requires 8 partitions which are typically not supported with built-in SDIO host controllers (which is what you are using if your microSD shows up as /dev/mmcblk*). We recommend using a USB based microSD card reader/writer which can be found from office supply stored for under $5.


[=#building]
= Building Android for Ventana from source =

== Pre-requisites ==

[=#dev-host]
=== Build Host ===
Per the Android documentation [https://source.android.com/source/building.html here] you should have a build host with the following:
 * Linux or Mac
 * 64bit environment
 * 100GB (for a single build, 150GB or more for multiple builds, and more if you use ccache)
 * Python 2.6 - 2.7
 * GNU Make 2.81 - 3.82
 * JDK 6 (for Gingerbread through !KitKat)
 * Git 1.7 or newer

Gateworks uses Ubuntu 14.04/13.10 64bit build hosts although other configurations may work.

A virtual machine is possible to use and Gateworks has verified that our latest BSP builds with the popular [http://nathanpfry.com/builduntu-virtual-machine-android-rom-compiling/ BuilduntuVM] based on Xubuntu with the following changes (based on BuildubuntuVM v1.5):
 * Download from [http://nathanpfry.com/builduntu-virtual-machine-android-rom-compiling/ BuilduntuVM page]
 * change Networking mode to bridged instead of NAT - !VirtualBox NAT can be unreliable with the heavy traffic a repo sync does.
 * adjust the memory allocated to the VM to a level appropriate for your host (defaults to 4GB, we've tested with 2GB)
 * install make v3.81 (make v4.0 on BuilduntuVM needs to be downgraded for Android !KitKat builds):
{{{#!bash
wget -o make.tar.gz http://ftp.gnu.org/gnu/make/make-3.81.tar.gz
tar -xvzf make-3.81.tar.gz
cd make-3.81
./configure
sudo make install
hash -r
}}}
 * install Oracle Java6 (openjdk7 on BuilduntuVM needs to be downgraded for Android !KitKat builds):
{{{#!bash
sudo apt-get install oracle-java6-installer
}}}
 * install a couple other packages our BSP requires:
{{{#!bash
sudo apt-get install u-boot-tools uuid-dev liblzo2-dev
}}}


References:
 * https://source.android.com/source/building.html
 * https://source.android.com/source/initializing.html


[=#network]
=== Network Connection and Disk Space ===
The initial {{{repo sync}}} of Android transfers approximately 15GB of data from the Internet. This can take several hours depending on your bandwidth.

While the source-code accounts for approximately 15GB of data, you will need an additional 25GB or so (40GB total) for a build.


[=#jdk]
=== JDK ===
Different versions of Android require different versions of a Java Development Kit (JDK). Note that multiple versions of Java can easily co-exist on an OS by using either a {{{JAVA_HOME}}} env variable pointing to the root of a JDK, or by using {{{Linux alternatives}}}. To avoid switching back and forth, Gateworks recommends setting a {{{JAVA_HOME}}} env variable.

JDK Requirements:
 * Android Lollipop - OpenJDK 7:
  - Ubuntu >= 14.04:
{{{#!bash
sudo apt-get update
sudo apt-get install openjdk-7-jdk
export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
}}}
 * Android Gingerbread through Kitkat: Oracle JDK 6:
  - Ubuntu 14.04/13.10:
{{{#!bash
# add the PPA with updated builds of Java 6JDK compatible with 13.10
sudo add-apt-repository ppa:webupd8team/java # hit enter when prompted
# install the package
sudo apt-get update && sudo apt-get install oracle-java6-installer # read and accept the license agreement
# verify the correct version is installed
java -version
 java version "1.6.0_45"
 Java(TM) SE Runtime Environment (build 1.6.0_45-b06)
 Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode)
export JAVA_HOME=/usr/lib/jvm/java-6-oracle
}}}

Note that you can have multiple JDK's installed at the same time and use 'update-alternatives' to configure which version of ''java'' and ''javac'' is used.

References:
 * https://source.android.com/source/initializing.html#installing-the-jdk


[=#required-packages]
=== Packages ===
Ubuntu 14.04 (Note that most of these instructions were found [http://forum.xda-developers.com/showthread.php?t=2639611&page=1 here]):
{{{#!bash
sudo apt-get purge icedtea-\* icedtea6-\*
sudo apt-get install git gnupg ccache lzop flex bison gperf build-essential zip curl \
  zlib1g-dev zlib1g-dev:i386 libc6-dev lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev \
  libx11-dev:i386 libreadline6-dev:i386 lib32z1-dev libgl1-mesa-glx:i386 libgl1-mesa-dev \
  g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc libreadline6-dev \
  lib32readline-gplv2-dev libncurses5-dev bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev \
  lib32bz2-dev squashfs-tools pngcrush schedtool dpkg-dev
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
sudo apt-get install u-boot-tools uuid-dev liblzo2-dev librsvg2-dev intltool mtd-utils pv
cpan App::cpanminus # type 'yes' to let it automatically choose settings for you
cpan Switch
}}}

Ubuntu 13.10:
{{{#!bash
sudo apt-get install git-core lzop ccache gnupg flex bison gperf build-essential \
  zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5 lib32z1 lib32bz2-1.0 \
  lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev \
  libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
  libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev \
  libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 \
  libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev \
  libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.8-dev \
  python gcc g++ cpp gcc-4.8 g++-4.8
sudo apt-get install u-boot-tools uuid-dev liblzo2-dev librsvg2-dev intltool mtd-utils pv
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
}}}

Ubuntu 12.04:
{{{#!bash
sudo apt-get install git gnupg flex bison gperf build-essential \
  zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
  libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
  libgl1-mesa-dev g++-multilib mingw32 tofrodos \
  python-markdown libxml2-utils xsltproc zlib1g-dev:i386
sudo apt-get install u-boot-tools uuid-dev liblzo2-dev librsvg2-dev intltool mtd-utils pv
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
}}}


References:
 * https://source.android.com/source/initializing.html#setting-up-a-linux-build-environment


[=#source]
== Obtaining Source ==
Android AOSP (Android Open Source Project) source is spread across 300+ git repositories. The [https://source.android.com/source/developing.html 'repo' tool] is used as a front-end to git to manage working with all of these repos. A manifest file describes all the repos used, where they can be found, what branch to checkout, and where to check it out to in the resulting directory tree. A {{{repo sync}}} command is what fetches or updates all these repos and an initial sync will pull down approximately 15GB of data from the Internet.

Of the roughly 334 various project trees that create Android, Freescale adds 13 new projects (for Freescale specific features/subsystems) and modifies 28 projects from upstream Android sources (to add support for Freescale features).


=== Access Control ===
Freescale has several projects and patches required for Android on the IMX6 CPU, some of which require a End User License Agreement (EULA). They distribute these as a tarball of patches which is difficult to work with, especially as Gateworks and our end users also apply patches on top of these to add functionality.

Gateworks puts the projects that are not Open Source in a bitbucket account with access control. If you need to build and develop Android source for Ventana, you will need to contact support@gateworks.com requesting access to the gateworks-android bitbucket team. You will need to sign our EULA and provide an ssh public key ({{{~/.ssh/id_rsa.pub}}}) for each user and workstation you need access from. To learn how to generate an SSH key on your linux host see [https://confluence.atlassian.com/pages/viewpage.action?pageId=270827678 here]. You will want to create a key without a passphrase as the whole point of this key is to automate connection to the repo's without requiring entering a passphrase (if you are prompted for a passphrase each time you contact a repo the {{{repo}}} tool will get in the way of entering in the passphrase)

Once you have confirmation from support@gateworks.com that we have added access for your ssh key(s) you need to do the following on your development host to add the bitbucket RSA key fingerprint to your development host so that you are not prompted for it during a {{{repo sync}}}:
{{{
#!bash
ssh-keyscan -H git.bitbucket.org >> ~/.ssh/known_hosts
}}}


[=#fetch]
=== Fetching Source ===
Once you have access to the private repositories (see [wiki:Android/Building#AccessControl above]) you can use the following steps to create a build directory for Android.

Branches:
 * gateworks_l5.1.1_2.1.0-ga - Android Lollipop 5.1 (Latest Gateworks Android release)
 * gateworks_kk4.4.3_2.0.0-ga - Android !KitKat 4.4.3
 * gateworks_jb4.3_1.1.0-ga - Android Jelly Bean 4.3

1. Create a directory for your Android build:
{{{#!bash
mkdir gateworks-android
cd gateworks-android
}}}

2. Get {{{repo}}} tool. This tool uses xml manifests to pull down multiple repos:
{{{#!bash
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ./repo
chmod a+x ./repo
}}}

3. Initialize android source repo (this pulls down the manifest of projects that make up the Gateworks Ventana Android BSP):
{{{#!bash
./repo init -u https://github.com/Gateworks/imx_android.git -b gateworks_l5.1.1_2.1.0-ga
}}}
 * use any of the above branches if you wish to use an older release
 * repeat this with a different branch name any time you wish to change to a new branch without pulling down all the repo's again in their entirety

4. (optional) pin the repo versions to the latest version which was known to have been successfully built by the Gateworks nightly build server:
{{{#!bash
wget http://dev.gateworks.com/android/lp-5.1.1/snapshot.xml # fetch the pinned manifest from the last successful nightly build
mv snapshot.xml .repo/manifest.xml # copy over the generic un-pinned manifest
}}}
 * the repo init command will fetch a repo 'manifest' which refers to various source repositories and branches but will fetch the latest changes from those branches. The Gateworks nightly build server posts the manifest pinned to the specific revision used in the build on completion of a successful build. You can also use a snapshot from a previously released pre-built binary by using the other snapshot files in ​http://dev.gateworks.com/android

5. Sync repo - this fetches the repos from the Internet (may take a while to download sources resulting in about 15GB more):
{{{#!bash
./repo sync -c -j8
}}}
 * the {{{-c}}} parameter tells repo to only fetch the current branch specified in the project manifest and can help speed up fetching as well as reduce disk space needed
 * the {{{-j}}} parameter tells repo to use multiple processes (8 in this case) and can help speed up fetching

Troubleshooting:
 * first, try {{{repo sync}}} again. Often temporary network congestion or outages may be the culprit.
  * Sometimes, a source destination may have change from the first {{{repo sync}}} you may have preformed. In this case, try {{{repo sync --force-sync}}} to force a sync to a new package location.
 * Bitbucket access issues:
  * if you see several '''Permission denied (publickey)''' errors then you have not been granted access to the Freescale proprietary repositories (see above)
  * if you see several '''The authenticity of host 'git.butbucket.org (131.103.20.168)' can't be established.''' messages then you have forgotten to add the bitbucket RSA key fingerprint to your development host (see above). Type 'yes' and hit return to add it permanently.
 * !VirtualBox VM issues:
  * when using a !VirtualBox VM the process hangs or fails with a variety of symptoms such as HTTP 500 errors. The default network behavior of !VirtualBox is to use NAT (Network Address Translation) to connect the guest system to the network and the heavy network activity of a repo sync triggers some corner cases in the NAT code. As a workaround configure !VirtualBox to use bridged network instead of NAT.
 * For various other network troubleshooting issues please see the official Android source download documentation [https://source.android.com/source/downloading.html here] and their known issues [https://source.android.com/source/known-issues.html#source-sync here]. Various issues that can be common are discussed there with workarounds:
  * behind a proxy or firewall - set HTTP_PROXY and HTTPS_PROXY and use a single thread ({{{repo sync -j1}}})
  * download failures (typically hangs or 406 errors) - disable tcp window scaling and/or use a single thread:
{{{#!bash
sudo sysctl -w net.ipv4.tcp_window_scaling=0
repo sync -j1
}}}
  * IP bandwidth exceeded (common if you try to {{{repo sync}}} a full tree more than once per day, or have multiple people/systems doing it behind a NAT firewall) - use authentication by [https://android.googlesource.com/new-password obtaining a password] and adding an '/a' path to the beginning of the URL to android.googlesource.com directory

References:
 * https://source.android.com/source/developing.html
 * https://source.android.com/source/downloading.html
 * https://source.android.com/source/known-issues.html
 * https://udinic.wordpress.com/2014/05/24/aosp-part-1-get-the-code-using-the-manifest-and-repo/


[=#repo]
=== Keeping up to date and/or pinning source with repo ===
When building projects that use multiple source repositories any repository may change and thus make your working directory out of date. Because Android uses hundreds of projects with their own repositories this can make it difficult to keep in sync - this is where the {{{repo}}} tool comes in handy.

The {{{repo sync}}} command will update all repositories with upstream changes:
{{{#!bash
repo sync --quiet
}}}

You can override the default Manifest by using a '''local manifest''' if you want to keep in sync with the upstream manifest yet make some minor change like pin a specific project or add a couple of projects. Reasons for doing this could be:
 * adding new projects
 * pinning certain projects
 * removing certain projects

To use a local manifest create {{{.repo/local_manifest.xml}}} and it will be merged with {{{.repo/manifest.xml}}} by the repo tool whenever the manifest is used. You can use the '''remove-project''' directive to remove a project that you don't want and even add it back with your own choices if you want something different. For example:
{{{#!xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
   <remove-project path="hardware/qcom/display" name="CyanogenMod/android_hardware_qcom_display" />
   <project path="hardware/qcom/display" name="WinSuk/android_hardware_qcom_display" />
</manifest>
}}}

The {{{repo manifest}}} command will create a snapshot of your current project's manifest allowing you to create a pinned version that can be used later to create a working directory with the various projects at the exact same state as your current working directory:
{{{#!bash
repo manifest -o snapshot.xml -r
}}}

This snapshot can then be copied over .repo/manifest.xml in a different build directory to pin the repository sources.

The Gateworks nightly build server creates a manifest snapshot like this and uploads the latest successful build to ​http://dev.gateworks.com/yocto so that it can be used to re-create a successful nightly build.

References:
 * [https://source.android.com/source/using-repo.html Official docs on using repo]
 * [http://xda-university.com/as-a-developer/repo-tips-tricks xda-university repo tips and tricks]
 * [http://wiki.cyanogenmod.org/w/Doc:_Using_manifests Cyanogenmod docs on using manifests]
 * [https://gerrit.googlesource.com/git-repo/+/master/docs/manifest-format.txt repo Manifest Format: the official, technical documentation for repo manifests]


[=#build]
== Building ==
1. Configure Android build system for 'ventana' product and desired variant (See [#variants above] for differences on the {{{eng}}} vs {{{user}}} build variant)
{{{#!bash
export JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
source build/envsetup.sh
lunch ventana-eng
}}}
 * An 'eng' build (ventana-eng) has certain debug options enabled and lowers security (makes things nice if your going to play around)
 * A 'user' build (ventana-user) is more locked down and intended for a production/shipping environment
 * This process is sometimes referred to as 'activating the shell' and must be done for each new shell (ie each time you login or open a new terminal). If this seems strange to you or if you are new to Linux build systems, you should probably only use a single shell to avoid confusion.

2. Build (takes up an additional ~25GB and takes several hours)
{{{#!bash
make 2>&1 | tee build.log
}}}

When complete the various build artifacts will be in {{{out/target/product/ventana/}}}

3. Put artifacts onto a storage device to boot. See next section using the 'mksdcard.sh' script. The following build artifacts are in {{{out/target/product/ventana/}}} grouped by the partition they belong in:
 * BOOT:
  * uImage - kernel image
  * boot/boot/uramdisk.img - initial ramdisk containing init system
  * boot/boot/6x_bootscript-ventana - u-boot bootscript (sets up android kernel cmdline)
  * boot/boot/uImage - kernel image
  * boot/boot/*.dtb - kernel device tree binary blobs
 * RECOVER:
  * ramdisk-recovery.img - initial ramdisk containing init system
 * SYSTEM:
  * system.img - filesystem image of /system directory (Android ROM)
 * USER:
  * userdata.img - user data

Note that the Android partition layout we use requires 8 partitions which are typically not supported with built-in SDIO host controllers based on standard kernel configurations (which is what you are using if your microSD shows up as /dev/mmcblk*). We recommend using a USB based microSD card reader/writer which can be found from office supply stored for under $5.


[=#create-tarball]
=== Creating a tarball of the built artifacts ===

If you would like to create an archive of the build artifacts including everything needed to image Android onto a removable block storage device as well as the NAND uib, the following will do so:
{{{#!bash
tar -cvjf l5.1.1_2.1.0-ga.tar.bz2 \
  --transform "s,^device/gateworks/ventana/,l5.1.1_2.1.0-ga/," \
  --transform "s,^out/target/product/ventana/,l5.1.1_2.1.0-ga/," \
  device/gateworks/ventana/mksdcard.sh \
  out/target/product/ventana/boot \
  out/target/product/ventana/uramdisk-recovery.img \
  out/target/product/ventana/userdata.img \
  out/target/product/ventana/system.img \
  out/target/product/ventana/android.ubi
}}}

Untaring the above archive would show:
{{{#!bash
tar xvf ../l5.1.1_2.1.0-ga.tar.bz2
l5.1.1_2.1.0-ga/mksdcard.sh
l5.1.1_2.1.0-ga/boot/
l5.1.1_2.1.0-ga/boot/boot/
l5.1.1_2.1.0-ga/boot/boot/imx6dl-gw54xx.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6dl-gw53xx.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6dl-gw52xx.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6dl-gw51xx.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6dl-gw551x.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6dl-gw552x.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6q-gw54xx.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6q-gw53xx.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6q-gw52xx.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6q-gw51xx.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6q-gw551x.dtb
l5.1.1_2.1.0-ga/boot/boot/imx6q-gw552x.dtb
l5.1.1_2.1.0-ga/boot/boot/uImage
l5.1.1_2.1.0-ga/boot/boot/6x_bootscript-ventana
l5.1.1_2.1.0-ga/boot/boot/uramdisk.img
l5.1.1_2.1.0-ga/uramdisk-recovery.img
l5.1.1_2.1.0-ga/userdata.img
l5.1.1_2.1.0-ga/system.img
l5.1.1_2.1.0-ga/android.ubi
}}}


[=#rebuild]
== Updating and Re-building ==
From time to time you may want to refresh your sources with upstream changes from Gateworks and elsewhere. The Gateworks Android BSP manifest file fetched from the {{{repo init}}} command controls what projects get fetched and where they go. The {{{repo sync}}} command with both update the manifest (in case projects have been added, removed, or changed) and updates all the individual git repos it references.
{{{#!bash
./repo sync --quiet
}}}
 * The quiet flag reduces most of the output allowing you to easily progress
 * This only pulls down 'changes' that have been made
 * As this alters source-code, do not do this while a build is running

Now you can repeat the steps above to rebuild. You do not need to do a {{{make clean}}}.


[=#install]
== Flashing Android to NAND Flash ==
If you have a board with 2GB NAND Flash, you can use the {{{nand_update}}} uboot script to flash the Android ubi file from a tftp server.

First you must copy the ubi from your build directory to your tftp server root directory:
{{{#!bash
cp out/target/product/ventana/android.ubi /tftpboot
}}}

The nand_update script will tftp the file file represented by the {{{image_rootfs}}} env variable from the server represented by the {{{serverip}}} env variable and flash it to the rootfs partition:
{{{#!bash
setenv image_rootfs android.ubi
run nand_update
reset
}}}


== Creating a bootable removable storage device ==
You can create a bootable removable storage device (micro-SD / USB stick / mSATA disk) with the mksdcard.sh script (located in {{{device/gateworks/ventana/mksdcard.sh}}} of the source directory). Assuming the removable device is in {{{/dev/sdc}}} on your linux host '''(this is an assumption here - please verify on your system with something like the 'Disks' tool on Ubuntu)''':
{{{#!bash
sudo device/gateworks/ventana/mksdcard.sh /dev/sdc
}}}
 * Note that sanity checks are done to ensure the device specified appears to be removable by checking its size. If you get an 'invalid disk' error because of this and want to force the script you can execute it as:
{{{#!bash
sudo device/gateworks/ventana/mksdcard.sh /dev/sdc ventana --force
}}}
 * If using an archive of build artifacts you will find the mksdcard.sh script in the root directory and can run it from there

Notes:
 * you must have a device of 2GB or larger

Booting:
 * Please see [wiki:Android/Booting here] for important instructions on booting Android from removable media