i.MX Android R10 User Guide

    3.1 Board Dip Switch Setting

        3.1.1 USB serial download settings

        3.1.2 Boot up settings

    3.2 System on MMC/SD and eMMC

        3.2.1 Storage Partitions

        3.2.2 Download with MFG Tool

        3.2.3 Download with dd utility 
        3.2.4 Download with fastboot

        3.2.6 Boot from MMC/SD and eMMC

    3.3 System on NFS

        3.3.1 Setup the NFS root

        3.3.2 Boot from TFTP and NFS

    3.4 Boot up configurations

4. Run
    4.1 Multimedia
        4.1.1 Music Play
        4.1.2 Video Play
        4.1.3 Streaming Play
        4.1.4 Camera
        4.1.5 Sound Recording
        4.1.6 Camcorder
        4.1.7 Usb Video Camera
    4.2 Storage
        4.2.1 Usb Mass Storage
        4.2.2 Multi-Storage
    4.3 Connection
        4.3.1 Wifi
        4.3.2 3G Modem
        4.3.3 Enable AR6003/AR6102 Wifi Card
    4.4 Display
        4.4.1 TVout with Video Only
        4.4.2 TVout with Video and UI
        4.4.3 Dual-Display
        4.4.4 Support 24bpp Pixel Format
    4.5 Applications & Development
        4.5.1 Key Maps
        4.5.2 Volume
        4.5.3 Brightness
        4.5.4 Screen Timeout
        4.5.5 ADB
        4.5.6 App to SD
        4.5.7 Recovery
        4.5.8 3D Demo
        4.5.9 Fastboot
        4.5.10 2G/2G

5. FAQ
    5.1 Why did the code fail to download from Google when repo init?
    5.2 Why I can't access the internet with browser using ethernet?
    5.3 Can I access Android shell using ethernet instead of a serial port?
    5.4 How do I change Android boot logo?
    5.5 How to use wake_lock to control specific devices? 

1. Setup

1.1 PC Setup

To build the Android source files, you will need to use Linux PC. It's suggested that you use the most recent version of Ubuntu which is the mostly tested OS for an Android build.
After installing Linux PC, you need check whether you have all necessary packages installed for an Android build. Refer to "Setting up your machine" on the Android web site http://source.android.com/source/download.html. 

    $ cd /opt (or any other directory you like)

    $ tar xzvf imx-android-r10.tar.gz

    $ cd imx-android-r10/code

    $ tar xzvf r10.tar.gz

i.MX51 BBG board (i.MX53 SMD  board have the same directory structure)

System images for MMC/SD and eMMC

• bootloader: imx51_BBG/u-boot-no-padding.bin or imx51_BBG/u-boot.bin (with padding)
• kernel: imx51_BBG/uImage
• Android file system:
• Initramfs:  imx51_BBG/SD/uramdisk.img
• System root:  imx51_BBG/SD/system.img
• Data: imx51_BBG/SD/userdata.img. Not provided as it's empty.
• 
  

System images for TFTP/NFS

Assume you had unzipped i.MX Android release package to /opt/imx-android-r10/.     $ cd ~     $ mkdir myandroid     $ cd myandroid     $ curl http://android.git.kernel.org/repo > ./repo     $ chmod a+x ./repo     $ ./repo init -u git://android.git.kernel.org/platform/manifest.git -b gingerbread     $ cp /opt/imx-android-r10/code/r10/default.xml .repo/manifests/default.xml  (To avoid loading unnecessary gits from Google repo, meanwhile load some gits from Google repo which is not included in default manifest)     $ ./repo sync

Get a clean kernel source code from kernel.org, and checkout the tag of 2.6.35.3: 

    $ cd myandroid

    $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.35.y.git kernel_imx

    $ cd kernel_imx

    $ git checkout v2.6.35.3

If you use uboot as your bootloader, then you need get a clean source code base from the original git:

$ cd myandroid/bootable/bootloader     $ git clone git://git.denx.de/u-boot.git uboot-imx

2.2 Patch Code for i.MX 

Apply all i.MX Android patches using following steps:

