Difference between revisions of "IoTGateway/BSP/Android/ABV2 User Guide iMX6"

From ESS-WIKI
Jump to: navigation, search
(Created page with "<big><big><big>Android BSP User Guide for iMX6 series</big></big></big> <!-- {| align="right" | __TOC__ |} --> =Getting Started= ==<span style="color:#0070c0;">Prerequisites...")
 
m (Winston.huang moved page ABV2 User Guide iMX6 to IoTGateway/BSP/Android/ABV2 User Guide iMX6 without leaving a redirect: appropriate directory hierarchy)
 
(35 intermediate revisions by the same user not shown)
Line 61: Line 61:
 
  $ sudo sh -c "echo "JAVA_HOME=/usr/lib/jvm/jdk1.6.0_45" >> /etc/environment"
 
  $ sudo sh -c "echo "JAVA_HOME=/usr/lib/jvm/jdk1.6.0_45" >> /etc/environment"
  
==<span style="color:#0070c0;">Conventions</span>==
+
==<span style="color:#0070c0;">Introducing BSP</span>==
<span style="color:purple">'''${PREBUILT_IMAGE}'''</span> : compressed prebuilt image (*.img.gz)
+
:The BSP contains cross toolchain, linux kernel source code, u-boot source code, Android root file system and some scripts. It is consist of three top folders: "android", "image", "scripts".
  
<span style="color:purple">'''${BSP_TARBALL}'''</span> : BSP tarball (*.tgz)
+
===<span style="color:#0070c0;">Overview</span>===
 +
:The description of some important folders as below:
 +
::'''android/'''
 +
:::'''prebuilt/gcc/linux-x86/host/''' : cross toolchain
 +
:::'''bootable/bootloader/uboot-imx/''' : u-boot source code
 +
:::'''kernel_imx/''' : linux kernel source code
 +
:::'''device/'''
 +
::::'''fsl/''' : Android device related settings
 +
::::'''fsl-proprietary/''' : modules & firmware(e.g. WiFi, GPU)
 +
:::'''hardware/imx/''' : HAL (Hardware Abstraction Layer)
 +
::'''image/''' : all built images located in
 +
::'''scripts/''' : to simplify building process (Please refer to [[#Build_Instructions|1.4]] & [[#Boot_up_from_SD_card_or_eMMC|1.5]] for details)
  
<span style="color:purple">'''${BSP_HOME}'''</span> : home directory of the BSP
+
===<span style="color:#0070c0;">Naming Rule</span>===
 +
:It is consist of the model name followed by "AB" plus version number, for example, 4410ABV2080 which "4410" stands for RSB-4410, "AB" is acronym of Android BSP, "V2080" stands for Version 2.080; other model names list below:
 +
::"3420" stands for ROM-3420
 +
::"5420" stands for ROM-5420
 +
::"7420" stands for ROM-7420
 +
::"DS31" stands for UBC-DS31
 +
::"U220" stands for UBC-220
  
<span style="color:purple">'''${BDIR}'''</span> : build directory (e.g. build-x11)
+
==<span style="color:#0070c0;">Conventions</span>==
 +
<span style="color:purple">'''${BOARD}'''</span> : target board name (list below)
 +
:rsb_4410 / rom_3420 / rom_5420 / rom_7420 / ubc_ds31 / ubc_200
  
<span style="color:purple">'''${MX6PROC}'''</span> : i.MX6 Processor
+
<span style="color:purple">'''${BSPHOME}'''</span> : the directory that BSP tarball extacted to
:mx6q for iMX6 Quad Core / Dual Core
 
:mx6dl for iMX6 Dual Lite / Solo
 
 
 
<span style="color:purple">'''${IMX6PROC}'''</span> : i.MX6 Processor
 
:imx6q / imx6dl
 
 
 
<span style="color:purple">'''${BOARD}'''</span> : available target boards list below
 
:rsb4410 / rom3420 / rom5420 / rom7420 / ubcds31 / ubc220
 
 
 
<span style="color:purple">'''${MC}'''</span> : machine code combined with <span style="color:purple">'''${IMX6PROC}${BOARD}${BOARD_REV}'''</span>
 
:for example,
 
<tt>
 
::imx6qrsb4410 for RSB-4410
 
::imx6qrom3420 for ROM-3420
 
::imx6qrom5420 for ROM-5420
 
::imx6qrom7420 for ROM-7420
 
::imx6qubcds31 for UBC-DS31
 
::imx6dlubc220 for UBC-220
 
</tt>
 
  
 
<span style="color:purple">'''${SD_DEVICE}'''</span> : device name of SD card in Ubuntu (e.g. /dev/sdf)
 
<span style="color:purple">'''${SD_DEVICE}'''</span> : device name of SD card in Ubuntu (e.g. /dev/sdf)
  
<span style="color:purple">'''${SDCARD_IMAGE}'''</span> : sdcard image built by bitbake (*.sdcard)
+
<span style="color:purple">'''${MMC_DEVICE}'''</span> : device name of on-board eMMC in Android (e.g. /dev/block/mmcblk0)
 
 
<span style="color:purple">'''${UBOOT}'''</span> :u-boot version(e.g. 2013.04-r0)
 
 
 
<span style="color:purple">'''${KERNEL}'''</span> : linux kernel version(e.g. 3.14.28-r0)
 
 
 
<span style="color:purple">'''${POKY}'''</span> : Yocto poky version(e.g. 1.5.3)
 
  
 
debug console / serial console
 
debug console / serial console
Line 107: Line 101:
 
:terminal program (e.g. gnome-terminal, xfce4-terminal ...)
 
:terminal program (e.g. gnome-terminal, xfce4-terminal ...)
  
==<span style="color:#0070c0;">Introducing BSP</span>==
+
==<span style="color:#0070c0;">Build Instructions</span>==
:The BSP is based on Yocto Project with Freescale enhanced features for i.MX6, plus specific target board features from Advantech Inc..
+
===<span style="color:#0070c0;">To build everything</span>===
 +
:Perform one of the following commands in terminal console
 +
:* engineer version (default option)
 +
::<code>$ cd <span style="color:#7030a0;">'''${BSPHOME}'''</span>/scripts</code>
 +
::<code>$ ./mk_android.sh <span style="color:#7030a0;">'''${BOARD}'''</span></code>
 +
:* user version
 +
::<code>$ cd <span style="color:#7030a0;">'''${BSPHOME}'''</span>/scripts</code>
 +
::<code>$ ./mk_android.sh <span style="color:#7030a0;">'''${BOARD}''' user</span></code>
  
===<span style="color:#0070c0;">Naming Rule</span>===
+
===<span style="color:#0070c0;">To build boot loader</span>===
:The tarball/prebuilt image name is consist of the model name followed by "LB" or "LI" plus version number and released date.
+
:Perform the following command in terminal console
 +
::<code>$ cd <span style="color:#7030a0;">'''${BSPHOME}'''</span>/scripts</code>
 +
::<code>$ ./mk_bootloader.sh <span style="color:#7030a0;">'''${BOARD}'''</span></code>
  
:For example, 4410LBV3240_2015-03-25.tgz which "4410" stands for RSB-<span style="color:#ff0000;">'''4410'''</span>, "LB" is acronym of <span style="color:#ff0000;">'''L'''</span>inux <span style="color:#ff0000;">'''B'''</span>SP, "V3240" stands for <span style="color:#ff0000;">'''V'''</span>ersion <span style="color:#ff0000;">'''3'''</span>.<span style="color:#ff0000;">'''240'''</span><nowiki>.</nowiki>
+
===<span style="color:#0070c0;">To build boot image</span>===
:For example, 4410LIV3240_DualQuad_2015-03-25.img.gz which "LI" is acronym for prebuilt <span style="color:#ff0000;">'''L'''</span>inux <span style="color:#ff0000;">'''I'''</span>mage, DualQuad means this image is fit for Dual Core/Quad Core.
+
:Perform the following command in terminal console
 +
::<code>$ cd <span style="color:#7030a0;">'''${BSPHOME}'''</span>/scripts</code>
 +
::<code>$ ./mk_bootimg.sh <span style="color:#7030a0;">'''${BOARD}'''</span></code>
  
===<span style="color:#0070c0;">BSP tarball</span>===
+
===<span style="color:#0070c0;">To build recovery image</span>===
:Unpack BSP tarball to home directory by performing the following command:
+
:Perform the following command in terminal console
::<code>$ tar xvf <span style="color:#7030a0;">'''${BSP</span><span style="color:#7030a0;">_TARBALL</span><span style="color:#7030a0;">}'''</span> -C ~/</code>
+
::<code>$ cd <span style="color:#7030a0;">'''${BSPHOME}'''</span>/scripts</code>
:::(Every BSP with different version contains an unique folder, e.g. after unpacking 4410LBV3240_2015-03-25.tg to home directory, the directory , ~/imx6LBV3240_2015-03-25 is the BSP's home folder.)
+
::<code>$ ./mk_recoveryimg.sh <span style="color:#7030a0;">'''${BOARD}'''</span></code>
:The description of some important folders list below:
 
::'''sources/'''
 
:::'''meta-advantech/''' : meta layer by Advantech
 
:::'''meta-fsl-*/''' : meta layer by Freescale
 
::'''fsl-setup-release.sh''' : to create one new build environment
 
::'''setup-environment''' : to continue an exist build environment
 
  
===<span style="color:#0070c0;">Prebuilt image</span>===
+
===<span style="color:#0070c0;">To build system image</span>===
:Perform the following command to build one boot-up SD card
+
:Perform the following command in terminal console
::<code>$ gunzip -c <span style="color:#7030a0;">'''${</span><span style="color:#7030a0;">PREBUILT_IMAGE</span><span style="color:#7030a0;">}'''</span> | dd of=<span style="color:#7030a0;">'''${SD_DEVICE}'''</span> bs=1M</code>
+
::<code>$ cd <span style="color:#7030a0;">'''${BSPHOME}'''</span>/scripts</code>
 +
::<code>$ ./mk_systemimg.sh <span style="color:#7030a0;">'''${BOARD}'''</span></code>
  
==<span style="color:#0070c0;">Build Instructions</span>==
+
===<span style="color:#0070c0;">To build OTA image</span>===
===<span style="color:#0070c0;">To create one new build environment</span>===
+
:Perform the following command in terminal console
:Perform the following commands in terminal console
+
::<code>$ cd <span style="color:purple">'''${BSPHOME}'''</span>/scripts</code>
::<code>$ cd <span style="color:#7030a0;">'''${BSP_HOME}'''</span></code>
+
::<code>$ ./mk_otapackage.sh <span style="color:purple">'''${BOARD}'''</span></code>
::<code>$ MACHINE=<span style="color:#7030a0;">'''${MC}'''</span> source fsl-setup-release.sh -b <span style="color:#7030a0;">'''${BDIR}'''</span> -e x11</code>
+
:and the OTA package, update.zip, is located in the following directory
:You need to read and accept the EULA.
+
::../android/out/target/product/<span style="color:purple">'''${BOARD}'''</span>.
:[[Image:accept_EULA.png]]
 
  
===<span style="color:#0070c0;">To continue an exist build environment</span>===
+
==<span style="color:#0070c0;">Boot up from SD card or eMMC</span>==
:Perform the following commands in terminal console
 
::<code>$ cd <span style="color:#7030a0;">'''${BSP_HOME}'''</span></code>
 
::<code>$ source setup-environment <span style="color:#7030a0;">'''${BDIR}'''</span></code>
 
  
===<span style="color:#0070c0;">To build sdcard image for Qt 4.8.5 used</span>===
+
===<span style="color:#0070c0;"> To create a bootable SD card</span>===
:To create/continue a build environment
 
 
:Perform the following command in terminal console
 
:Perform the following command in terminal console
::<code>$ bitbake fsl-image-x11</code>
+
::<code>$ cd '''<span style="color:#7030a0;">${BSPHOME}</span>'''/scripts</code>
:The file, fsl-image-x11-<span style="color:#7030a0;">'''${MC}'''</span>.sdcard, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0;">'''${MC}'''</span>, while building process finished successfully.
+
::<code>$ ./mksd-android.sh <span style="color:purple;">'''${SD_DEVICE}'''</span></code>
  
===<span style="color:#0070c0;">To build sdcard image for Qt 5.2.1 used</span>===
+
===<span style="color:#0070c0;">To transfer whole system to onboard eMMC</span>===
:To create/continue a build environment
+
:Boot up from SD card
:Perform the following command in terminal console
+
:Perform the following commands in debug console
::<code>$ bitbake fsl-image-x11-qt5</code>
+
::<code># cd /data/mkimage/scripts</code>
:The file, fsl-image-x11-qt5-<span style="color:#7030a0;">'''${MC}'''</span>.sdcard, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0;">'''${MC}'''</span>, while building process finished successfully.
+
::<code># sh ./mksd-android.sh <span style="color:purple;">'''${MMC_DEVICE}'''</span></code>
 +
:Remove SD card, then target board can boot up from onboard eMMC.
 +
 
 +
=Software Functionality=
 +
==<span style="color:#0070c0;">Serial Port Test</span>==
 +
===<span style="color:#0070c0;">Serial Port Setup</span>===
 +
#Click "Serial Port"
 +
#:[[File:imx6ABV1_APP_serialport.png|800px]]
 +
#Click "Setup"
 +
#:[[File:imx6ABV1_serialport_setup.png|800px]]
 +
#Click "Device" , and choose the used device(e.g. ttymxc1)
 +
#:[[File:imx6ABV1_serialport_setup_device_1.png]]
 +
#Click "Baud rate" , and choose the used baudrate(e.g. 115200)
 +
#:[[File:imx6ABV1_serialport_setup_device_2.png]]
 +
 
 +
===<span style="color:#0070c0;">Console Test</span>===
 +
#Open one serial console.
 +
#Click "Console"
 +
#:[[File:imx6ABV1_console.png|800px]]
 +
#:Typing some characters (e.g. "This is a test. 123456789ABCDEF") then pressing Enter in serial console, the identical message will shows up in reception block as below:
 +
#:[[File:imx6ABV1_console_serialport.png]]
 +
#:On the other hand, typing some message (ex. "MESSAGE from Android") in emission block, the identical message will shows up in serial console as below:
 +
#:[[File:imx6ABV1_console_message_from.png]]
  
===<span style="color:#0070c0;">To build sdcard image without Qt</span>===
+
===<span style="color:#0070c0;">Loopback Test</span>===
:To create/continue a build environment
+
#Plug loopback device into COM2
:Perform the following command in terminal console
+
#Click "Loopback"
::<code>$ bitbake fsl-image-fb</code>
+
#:The loopback test result will show up as below
:The file, fsl-image-fb-<span style="color:#7030a0;">'''${MC}'''</span>.sdcard, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0;">'''${MC}'''</span>, while building process finished successfully.
+
#:[[File:imx6ABV1_loopback.png|800px]]
  
===<span style="color:#0070c0;">To build toolchain installer for Qt 4.8.5 used</span>===
+
===<span style="color:#0070c0;">Send01010101 Test</span>===
:To create/continue a build environment
+
#Open one serial console.
:Perform the following command in terminal console
+
#Click Send01010101 .
::<code>$ bitbake fsl-image-x11 -c populate_sdk</code>
+
#:The character "U" (b'01010101) will show up continuously as below:
:The installer, poky-eglibc-x86_64-fsl-image-x11-cortexa9hf-vfp-neon-toolchain-qt4-<span style="color:#7030a0;">'''${POKY}'''</span>.sh, will be located in the directory "./tmp/deploy/sdk".</code>
+
#:[[File:imx6ABV1_send01010101.png]]
  
===<span style="color:#0070c0;">To build toolchain installer for Qt 5.2.1 used</span>===
+
==<span style="color:#0070c0;">Display Output Option</span>==
:To create/continue a build environment
 
:Perform the following command in terminal console
 
::<code>$ bitbake fsl-image-x11-qt5 -c populate_sdk</code>
 
:The installer, poky-eglibc-x86_64-fsl-image-x11-qt5-cortexa9hf-vfp-neon-toolchain-<span style="color:#7030a0;">'''${POKY}'''</span>.sh, will be located in the directory "./tmp/deploy/sdk".</code>
 
  
===<span style="color:#0070c0;">To build toolchain installer without Qt</span>===
+
===<span style="color:#0070c0;">Single HDMI Display</span>===
:To create/continue a build environment
+
:Perform the following command in u-boot:
:Perform the following command in terminal console
+
::<code>> setenv bootargs 'console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M androidboot.hardware=freescale'</code>
::<code>$ bitbake fsl-image-fb -c populate_sdk</code>
+
::<code>> saveenv </code>
:The installer, poky-eglibc-x86_64-fsl-image-fb-cortexa9hf-vfp-neon-toolchain-<span style="color:#7030a0;">'''${POKY}'''</span>.sh, will be located in the directory "./tmp/deploy/sdk".</code>
+
::<code>> reset </code>
  
===<span style="color:#0070c0;">To build u-boot</span>===
+
===<span style="color:#0070c0;">Single VGA Display</span>===
:To create/continue a build environment
+
:Perform the following command in u-boot:
:Perform the following command in terminal console
+
::<code>> setenv bootargs 'console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=lcd,1920x1080M@60,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M androidboot.hardware=freescale'</code>
::<code>$ bitbake u-boot-imx</code>
+
::<code>> saveenv </code>
:The two files, u-boot_crc.bin & u-boot_crc.bin.crc, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0;">'''${MC}'''</span>.
+
::<code>> reset </code>
  
===<span style="color:#0070c0;">To build linux kernel</span>===
+
===<span style="color:#0070c0;">Single LVDS Display</span>===
:To create/continue a build environment
+
:Perform the following command in u-boot:
:Perform the following command in terminal console
+
::<code>> setenv bootargs 'console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=ldb,1024x768M@60,bpp=24 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M androidboot.hardware=freescale'</code>
::to show up menuconfig
+
::<code>> saveenv </code>
:::<code>$ bitbake linux-imx -c menuconfig</code>
+
::<code>> reset </code>
::to do build
 
:::<code>$ bitbake linux-imx</code>
 
:The two files, uImage & uImage-<span style="color:#7030a0;">'''${IMX6PROC}'''</span>-<span style="color:#7030a0;">'''${BOARD}'''</span>.dtb, will be located in directory, ./tmp/deploy/images/<span style="color:#7030a0;">'''${MC}'''</span>.
 
  
==<span style="color:#0070c0;">Creating boot-up on-board flash from prebuilt image</span>==
+
===<span style="color:#0070c0;">Dual Display</span>===
 +
:For example of HDMI & VGA, Perform the following command in u-boot:
 +
::<code>> setenv bootargs 'console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb1:dev=lcd,1920x1080M@60,bpp=32 video=mxcfb2:off video=mxcfb3:off fbmem=28M,28M androidboot.hardware=freescale'</code>
 +
::<code>> saveenv </code>
 +
::<code>> reset </code>
  
===<span style="color:#0070c0;">To create one boot-up SD card</span>===
+
==<span style="color:#0070c0;">Network Setup==
:Perform the following command in terminal console
+
===<span style="color:#0070c0;">Wi-Fi</span>===
::<code>$ gunzip -c '''<span style="color:#7030a0;">${PREBUILT_IMAGE</span>''' | dd of=<span style="color:#7030a0;">'''${SD_DEVICE}'''</span> bs=1M</code>
+
#Click "Settings"
 +
#:[[File:imx6ABV1_APP_settings.png|800px]]
 +
#Turn Wi-Fi on
 +
#:[[File:imx6ABV1_settings_wifi_on.png|800px]]
 +
#Choose ESSID (e.g. ESSD Testing )
 +
#:[[File:imx6ABV1_settings_wifi_choose_ESSID.png|800px]]
 +
#Input correct password
 +
#:[[File:imx6ABV1_settings_wifi_password.png]]
 +
#Wi-Fi Authenticating/Connecting/Obtaining IP address
 +
#:[[File:imx6ABV1_settings_wifi_authenticating.png|800px]]
 +
#:[[File:imx6ABV1_settings_wifi_connecting.png|800px]]
 +
#:[[File:imx6ABV1_settings_wifi_obtaining_ip.png|800px]]
 +
#Wi-Fi connected
 +
#:[[File:imx6ABV1_settings_wifi_connected.png|800px]]
  
===<span style="color:#0070c0;">To transfer whole system to on-board flash</span>===
+
===<span style="color:#0070c0;">Ethernet</span>===
:Boot up from SD card
+
#Click "Settings" / "Ethernet configuration" , then Turn on Ethernet
:Perform the following commands in debug console
+
#:[[File:imx6ABV1_settings_ethernet_config.png|800px]]
::<code># cd /mk_inand</code>
+
#Click "Ethernet configuration"
::<code># ./mksd-linux.sh /dev/mmcblk0</code>
+
#:[[File:imx6ABV1_settings_ethernet_config_next_level.png|800px]]
:press y followed by Enter, if following message shows up:
+
#Choose Connection Type (DHCP or Static IP)
::[[File:all_data_will_be_destroyed.png]]
+
#:[[File:imx6ABV1_settings_ethernet_config_dhcp.png||400px]][[File:imx6ABV1_settings_ethernet_config_static.png|400px]]
:While "[Done]" shows up means the transferring is finished.
 
  
==<span style="color:#0070c0;">Creating boot-up on-board flash from built sdcard image</span>==
+
==<span style="color:#0070c0;">To update system==
===<span style="color:#0070c0;">To create one boot-up SD card</span>===
+
#Refer to 1.4.6 to build OTA package.
:Perform the following commands in terminal console
+
#Plug SD card that contains OTA package(update.zip) into SD slot.
::<code>$ pushd <span style="color:#7030a0;">'''${BSP_HOME}'''</span>/<span style="color:#7030a0;">'''${BDIR}'''</span>/tmp/deploy/images/<span style="color:#7030a0;">'''${MC}'''</span></code>
+
#Click "Settings" / "About tablet" / "Addition system updates" :
::<code>$ dd if=<span style="color:#7030a0;">'''${SDCARD_IMAGE}'''</span> of=<span style="color:#7030a0;">'''${SD_DEVICE}'''</span> bs=1M</code>
+
#:[[File:imx6ABV1_settings_addition_system_updates.png|800px]]
::<code>$ popd</code>
+
#Wait for one moment, system will reboot for updating
 +
#:[[File:imx6ABV1_poweroff.png|800px]]
 +
#It will take some time to update.
  
===<span style="color:#0070c0;">To transfer whole system to on-board flash</span>===
+
=System Recovery=
:Boot up from SD card
+
Please refer to [[#To_create_a_bootable_SD_card|1.5.1]] & [[#To_transfer_whole_system_to_onboard_eMMC|1.5.2]] to create a bootable SD card and transfer whole system to on-board eMMC.
:Insert USB stick that contains <span style="color:#7030a0;">'''${SDCARD_IMAGE}'''</span>, USB stick will be auto mounted to /media/sda1.
 
:Perform the following commands in debug console
 
::<code># umount /media/mmcblk0p?</code>
 
::<code># cd /media/sda1</code>
 
::<code># dd if=<span style="color:#7030a0;">'''${SDCARD_IMAGE}'''</span> of=/dev/mmcblk0 bs=4M conv=fsync</code>
 
::<code># P2START=$(fdisk -lu | grep mmcblk0p2 | awk '{print $2}')</code>
 
::<code># echo -e "d\n2\nn\np\n2\n<span style="color:#7030a0;">'''${P2START}'''</span>\n\nw\n" | fdisk -u /dev/mmcblk0</code>
 
::<code># umount /media/mmcblk0p2</code>
 
::<code># e2fsck -f -y /dev/mmcblk0p2</code>
 
::<code># resize2fs /dev/mmcblk0p2</code>
 
::<code># poweroff</code>
 

Latest revision as of 04:04, 29 September 2016

Android BSP User Guide for iMX6 series

Getting Started

Prerequisites

All operations in this guide are based on Ubuntu 12.04 LTS 64bit only.
First please install Ubuntu 12.04 LTS 64bit* with minimum 2GB memory.
* ubuntu-12.04.1-desktop-amd64.iso

To install required packages

Please login and perform the following commands:

$ sudo apt-get install ssh
$ sudo apt-get install ia32-libs libx11-dev:i386 libreadline6-dev:i386 \
libgl1-mesa-glx:i386 zlib1g-dev:i386 uuid-dev:i386 liblzo2-dev:i386 \ 
libncurses5-dev:i386
$ sudo apt-get install \
bison build-essential ccache dpkg flex gcc g++ gettext intltool \
libarchive-zip-perl libfreetype6-dev libdbus-glib-1-dev liborbit2-dev \
libxml2-dev libx11-dev libgtk2.0-dev liblzo2-2 libtool m4 \
patch rpm tcl uboot-mkimage uuid zlib1g zlib1g-dev \
git gnupg flex bison gperf build-essential  zip \
curl libc6-dev libncurses5-dev 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 \
gcc-4.6 g++-4.6 cpp-4.6 gcc-4.6-multilib uuid-dev liblzo2-dev \
uboot-mkimage libarchive-zip-perl \
wget git-core unzip texinfo gawk diffstat build-essential chrpath \
sed cvs subversion coreutils texi2html \
docbook-utils python-pysqlite2 help2man make gcc g++ \
desktop-file-utils libgl1-mesa-dev libglu1-mesa-dev mercurial \
autoconf automake groff curl lzop asciidoc xterm
$ sudo apt-get install libncurses5-dev:i386 liblzo2-dev:i386 uuid-dev:i386
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
$ tar zcvf ~/usr_lib_i386-linux-gnu_for_Building_Android_KK.tar.gz \
/usr/lib/i386-linux-gnu/{libuuid.a,libuuid.so,liblzo2.so,liblzo2.a}
$ sudo apt-get install uuid-dev liblzo2-dev
$ sudo tar zxvf ~/usr_lib_i386-linux-gnu_for_Building_Android_KK.tar.gz -C /

To install JDK

Please download "jdk-6u45-linux-x64.bin" manually, put it to directory ~/FILES/ and perform the following commands:

$ cd /usr/lib
$ sudo ~/FILES/jdk-6u45-linux-x64.bin
$ sudo mkdir jvm
$ cd jvm
$ sudo mv ../jdk1.6.0_45 .
$ cd jdk1.6.0_45/
$ sudo update-alternatives --install /usr/bin/java    java    /usr/lib/jvm/jdk1.6.0_45/jre/bin/java    2
$ sudo update-alternatives --install /usr/bin/javac   javac   /usr/lib/jvm/jdk1.6.0_45/bin/javac   2
$ sudo update-alternatives --install /usr/bin/jar     jar     /usr/lib/jvm/jdk1.6.0_45/bin/jar     2
$ sudo update-alternatives --install /usr/bin/javap   javap   /usr/lib/jvm/jdk1.6.0_45/bin/javap   2
$ sudo update-alternatives --install /usr/bin/javadoc javadoc /usr/lib/jvm/jdk1.6.0_45/bin/javadoc 2
$ sudo update-alternatives --config javap
$ sudo update-alternatives --config javadoc
$ sudo update-alternatives --config java
$ sudo update-alternatives --config javac
$ sudo update-alternatives --config jar
$ cd ~/
$ sudo sh -c "echo "JAVA_HOME=/usr/lib/jvm/jdk1.6.0_45" >> /etc/environment"

Introducing BSP

The BSP contains cross toolchain, linux kernel source code, u-boot source code, Android root file system and some scripts. It is consist of three top folders: "android", "image", "scripts".

Overview

The description of some important folders as below:
android/
prebuilt/gcc/linux-x86/host/ : cross toolchain
bootable/bootloader/uboot-imx/ : u-boot source code
kernel_imx/ : linux kernel source code
device/
fsl/ : Android device related settings
fsl-proprietary/ : modules & firmware(e.g. WiFi, GPU)
hardware/imx/ : HAL (Hardware Abstraction Layer)
image/ : all built images located in
scripts/ : to simplify building process (Please refer to 1.4 & 1.5 for details)

Naming Rule

It is consist of the model name followed by "AB" plus version number, for example, 4410ABV2080 which "4410" stands for RSB-4410, "AB" is acronym of Android BSP, "V2080" stands for Version 2.080; other model names list below:
"3420" stands for ROM-3420
"5420" stands for ROM-5420
"7420" stands for ROM-7420
"DS31" stands for UBC-DS31
"U220" stands for UBC-220

Conventions

${BOARD} : target board name (list below)

rsb_4410 / rom_3420 / rom_5420 / rom_7420 / ubc_ds31 / ubc_200

${BSPHOME} : the directory that BSP tarball extacted to

${SD_DEVICE} : device name of SD card in Ubuntu (e.g. /dev/sdf)

${MMC_DEVICE} : device name of on-board eMMC in Android (e.g. /dev/block/mmcblk0)

debug console / serial console

serial terminal program (e.g. minicom, putty, teraterm ...) that serial port is configured to 115200 8N1

terminal console

terminal program (e.g. gnome-terminal, xfce4-terminal ...)

Build Instructions

To build everything

Perform one of the following commands in terminal console
  • engineer version (default option)
$ cd ${BSPHOME}/scripts
$ ./mk_android.sh ${BOARD}
  • user version
$ cd ${BSPHOME}/scripts
$ ./mk_android.sh ${BOARD} user

To build boot loader

Perform the following command in terminal console
$ cd ${BSPHOME}/scripts
$ ./mk_bootloader.sh ${BOARD}

To build boot image

Perform the following command in terminal console
$ cd ${BSPHOME}/scripts
$ ./mk_bootimg.sh ${BOARD}

To build recovery image

Perform the following command in terminal console
$ cd ${BSPHOME}/scripts
$ ./mk_recoveryimg.sh ${BOARD}

To build system image

Perform the following command in terminal console
$ cd ${BSPHOME}/scripts
$ ./mk_systemimg.sh ${BOARD}

To build OTA image

Perform the following command in terminal console
$ cd ${BSPHOME}/scripts
$ ./mk_otapackage.sh ${BOARD}
and the OTA package, update.zip, is located in the following directory
../android/out/target/product/${BOARD}.

Boot up from SD card or eMMC

To create a bootable SD card

Perform the following command in terminal console
$ cd ${BSPHOME}/scripts
$ ./mksd-android.sh ${SD_DEVICE}

To transfer whole system to onboard eMMC

Boot up from SD card
Perform the following commands in debug console
# cd /data/mkimage/scripts
# sh ./mksd-android.sh ${MMC_DEVICE}
Remove SD card, then target board can boot up from onboard eMMC.

Software Functionality

Serial Port Test

Serial Port Setup

  1. Click "Serial Port"
    Imx6ABV1 APP serialport.png
  2. Click "Setup"
    Imx6ABV1 serialport setup.png
  3. Click "Device" , and choose the used device(e.g. ttymxc1)
    Imx6ABV1 serialport setup device 1.png
  4. Click "Baud rate" , and choose the used baudrate(e.g. 115200)
    Imx6ABV1 serialport setup device 2.png

Console Test

  1. Open one serial console.
  2. Click "Console"
    Imx6ABV1 console.png
    Typing some characters (e.g. "This is a test. 123456789ABCDEF") then pressing Enter in serial console, the identical message will shows up in reception block as below:
    Imx6ABV1 console serialport.png
    On the other hand, typing some message (ex. "MESSAGE from Android") in emission block, the identical message will shows up in serial console as below:
    Imx6ABV1 console message from.png

Loopback Test

  1. Plug loopback device into COM2
  2. Click "Loopback"
    The loopback test result will show up as below
    Imx6ABV1 loopback.png

Send01010101 Test

  1. Open one serial console.
  2. Click Send01010101 .
    The character "U" (b'01010101) will show up continuously as below:
    Imx6ABV1 send01010101.png

Display Output Option

Single HDMI Display

Perform the following command in u-boot:
> setenv bootargs 'console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M androidboot.hardware=freescale'
> saveenv
> reset

Single VGA Display

Perform the following command in u-boot:
> setenv bootargs 'console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=lcd,1920x1080M@60,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M androidboot.hardware=freescale'
> saveenv
> reset

Single LVDS Display

Perform the following command in u-boot:
> setenv bootargs 'console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=ldb,1024x768M@60,bpp=24 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M androidboot.hardware=freescale'
> saveenv
> reset

Dual Display

For example of HDMI & VGA, Perform the following command in u-boot:
> setenv bootargs 'console=ttymxc0,115200 androidboot.console=ttymxc0 vmalloc=400M init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb1:dev=lcd,1920x1080M@60,bpp=32 video=mxcfb2:off video=mxcfb3:off fbmem=28M,28M androidboot.hardware=freescale'
> saveenv
> reset

Network Setup

Wi-Fi

  1. Click "Settings"
    Imx6ABV1 APP settings.png
  2. Turn Wi-Fi on
    Imx6ABV1 settings wifi on.png
  3. Choose ESSID (e.g. ESSD Testing )
    Imx6ABV1 settings wifi choose ESSID.png
  4. Input correct password
    Imx6ABV1 settings wifi password.png
  5. Wi-Fi Authenticating/Connecting/Obtaining IP address
    Imx6ABV1 settings wifi authenticating.png
    Imx6ABV1 settings wifi connecting.png
    Imx6ABV1 settings wifi obtaining ip.png
  6. Wi-Fi connected
    Imx6ABV1 settings wifi connected.png

Ethernet

  1. Click "Settings" / "Ethernet configuration" , then Turn on Ethernet
    Imx6ABV1 settings ethernet config.png
  2. Click "Ethernet configuration"
    Imx6ABV1 settings ethernet config next level.png
  3. Choose Connection Type (DHCP or Static IP)
    Imx6ABV1 settings ethernet config dhcp.pngImx6ABV1 settings ethernet config static.png

To update system

  1. Refer to 1.4.6 to build OTA package.
  2. Plug SD card that contains OTA package(update.zip) into SD slot.
  3. Click "Settings" / "About tablet" / "Addition system updates" :
    Imx6ABV1 settings addition system updates.png
  4. Wait for one moment, system will reboot for updating
    Imx6ABV1 poweroff.png
  5. It will take some time to update.

System Recovery

Please refer to 1.5.1 & 1.5.2 to create a bootable SD card and transfer whole system to on-board eMMC.