Assume you had unzipped i.MX Android release package to /opt/imx-android-r10/.     $ cd ~/myandroid     $ . /opt/imx-android-r10/code/r10/and_patch.sh     $ help     Now you should see "c_patch" function is available for you       $ c_patch /opt/imx-android-r10/code/r10 imx_r10       Here "/opt/imx-android-r10/code/r10" is the location of the patches (i.e. directory created when you unzip release package)     "imx_r10" is the branch which will be created automatically for you to hold all patches (only in those existing Google gits).     You can choose any branch name you like instead of "imx_r10".         If everything is OK, "c_patch" will generate the following output to indicate successful patch:     **************************************************************     Success: Now you can build android code for FSL i.MX platform     **************************************************************

Note: The patch script (and_patch.sh) utalizes some basic utilities like awk/sed. If they are not available on your LinuxPC, install them in advance.

To run Android using NFS or from SD, build the kernel with the default configuration now as follows:

With a successful build in either of the above case, the generated kernel image is ~/myandroid/kernel_imx/arch/arm/boot/uImage.

Generate uImage to be loaded by u-boot

After applying all i.MX patches, build the kernel and Android image using following steps:

    $ cd ~/myandroid

    $ export CROSS_COMPILE=~/myandroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- 

    Command to build for i.MX51 BBG3 board is:

    $ make PRODUCT-imx51_bbg-eng 2>&1 | tee build_imx51_bbg_android.log

    "imx51_BBG" is the product names (see ~/myandroid/device/fsl/product)

    Command to build for i.MX53 smd board is:    
    $ make PRODUCT-imx53_smd-eng 2>&1 | tee build_imx53_smd_android.log

    "imx53_smd" is the product names (see ~/myandroid/device/fsl/product)

    After build, check build_*_android.log to make sure no build error.

For i.MX51 BBG build, the following outputs are generated as default under myandroid/out/target/product/imx51_BBG: 
or 

For i.MX53 SMD build, the following outputs are generated as default under myandroid/out/target/product/imx53_smd :

root/ : root file system (including init, init.rc, etc). Mounted at /
system/:  Android system binary/libraries. Mounted at /system

data/: Android data area. Mounted at /data

Above three folders can be used to create your Android file system for NFS mounting, i.e. root/ > /, system/ > /system, data/ > /data

recovery/: root file system when booting in "recovery" mode. Not directly used.
ramdisk.img: Ramdisk image generated from "root/". Not directly used.
system.img: EXT4 image generated from "system/". Can be programmed to "SYSTEM" partition on SD card with "dd"
userdata.img: EXT4 image generated from "data/".
recovery.img: EXT4 image generated from "recovery/". Can be programmed to "RECOVERY" partition on SD card with "dd" 

Generate uRamdisk to be loaded by uboot

The following steps generate a RAMDISK image recognized by uboot:

Assume you had already built uboot. mkimage was generated under myandroid/bootable/bootloader/uboot-imx/tools/     $ cd myandroid/out/target/product/imx51_bbg     $ ~/myandroid/bootable/bootloader/uboot-imx/tools/mkimage -A arm -O linux -T ramdisk -C none -a 0x90308000 -n "Android Root Filesystem" -d ./ramdisk.img ./uramdisk.img or     $ cd myandroid/out/target/product/imx53_smd     $ ~/myandroid/bootable/bootloader/uboot-imx/tools/mkimage -A arm -O linux -T ramdisk -C none -a 0x70308000 -n "Android Root Filesystem" -d ./ramdisk.img ./uramdisk.img

3. Download images and Boot-up system

3.1 Board Dip Switch Setting

About the details dip switches, you can refer to "uboot_mx51.pdf", "i.MX53_EVK_Linux_BSP_UserGuide.pdf" and "Codex_CPU_Boot_Mode.xls"

3.1.1 USB serial download settings

i.mx51 BBG

Switch	S-1	S-2	S-3	S-4	S-5	S-6	S-7	S-8	S-9	S-10
S1	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF	ON

i.mx53 SMD

Switch	D1	D2	D3	D4	D5	D6	D7	D8
SW26	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF
SW28	OFF	OFF	ON	ON	OFF	OFF	OFF	OFF

i.mx50 RD

Switch	D1	D2	D3	D4	D5	D6	D7	D8
SW5	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF
SW4	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF
SW3	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF

3.1.2 Boot up settings

i.mx51 BBG MMC/SD Slot1 Boot

Switch	S-1	S-2	S-3	S-4	S-5	S-6	S-7	S-8	S-9	S-10
S1	OFF	OFF	OFF	OFF	OFF	OFF	ON	ON	OFF	OFF

i.mx53 SMD eMMC(SD slot3) Boot

Switch	D1	D2	D3	D4	D5	D6	D7	D8
SW26	OFF	ON	OFF	OFF	ON	ON	ON	OFF
SW28	OFF	OFF	OFF	OFF	OFF	OFF	OFF	ON

i.mx53 SMD MMC/SD (slot1) Boot

Switch	D1	D2	D3	D4	D5	D6	D7	D8
SW26	OFF	OFF	OFF	OFF	OFF	OFF	ON	OFF
SW28	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF

i.mx50 RD eSDHC1-SD-4bit; others boot mode, refer to "Codex_CPU_Boot_Mode.xls"

Switch	D1	D2	D3	D4	D5	D6	D7	D8
SW5	OFF	ON	OFF	OFF	ON	OFF	OFF	OFF
SW4	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF
SW3	OFF	OFF	OFF	OFF	OFF	OFF	OFF	OFF

3.2 System on MMC/SD and eMMC

Android support running on the MMC/SD card, or on board eMMC device.
We need images below to create an android system on MMC/SD or eMMC device:

• u-boot image: u-boot.bin or u-boot-no-padding.bin
• kernel image: uImage
• ramdisk image: uramdisk.img
• Android system root image: system.img
• Recovery root image: recovery.img

3.2.1 Storage Partitions

• [Partition type/index] is which defined in the MBR. 
• [Name] is only meaningful in android, you can ignore it when creating these partitions.
• [Start Offset] shows where partition is started, unit in MBytes.

Partition Type/Index	Name	Start Offset	Size	File System	Content
N/A	BOOT	0	10MB	N/A	bootloader/kernel/uramdisk images
Primary 1	MEDIA	11MB	User Defined	VFAT. Mount as /sdcards	Media file storage
Primary 2	SYSTEM	follow MEDIA	>= 200MB	EXT4. Mount as /system (with read only)	Android system bin/libs (system.img)
Logic 5 (Extended 3)	DATA	follow SYSTEM	> 200MB	EXT4. Mount as /data	Android data (e.g. installed app)
Logic 6 (Extended 3)	CACHE	follow DATA	> 10MB	EXT4. Mount as /cache	Android cache
Primary 4	RECOVERY	follow CACHE	> 20MB	EXT4. Mount as / in recovery mode	Root file system for recovery mode (recovery.img)

To create these partitions, you can simply use MFG tool described in next section, or use fdisk utility on Linux PC.

3.2.2 Download Images with MFG Tool

• Copy the MFG Tools from the release package "tools\" to your folder
• Untar the package and set the "dip switch"
  
• Use the android images replace the default images:

       Using the i.MX53 SMD as a example:
       Copy "u-boot.bin" "uImage" to  Profiles/MX53 Linux Updata/OS Firmware/files, and rename u-boot.bin to u-boot-mx53-smd.bin
       Copy "system.img", "recovery.img", "uramdisk.img" to  Profiles/MX53 Linux Updata/OS Firmware/files/android

• Open the MFGTool, plug in the usb cable and choose your profile

       Notes: found a new devices and install the driver  (the drivers\ directory)
                 select the profile: Option -> Configuration -> Profiles -> Options-> click the  cell (such as: MX53SMD-SD )

• Power on the board, you will see device connected

       Such as: “Freescale i.MX53 USB BuldIO Device”; please check the right port number and devices.
                    “Options->Configuration->USB Ports”

•  When all preparation done, press the "Start"

Notes: you can connect the serial port to check the download process.

Android profile in MFG tool uses the default mbr.bin to create partitions for the storage. This default mbr.bin is only for the images provided into the example. If the user replace with new flashed image, the user must update mbr.bin to create the right partition table. Another option is that the user modify ucl.xls to use fdisk instead of mbr.bin to create partitions. For fdisk usage, please refer to other profile to create the right fdisk-u.input.

3.2.3 Download Images with dd utility

The linux utility "dd" on Linux PC can be used to download the images into the MMC/SD card. Before download, make sure your MMC/SD card's partitions are created.

Download the uboot image:     # sudo dd if=u-boot.bin of=/dev/sdx bs=1K skip=1 seek=1; sync Or If you're using no padding uboot image:     # sudo dd if=u-boot-no-padding.bin of=/dev/sdx bs=1K seek=1; sync     Download the kernel image:     # sudo dd if=uImage of=/dev/sdx bs=1M seek=1; sync         Download the initramfs image:     # sudo dd if=uramdisk.img of=/dev/sdx bs=1M seek=6; sync     Download the android system root image:     # sudo dd if=system.img of=/dev/sdx2; sync        Download the android recovery image:     # sudo dd if=recovery.img of=/dev/sdx4; sync

3.2.4 Download Images with fastboot

The fastboot is a utility which can use to download images from Windows/Linux PC to the target storage device.




When a MMC/SD or eMMC device ready for Android system boot, then you can power on the board to setup the u-boot environment for loading kernel/ramdisk from device

3.3 System on NFS

Android support running the system on NFS root filesystem. We can put the total android root system into NFS, but loading kernel image from TFTP server.

U-Boot > setenv ethaddr 00:04:9f:00:ea:d3            [setup the MAC address] U-Boot > setenv fec_addr 00:04:9f:00:ea:d3           [setup the MAC address] U-Boot > setenv loadaddr <kernel load addr>          [0x90800000 for i.MX51, 0x70800000 for i.MX50/3]        U-Boot > setenv bootfile uImage U-Boot > setenv serverip <your server ip>            [Your TFTP/NFS server ip] U-Boot > setenv nfsroot <your rootfs>                [Your rootfs] U-Boot > setenv bootcmd 'dhcp;bootm'                 [load kernel from TFTP and boot] U-Boot > setenv bootargs <NFS bootargs>              [For different platforms, please refer to below table; do not add ''] U-Boot > saveenv                                     [Save the environments]

Platform	Bootargs
i.MX51 BBG with WVGA	console=ttymxc0 init=/init androidboot.console=ttymxc0 root=/dev/nfs nfsroot=${serverip}:${nfsroot} rw ip=dhcp di1_primary gpu_memory=16M
i.MX53 SMD with LVDS	console=ttymxc0 init=/init androidboot.console=ttymxc0 root=/dev/nfs nfsroot=${serverip}:${nfsroot} rw ip=dhcp video=mxcdi1fb:RGB666,XGA ldb di1_primary gpu_memory=64M
i.MX50 RDP with E-Ink	console=ttymxc0 init=/init androidboot.console=ttymxc0 root=/dev/nfs nfsroot=${serverip}:${nfsroot} rw ip=dhcp keypad

For the first time boot, it causes some time to finish and finally you can got to the Android UI.

3.4 Boot Up configurations

3.4.1 U-Boot environment

• ethaddr/fec_addr: MAC address of your board
• serverip: IP address of your TFTP/NFS server
• loadaddr/rd_loadaddr: the kernel/initramfs image load address in memory. Different platform may have different loadaddr and rd_loadaddr, listed below: 

• 	I.MX51 BBG	I.MX53 EVK	I.MX50 RD
  loadaddr	0x90800000	0x70800000	0x70800000
  rd_loadaddr	0x90C00000	0x70C00000	0x70C00000

• bootfile: the name of image file loaded by "dhcp" command, when you using TFTP to load kernel.
• bootcmd: the first variable to run after uboot boot
• bootargs: the kernel command line, bootloader passed to kernel. Described in 3.4.2 section
• dhcp: get ip address by BOOTP protocol, and load the kernel image ($bootfile env) from TFTP server.
• bootm: start to run the kernel.

3.4.2 Kernel command line (bootargs)

Kernel Parameter	Description	Typical Value	Used When
console	where to output kernel log by printk	console=ttymxc0	All case
androidboot.console	indicate Android shell where to put log	androidboot.console=ttymxc0	All case for Android (with this parameter, you can use Ctrl-C in Android shell)
init	tell kernel where is the init file	init=/init	All case for Android. "init" in Android is located in "/" instead of in "/sbin"
ip	tell kernel how/whether to get IP address	ip=none or  ip=dhcp or  ip=static_ip_address	"ip=dhcp" or "ip=static_ip_address" is mandatory in "boot from TFTP/NFS"
nfsroot	where is NFS server/directory	rootfs=ip_address:/opt/nfsroot,v3,tcp	Used in "boot from tftp/NFS" together with "root=/dev/nfs"
root	indicate where is the root file system	root=/dev/nfs or root=/dev/mmcblk0p2	Used in "boot from tftp/NFS" (i.e. root=/dev/nfs); Used in "boot from SD" (i.e. root=/dev/mmcblk0p2) if no ramdisk is used for root fs
video	tell kernel/driver which resolution/depth and refresh rate should be used	video=mxcdi0fb:1024x768M-16@60	Used when display on DVI (i.MX51 BBG3 board). Please check "Display Settings" table below for detail.
di1_primary	tell kernel/driver using DI1 display	di1_primary	Used to tell kernel which display interface is the default on for UI.
calibration	tell kernel/driver to do touch panel calibration when 1st boot	calibration	Used when touch panel is needed. i.e. when you display everything on DVI or multitouch screen, no need for this.
gpu_memory	GPU shared memory used by driver	gpu_memory=16M	It's 16MB on MX51 BBG, but 64M on MX53 SMD
keypad (for i.mx50)	Use the keypad on E-ink panel board	keypad	Use the keypad on E-ink panel board

4. Run

4.1 Multimedia

4.1.1 Music Play

• Insert a SD card with music files (such as mp3) on FAT partition
• Connect headset/headphone to your board
• Launch the main menu
• on the BBG3, use UP/DOWN/LEFT/RIGHT key to highlight the MENU icon at the right side of home screen, press ENTER (or F9)
• Launch the Music application by selecting  the Music icon 

4.1.2 Video Play

• Insert a SD card with video stream files (.3gp, .mp4) on FAT partition
• Launch the main menu
• Launch the Gallery application by selecting Gallery icon
• During play, touching the screen will cause a semi-transient pop-up menu to be displayed. You can select backward/forward/pause/play.

4.1.3 Streaming Play

• Launch the main menu
• Launch the Browser application by selecting the Browser icon
• Open a webpage http link with a rtsp streaming link or a multimedia file http link embedded.
• Click the rtsp streaming link or multimedia http link.
• During play, touch the screen displays a semi-transient pop-up menu. You can select backward/forward/pause/play if the streaming server supports those features.

4.1.4 Camera (Still Image Capture)

• Insert a formatted SD card into the board
• Connect a headset to the board (this is a workaround for the PIN max issue. See the Known Issues in the release note documentation)
• Launch the main menu
• Launch the Camera application by selecting the Camera icon
• A preview screen appears (as a viewfinder) (it will take about 3~4 seconds to see the preview)
• Click the button on the left of the preview window to set the parameters for picture, now only support the configuration of the picture size.
  
• Click the Shot icon on the preview screen
• A still image is captured and saved as a JPEG file on the SD card
• Go to Gallery application to see the captured picture

4.1.5 Sound Recording

• Insert a formated SD card into the board
• Connect microphone to the board
• Choose Main Menu > Sound Recorder
• Press the record button to start the recording
• Speak into the microphone
• Press the stop button to pause the recording
• Press the play to listen what has been recorded
• Select Use this recording. The application exits and a new file (.3gp with AMR-NB) is saved to the SD card
• Choose the Main Menu > Music. If you can't see the new .3gp file, try below:
• Choose the Main Menu > SD card & phone storage > Umount SD card
• Remove the SD card and insert the SD card again
• Choose the Main Menu > Music. You should be able to see the recorded sound file

4.1.6 Camcorder

• Insert a formatted SD card into the board
• Connect a microphone to the board
• Choose Main Menu
  
• Launch the Camera application, since the Camera and Camcorder are in one application
  
• Switch to camecorder by the switch button on the left to see preview screen
• Click the record icon, which changes to stop icon.
• Click the button on the left of the preview screen to configure the video recording, now support the Following qualities:
  
• High quality: H.264 & AMR-NB in MP4.
• Low quality: H.263 & AMR-NB in 3GP.
• The Camcorder configure file is in device/fsl/proprietary/codec/conf/media_profiles.xml, in which the format, bitrate, channels, etc can be configured.
  
• Show something before camera sensor and say something to the microphone
• Click the stop icon.
• Quit the Camcorder application
• Choose Main Menu > Gallery to play the video file you just recorded

4.1.7 USB Camera

• rebuild and replace the libcamera.so
  Uncomment hardware/mx5x/libcamera/CameraHal.h
  #define UVC_CAMERA 1
  or add UVC_CAMERA in Android.mk
  
  replace the libcamera.so in /system/lib/
• connect the UVC camera to the board
  Logitech E3500 is support
• open the "camera" or "camcorder" to use

notes: the UVC may be not enable in the default configure, so you can enable it by manual
         Device Drivers  --->
                  <*> Multimedia support  --->
                          [*]   Video capture adapters  --->
                                  [*]   V4L USB devices  --->
                                          <*>   USB Video Class (UVC)

4.2 Storage

4.2.1 USB Mass Storage

4.2.2 Multi-Storage Access

There are total three storages supported in i.MX51 BBG.i.MX51 BBG supports the following storages：

• SD card in MMC/SD connector P1

• SD card in MMC/SD connector P2

• UDISK connected to the board through the USB port

Environment.getExternalSDStorageDirectory()

Environment.getExternalUDiskStorageDirectory()

Environment.getExternalExtSDStorageDirectory()

Environment.getExternalSDStorageState()

Environment.getExternalUDiskStorageState()

Environment.getExternalExtSDStorageState()

4.3 Connection

4.3.1 Enable WiFi

• Choose Main Menu > Setting > Wireless control
• Enable Wi-Fi
• Enter the WiFi settings, it should automatically search all available APs and display them on screen
• Select your WiFi AP, and click connect
• Input password if required
• To make sure you have a WiFI connection type 
  $ netcfg (you should see a wlan0 interface)
• Use the browser to access the internet

4.3.2 Browse Internet using 3G Modem Connection

• Install the HuaWei EM750M module and antenna on the EM750M debug board
• Insert a SIM card into the SIM slot on the HuaWei EM750M module debug board
• Connect the EM750M module debug board to BBG3 board with a USB cable
• Power up the EM750M module (until the red LED is let)
• Wait for a few seconds, you should be able to use Dialer or Message to call others or send SMS
• Setup APN for packet call:
• Choose Main Menu > Wireless control > Mobile Networks > Access Point Names
• Press the MENU key and select New APN
• Name: ChinaMobile (any name you can choose), APN: cmnet (contact your operator), MCC/MNC:460/00 (country/network code for your operator)
• Press the MENU key and select Save
• reboot the board
• After reboot, make sure you already connect to internet via 3G modem:
   $ netcfg (you should see a ppp interface)
   $ getprop net.dns1 (a meaningful IP address should be displayed)
• Launch browser 

4.3.3 Enable the AR6002 WIFI card

    Notes: the default enabled is AR6003; the AR6102 also can use the same module with AR6002

• Change the BOARD_WLAN_CHIP in device/fsl/imx51_bbg/BoardConfig.mk to AR6002

  BOARD_WLAN_CHIP             := AR6002

• setenv bootargs_android 'setenv bootargs ${bootargs} ip=dhcp init=/init androidboot.console=ttymxc0 di1_primary gpu_memory=32M video=mxcdi0fb:RGB24,720P60 video=mxcdi1fb:RGB666,XGA ldb calibration'

Dual-Display feature can be enabled dynamically with below steps:

setprop rw.SECOND_DISPLAY_CONNECTED 1

setprop sys.SECOND_DISPLAY_ENABLED 1

setprop rw.SECOND_DISPLAY_CONNECTED 0

setprop sys.SECOND_DISPLAY_ENABLED 0

4.4.4 24bpp pixel format support for UI

4.5 Application & Development

4.5.1 Key Map

The key mapping for a Dell USB keyboard used with the BBG3 board (defined in /system/usr/keylayout/Dell_Dell_USB_Keyboard.kl) is as follows:

Key	Act as
ESC	BACK
F1	MENU
F2	SOFT_RIGHT
F3	CALL
F4	ENDCALL
F5	ENDCALL
F8	HOME
F9	DPAD_CENTER
UP	DPAD_UP
DOWN	DPAD_DOWN
BACK	DEL
ENTER	ENTER

The key map of the keypad on the BBG3 add-on peripheral board (defined in /system/usr/keylayout/mxckpd.kl) is as follows:

POWER	N/A	CALL	VOLUME_UP		DPAD_LEFT		MENU
				DPAD_DOWN	DPAD_CENTER	DPAD_UP	HOME
CAMERA	N/A	ENDCALL	VOLUME_DOWN		DPAD_RIGHT		BACK

The key map of the keypad on the i.MX508 (defined in /system/usr/keylayout/mxckpd.kl) is as follows:

Key	Act as
PREV(SW2)	BACK
F1(SW5)	MENU
F9(SW15)	ENTER
9(SW24)	DPAD_LEFT
0(SW25)	DPAD_RIGHT
O(SW34)	DPAD_UP
P(SW35)	DPAD_DOWN
POWER(SW70)	POWER
RESET(SW71)	RESET
NXT1(SW3)/NXT2(SW4)	DPAD_CENTER

For imx53_EVK/imx50_PD, the "power key" on board support the suspend/resume operation.

4.5.2 Adjust Media Volume for Music and Video

Main Menu > Settings > Sound > Volume

4.5.3 Adjust Brightness of LCD Backlight

Main Menu > Settings > Display > Brightness

4.5.4 longer Screen Timeout

Main Menu > Settings > Display > Screen timeout > 30 minutes

4.5.5 ADB over USB

In linux environment, the "idVendor" must be set.  Now, the "idVendor" is "0x0bb4".

# Log in as root and create this file: /etc/udev/rules.d/51-android.rules.

SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"

# Now execute:

chmod a+r /etc/udev/rules.d/51-android.rules

4.5.6 App to SD

4.5.7 Software Update and Wipe Partition using Recovery Mode

• Prepare for all android source code that assumed to be saved in ~/myandroid directory. 
• Prepare for ADB over USB. make sure that ADB over USB is ok. USB cable is connected. Refer to ADB over USB section for more information.
• Connect the UART to the PC and open a terminal to check for printed messages
• Enter the recovery by manual
  

       for imx51_BBG board:
       setenv bootargs_android_recovery 'setenv bootargs ${bootargs} init=/init root=/dev/mmcblk0p4 rootfs=ext4 di1_primary'
       setenv bootcmd_android_recovery 'run bootargs_base bootargs_android_recovery;mmc read 0 ${loadaddr} 0x800 0x1800;bootm'
       run bootcmd_android_recovery
       For imx53_EVK board:
       setenv bootargs_android_recovery 'setenv bootargs ${bootargs} init=/init root=/dev/mmcblk0p4 rootfs=ext4'
       setenv bootcmd_android_recovery 'run bootargs_base bootargs_android_recovery;mmc read 0 ${loadaddr} 0x800 0x1800;bootm'
       run bootcmd_android_recovery

• When system had complete to bootup, the following UI appears : 

• Select the required option using the direction keys on the keypad or keyboard.
• Apply sdcard:update.zip, you may update the software from update.zip as shown in the following example:
• Copy this directory from android source code myandroid/bootable/recovery/etc to a tempepory directory, such as ~/recovery. 
• cd ~/recovery and remove init.rc from this directory. 
• Edit ./META-INF/com/google/android/updater-script.ext4 according to the required commands. for example, in order to format /system partition and use update.zip to update system partition, copy whole the entire content directory to system partition, all commands are found in ~/myandroid/bootable/recovery/update/install.c
• You must notice, when your signing the zip package, it will lose ALL of the permission information, you need to set the right permission in the script. You can find the example in ./META-INF/com/google/android/updater-script.ext4 (Notice, In the update.zip there only ONE script, named updater-script, you should rename the example script)
• Example scripts: There were two example script in code base:
  
• updater-script.ext4  is copy all files under update.zip:system/ to your device's system/
• updater-script-patched.ext4 is using binary patch to upgrade your device.
  
• Also, since froyo, update-script already rename to updater-script.
  
• Copy update-binary, Copy out/target/product/YOU_PRODUCT/system/bin/updater to ~/reocvery/META-INFO/com/google/android/update-binary
  

• Create a directory called system and copy some files you would like to update to ./system.
• Create a directory called res to save the public key of your system.
  
  fsl@fsl-desktop:~/recovery$ mkdir res
  fsl@fsl-desktop:~/recovery$ ~/myandroid/out/host/linux-x86/framework/dumpkey.jar ~/myandroid/build/target/product/security/testkey.x509.pem > res/keys
  
  
  
• Create a package called recovery.zip using the zip command

  fsl@fsl-desktop:~/recovery$zip recovery.zip -r ./META-INF ./system ./res

• recovery.zip is located in the current directory. Then create a digital signature for recovery.zip package as follows.

  fsl@fsl-desktop:~/recovery$ cd ~/myandroid fsl@fsl-desktop:~/myandroid$ make signapk fsl@fsl-desktop:~/myandroid$ cd ~/recovery fsl@fsl-desktop:~/recovery$ java -jar ~/myandroid/out/host/linux-x86/framework/signapk.jar -w ~/myandroid/build/target/product/security/testkey.x509.pem ~/myandroid/build/target/product/security/testkey.pk8 recovery.zip recovery_signed.zip

• recovery_signed.zip is located in the current directory. Copy it to the SD card using ADB

  fsl@fsl-desktop:~/recovery$ adb push recovery_signed.zip /sdcard/update.zip

• update.zip is completed and the system is updated based on the commands in the update-script. Check for error messages on the LCD. 

• Wipe data/factory reset. /data and /cache partitions are formatted.
• Wipe cache partition. /cache partition is formatted. 

• Reboot the system.          

4.5.8 3D Demo

• The image distortion in the 3D screen shown above is caused by screen capture.
• To disable hardware 2D for UI frameworks (surfaceflinger), use this command:

  $ setprop debug.sf.enable_hgl 0

• To disable hardware 2D/3D (use Android software 2D/3D implementation), use this command:

  $ setprop debug.egl.hw 0

• To show FPS(frame per second) in LOGCAT, use this command:

  $ setprop debug.sf.showfps 1

fastboot.exe reboot

TARGET_KERNEL_2G := true

5. FAQ

5.1 Why did the code fail to download from Google when repo init?

        Perhaps because you are behind the firewall. If you have http proxy and your firewall support socks, then take the following steps:
 

* Install Dante - a socks client        $ sudo apt-get install dante-client     * Configure Dante by adding below lines into /etc/dante.conf           route {                 from: 0.0.0.0/0 to: .  via: DNS_OR_IP_OF_YOUR_SOCKS_SERVER port = PORT_OF_YOUR_SOCKS_SERVER                 proxyprotocol: socks_v5                     }       resolveprotocol: fake       * Set environment variable for http proxy and socks       $ export http_proxy=...        $ export SOCKS_USER=...        $ export SOCKS_PASSWD=...       * Download Android code from google        $ curl http://android.git.kernel.org/repo > ./repo         $ chmod a+x ./repo         $ socksify ./repo init -u git://android.git.kernel.org/platform/manifest.git -b froyo     $ cp /opt/imx-android-r10/code/r10/default.xml .repo/manifests/default.xml         $ socksify ./repo sync

5.2 Why I can't access the internet with browser using ethernet?

        It always reports "Web page not available" even if I have directly internet access (not behind a proxy/firewall. Note: Android browser seems not support proxy setup)?

DNS setup. For ethernet, the Android does not setup DNS automatically. So DNS must be manually setup. This is not an issue for WiFi since dhcpcd is explicitly called after WiFi access is available.

How to solve/workaround this issue:
In console, input setprop net.dns1 IP_OF_YOUR_PRIMARY_DNS_SERVER. Ping any host with DNS name. If successful, you should be able to use Browser to access any web site now.

5.3 Can I access Android shell using ethernet instead of a serial port?

        Yes. On the Linux PC (assume you had built Android code or install Android SDK), complete the following actions:

$ ping IP_OF_YOUR_BOARD (run "netcfg" on board to get IP address)     $ export ADBHOST=IP_OF_YOUR_BOARD     "adb" is a host tool created during Android build.It's under out/host/linux-x86/bin/. Make sure you set path properly.     $ adb kill-server (not sure why need this step. Just re-start adb daemon on board)     $ adb shell     # NOW YOU ARE IN ANDROID SHELL ON BOARD

5.4 How do I change Android boot logo?

        If there is a file called initlogo.rle under the root folder, Android displays it while booting. Complete following steps to create a rle compressed picture from a png file.

             1. Find an image you like
             2. Edit it with your favorite editing suite and scale it to 480x640
             3. After scaling it, convert the colorspace to 256 colors (8-bit)
             4. Save it as a PNG without alpha channel/transparency.
             5. Use the convert tool from the ImageMagick toolkit: convert -depth 8 splash.png rgb:splash.raw
             6. Compile the Android tool in mydroid/build/tools/rgb2565(gcc -O2 -Wall -Wno-unused-parameter -o rgb2565 to565.c)
             7. Run the conversion command: rgb2565 < splash.raw > splash.raw565
             8. Copy splash.raw565 to mydroid/out/target/product/imx51_BBG/root/initlogo.rle. make it to zImage ramdisk for nand boot

5.5 How to use wake_lock to control specific devices?

        If an application hold a wake_lock, the system will not enter suspend mode. Except turn off LCD, you may want to do more things to control device during the time of holding a wake_lock. For instance, if mp3 player holds the wake_lock called “audioplay”, device drivers can also call register_lock_handle() with the same lock name as parameter, to register one or more device handles dealing with power related operation during early suspend.This is an extension to refine devices control during early suspend.