NOTICE: The Processors Wiki will End-of-Life in December of 2020. It is recommended to download any files or other content you may need that are hosted on The site is now set to read only.

TI-Android-GingerBread-2.3.4-DevKit-2.1 DeveloperGuide

From Texas Instruments Wiki
Jump to: navigation, search



TI Android GingerBread 2.3.4 DevKit 2.1 Developer Guide

The objective of this document is to guide Android developers to get access to Android sources for TI devices, setting up host environment for compilation and enabling debug environment to ease the app development, debugging and deployment.

Host (PC) setup requirements

The host development environment for Android is based on ubuntu, please install ubuntu version 10.04 or later The host installation would need few more Android specific dependencies, these can be installed dynamically over network using below commands.

For Ubuntu on 32-bit machines

  $ sudo add-apt-repository "deb lucid partner"
  $ sudo add-apt-repository "deb-src lucid partner"
  $ sudo apt-get update
  $ sudo apt-get install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev minicom tftpd uboot-mkimage expect
  $ sudo update-java-alternatives -s java-6-sun


  1. Android Gingerbread (2.3.4) needs Java 6 on ubuntu, whereas the previous version FroYo (2.2) was using Java 5.
  2. Please refer to the AOSP for latest information

Source locations

TI provides Android sources for all the supported devices in multiple locations, developers can download the sources from the repository or use the pre-packaged repo in the DevKit.


A tool called 'Repo' helps to fetch the android sources from Repo is a tool that makes it easier to work with Git in the context of Android.
For more information about Repo, see the link
To install, initialize, and configure Repo, follow these steps:
Make sure you have a bin/ directory in your home directory, and that it is included in your path:

  $ mkdir ~/bin
  $ PATH=~/bin:$PATH

Download the Repo script and ensure it is executable:

  $ curl > ~/bin/rep
  $ chmod a+x ~/bin/repo

The following commands help developers to clone sources from repository

  $ mkdir rowboat-android
  $ cd rowboat-android
  $ repo init -u git:// -m TI-Android-GingerBread-2.3.4-DevKit-2.1.xml
  $ repo sync

Using pre-packaged repo

The above method is ideal but is time consuming, so developers can use the pre-packaged Android sources in DevKit package.

NOTE: Once the sources are generated developers can do a “repo sync” to pull latest updates (if any) from

  $ mkdir rowboat-android
  $ cd rowboat-android
  $ Download the pre-packaged repo from
  $ tar -xvzf 	TI_Android_GingerBread_2_3_4Sources.tar.gz
  $ cd 	TI_Android_GingerBread_2_3_4Sources
  $ ./.repo/repo/repo sync --local-only

This will generate the sources for

  • Android File system
  • Android Linux Kernel (in kernel directory)
  • u-boot boot loader (in u-boot directory)
  • x-loader (in x-loader directory)
  • Toolchain (prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin)

Tool chain setup

Setup the tool-chain path to point to arm-eabi- tools in prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin

  $ export PATH=<PATH_TO_ROWBOAT>/rowboat-android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH

Compilation procedure

To build x-loader

  • Change directory to x-loader
  $ cd x-loader

Execute the following commands

$ make CROSS_COMPILE=arm-eabi- distclean
$ make CROSS_COMPILE=arm-eabi- <config>
$ make CROSS_COMPILE=arm-eabi-
  • Where config is omap3evm_config for AM37x EVM
  • Where config is omap3beagle_config for Beagleboard-xm
  • Where config is am3517evm_config for AM35x EVM

This command will build the x-loader Image "x-load.bin"

To create the MLO file used for booting from a MMC/SD card, sign the x-loader image using the signGP tool found in the Tools/signGP directory of the Devkit.\

  Note: you will need to copy the signGP tool from the Tools/signGP directory to the directory that contains the x-load.bin file
  $ ./signGP ./x-load.bin

The signGP tool will create a .ift file, rename the x-load.bin.ift to MLO

  $ mv x-load.bin.ift MLO

To build boot loader (u-boot)

  • Change directory to u-boot
  $ cd u-boot
  • Do the following to build u-boot for AM37x EVM
  $ make CROSS_COMPILE=arm-eabi- distclean
  $ make ARCH=arm CROSS_COMPILE=arm-eabi- <config>
  $ make ARCH=arm CROSS_COMPILE=arm-eabi- 
  • Where config is omap3_evm_config for AM37x EVM
  • Where config is omap3_beagle_config for Beagleboard-xm
  • Where config is am3517_evm_config for AM35x EVM

This command will generate the u-boot Image "u-boot.bin"

NOTE: Copy the "mkimage" from "tools" folder to /usr/bin folder on your host machine, this is needed for kernel uImage generation

To build Linux kernel

  • Change directory to kernel
  $ cd kernel
  • Do the following to build sources for AM37x EVM
  $ make ARCH=arm CROSS_COMPILE=arm-eabi- distclean
  $ make ARCH=arm CROSS_COMPILE=arm-eabi- <config>
  $ make ARCH=arm CROSS_COMPILE=arm-eabi- uImage
  • Where config is omap3_evm_android_defconfig for AM37x EVM
  • Where config is omap3_beagle_android_defconfig for Beagleboard-xm
  • Where config is am3517_evm_android_defconfig for AM35x EVM

This will generate uImage (kernel image) in kernel/arch/arm/boot folder

To build Android filesystem

Filesystem with SGX

To Build the root file system for AM37x (or Beagle XM, AM35x EVM, AM37x REV G EVM)

  $ cd <PATH_TO_ANDROID_SOURCES> (i.e. ~/rowboat-android or ~/rowboat-android/TI_Android_GingerBread_2_3_4Sources)
  $ make TARGET_PRODUCT= <product name> OMAPES=<ES version> -j<N> 
  NOTE: product name can be beagleboard (For Beagleboard Rev Cx and Beagleboard XM A/B/C)or omap3evm (For AM37x or OMAP35x)or am3517evm(For AM35X)
  OMAPES variable controls the ES version of the device
  For AM35x                = 3.x
  For AM37x                = 5.x
  For OMAP35x              = 3.x
  For Beagleboard Rev Cx   = 3.x
  For Beagleboard XM A/B/C = 5.x
  <N> should be twice the number of processors on your host machine. For example, a dual core machine would use -j4

The above command will build Android FS, kernel, SGX drivers and WLAN drivers (In case of AM37x). After successfull build, the kernel image can be found at kernel/arch/arm/uImage. Android rootfs components (root and system folders) will be located in out/target/ptoduct/omap3evm. SGX drivers and libraries are installed in Android rootfs components. WLAN drivers and firmware are installed in system component of the Android rootfs(For AM37x only).

Filesystem without SGX

To build the root file system for AM37x (or Beagle XM, AM35x EVM, AM37x REV G EVM) without SGX accelerated graphics support

  $ make TARGET_PRODUCT= <product name> droid -j<N> 
  NOTE: product name can be beagleboard (For Beagleboard Rev Cx and Beagleboard XM A/B/C)or omap3evm (For AM37x)or am3517evm(For AM35X)
  <N> should be twice the number of processors on your host machine. For example, a dual core machine would use -j4
  NOTE: If filesystem is already built with SGX, then the projects need to be cleaned using the following command:
       $ make TARGET_PRODUCT= <product name> clean

Create root filesystem tarball

Prepare the root filesystem as follows:

  $ cd out/target/product/omap3evm
  $ mkdir android_rootfs
  $ cp -r root/* android_rootfs
  $ cp -r system android_rootfs
  $ sudo ../../../../build/tools/ ../../../host/linux-x86/bin/fs_get_stats android_rootfs . rootfs rootfs.tar.bz2

The rootfs.tar.bz2 is the android filesystem, it can be put on a SD/MMC Card or used our NFS.

RowboPERF Integration

  • Download the sources from rowboat
   #> git clone -b rowboat-gingerbread git://
   #> cd rowboperf
  • Refer the instructions in the README file for building and installing rowboperf components

NOTE: Clone rowboperf sources outside the rowboat-android tree.

Adobe Flash 10 Integration

The Android version of Flash10 that runs on GingerBread is now available for customer download (by registration) at,

The below steps give the procedure to download the Adobe Flash 10 library for Android GingerBread and installing the same in File system.

  • Execute the installer
  $ ./TI Flash10.3 Android Webkit Plugin-0.80-Linux-x86-Install.bin

Will result in following instruction, press "Y"

  This will install Flash10.1 Android Webkit Plugin on your computer.  Continue? [n/Y] Y
  Select the source install location
  Where do you want to install Flash10.1 Android Webkit Plugin? 
  [/home/user/flash10_androidplugin] /home/user/flash10_androidplugin
  Installing Flash10.1 Android Webkit Plugin...
  Installing Program
  Installation complete.
  After Installation the following directory structure is resulted 
  • Change to Flash installed directory on Host PC
  $ cd flash10_androidplugin 
  $ ls
  install_flash_player.apk  uninstall
  $ adb install install_flash_player.apk
  • Do the browser configuration
    • Explained in the below section

To generate SD/MMC card to boot Android

These compiled Images can be copied to a SD / MMC card to boot Android on AM37x EVM The utility mk-bootscr from Tools package can be used to generate a boot script(boot.scr) for the evm to boot automatically.(Provided the NAND environment is empty)

  $ ./mkbootscr
  • Copy all the images to one folder
  $ mkdir image_folder
  $ cp kernel/arch/arm/boot/uImage image_folder
  $ cp u-boot/u-boot.bin image_folder
  $ cp x-loader/MLO image_folder
  $ cp Tools/mk-bootscr/boot.scr image_folder
  $ cp out/target/product/omap3evm/rootfs.tar.bz2 image_folder
  $ cp media_clips image_folder
  $ cp Tools/mk-mmc/ image_folder
  $ ./mkmmc-android <sd card mounted dev folder example:/dev/sdc> MLO u-boot.bin uImage boot.scr rootfs.tar.bz2 Media_Clips

NOTE: and mk-bootscr are provided in tools folder in DevKit

Hardware Setup and Requirements

This release of TI Android GingerBread 2.3.4 DevKit 2.1 is evaluated on the below given list of platforms. This package should be easily portable on other platforms on similar TI devices.


TI Device Platform Supported Version Other Accessories

OMAP35x EVM Rev G DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)

Beagleboard Rev Cx DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)

AM3517 Evaluation Module Rev C DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)

AM37x Evaluation Module Rev C DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)

BeagleBoard XM Rev A/B DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)


  • EVM

This section describes the setup and instructions to run TI’s Android DevKit OOB demo on AM37x/DM3730 EVM.

Step 1: Insert SD card into MMC/SD slot on the EVM

Step 2: Set the DIP switch settings to boot from MMC/SD card

AM37x EVM the DIP switch SW4 should be set as shown below


AM35x EVM the DIP switch S7 should be set as shown below

1 2 3 4 5 6 7 8

Step 3: Turn ON the EVM

Refer to UserGuide and RowboPERF user guide from document folder in DevKit release

  • Beagle XM

Step 1: Insert SD card into MMC/SD slot on the Beagleboard

Step 2: Turn ON the Beagleboard

Refer to UserGuide and RowboPERF user guide from document folder in DevKit release

Application Development and Debugging

Using TI's Code Composer Studio V5 (Eclipse based)

Code Composer Studio (CCS) is the integrated development environment for TI's DSPs, microcontrollers and application processors based on the Eclipse open source software framework which includes a suite of tools used to develop and debug embedded applications. Since CCS is based on Eclipse, it is possible to integrate the Android Development Tools (ADT) like Android Debug Bridge (ADB), Dalvik Debug Monitoring System (DDMS) and ndk-gdb in CCS to enable the debugging of Android Applications directly on Android Device (i.e TI EVM) along with the inherent CCS capability of Linux Aware Debug and DSP Debugging.

This wiki walks you through installation of Android Debugging Tools in CCS, connecting CCS with Android Device and illustrates a debugging session of an HelloWorld Application based on android NDK having a mix of Java and Native C Code.

Preparing CCS for Android Development

Note: The steps below are condensed version of steps mentioned on

1. Installing the ADT Plugin in CCS Refer

2. Adding Platforms and Other Components

  • On Windows, double-click the SDK Manager.exe file at the root of the Android SDK directory
  • On Linux, run '<SDK>tools/android'
  • Proxy Settings (If needed): Go to Settings and set the Proxy to work with your network
  • To download components, use the graphical UI of the Android SDK and AVD Manager, shown in Figure below, to browse the SDK repository and select new or updated components. The Android SDK and AVD Manager will install the selected components in your SDK environment. Refer the list of Recommended Components:


Setup debugging via ADB over network

Step 1: Upon installing the ADT plugin, DDMS should have been setup. DDMS configuration should be changed as in below:

Click on Window->Preferences; Select Android -> DDMS
Change - ADB debugger base port: 8700; Logging Level: Verbose
Click on Apply

Step 2: DDMS perspective can now be opened from the eclipse menu via:

Window -> Open Perspective -> Other -> DDMS; 
Click on OK

Step 3: Get CCS to attach to your TI EVM:

Things to do on Android Device: Obtain IP of your EVM via the executing following command on your EVM’s Serial Terminal:

      # netcfg

ADB stub on target defaults to USB. To fix this, execute the following on your EVM’s Serial Terminal :

# setprop service.adb.tcp.port 5555
# stop adbd
# start adbd

On the Host machine run the following commands from cmd prompt:

 $ cd <ANDROID_SDK_ROOT>\platform-tools
 $ adb kill-server
 $ adb start-server
 $ adb connect <target_ip_address>:5555

Check if you are now connected to the TI EVM device by running the following command on the cmd prompt:

 $ adb devices

It should output something like:

 emulator-5554 device

This confirms that EVM is connected. With this setup, you should be able to use ADB, logcat, DDMS and other tools directly from CCS ADT environment for creating your applications for Android.

Note: you can refer the following for more details:

Debugging Android with CCS

Hello World Application on Android Virtual Device (AVD)

Hello-jni of Android NDK on Android Device

  • In CCS:
  1. Click File > New Android Project...
  2. Select the Create project from existing source radio button.
  3. Select any API level above Android 1.5.
  4. In the Location field, click Browse... and select the <ndk-root>/samples/hello-jni directory.
  5. Click Finish.
  6. Go to C/C++ Perspective. Click File->New->Convert to C/C++ Project
  • Edit jni/ and add the following line before BUILD_SHARED_LIBRARY: APP_CFLAGS := -g. This will add debugging symbols in to your native C code.
  • Compile the native code using the ndk-build command from cmd prompt:
  cd <ndk-root>/samples/hello-jni
  • In CCS, create a debug configuration for a C/C++ application:
    • Create a new debug configuration for a C/C++ application. Click Run->Debug Configurations.
    • Set the process launcher to “Standard Create Process Launcher”
    • On “Main” tab, set:
      C/C++ Application: android-ndk-r5-windows\android-ndk-r5\samples\hello-jni\obj\local\armeabi\app_process
      Select Disable auto build
    • On “Debugger” tab, set:
      • Debugger: gdbserver
      • Stop on startup at: Java_com_example_hellojni_HelloJni_stringFromJNI (It is the entry function of the native C code)
      • Main Tab:
        • GDB debugger: android-ndk-r5-windows\android-ndk-r5\toolchains\arm-eabi-4.4.0\prebuilt\windows\bin\arm-eabi-gdb.exe
        • GDB command file: android-ndk-r5-windows\android-ndk-r5\samples\hello-jni\libs\armeabi\gdb.setup
        • GDB command set: Standard
        • Protocol: mi
        • Select only Verbose console mode
      • Connection Tab:
        • Type: TCP
        • Host name or IP address: localhost
        • Port number: 5039
  • Open the ndk-gdb script that came with the android NDK and comment the last line (we are not calling the usual gdb client, but we will attach an Eclipse gdb session instead)
  • Only For Windows: Run dos2unix.exe on ndk-gdb from cygwin after editing to make sure that we do not have any unwanted dos symbols in the script

  • Starting Java Debugger:
    • Make sure you are in Java Perspective.
    • Click Run->Debug Configurations.
    • Place a breakpoint in Java code just before the native code call
    • Select Android Debug Configuration instance “HelloJni” and click “Debug”
    • It will prompt you to switch and open to CCS Debug Perspective. Select “yes”

  • Starting GDB Debugger:
    • In cygwin, make sure that the root of android-ndk is in PATH.
    • In cygwin, Go to /android-ndk-r5-windows/android-ndk-r5/samples/hello-jni and execute the following and wait until you get a prompt again:
  ndk-gdb –adb=<PATH_TO_android-sdk-windows/platform_tools/adb.exe>
sample command: $ ndk-gdb --adb=/cygdrive/c/PROGRA~1/Android/android-sdk-windows/platform-tools/adb.exe
    • CCS, go to C/C++ Perspective and click Run->“Debug”. This will launch the gdbserver in CCS Debug Perspective.
    • Now, you can seamlessly debug between Java and Native C code

Using ADB Android Debugger, Downloader

Android Debug Bridge (adb) is a versatile tool lets you manage the state of the Android-powered device. For more information about what is possible with adb, see Android Debug Bridge page at The ADB tool can be used to

  • Download an application from a host machine, install & run it on the target board.
  • Start a remote shell in the target instance.
  • Debug applications running on the device using the debugging tool DDMS ( Dalvik Debug Monitor Server) which runs on top of adb connection.
  • Copy files to and from the board to host machine

Downloading "ADB" & Host setup

The adb tool is a part of Android SDK package located at For an overview of how to install and set up the Android SDK, follow download & setup instructions from Once you install Android SDK, the directory contents look like this.

SDK Readme.txt

The adb tool is located in tools/ directory under the Android SDK installation. Export the tools directory path as shown below.

  $ export PATH=${PATH}:<your_sdk_dir>/tools

Connecting Host machine to board through adb

This release of DevKit has been tested for three different methods of connecting a given board with host machine

  • adb over USB
  • adb over USB Ethernet
  • adb over Ethernet

The below sections describe each of these methods and provides necessary instructions for the same.

adb over USB

  • Make sure that the mini-usb cable is connected between the host usb port and the target’s USB OTG port
  • Turn on "USB Debugging" on your board. On the board (UI screen)-
    • Go to home screen, press MENU,
    • Select Applications, select Development, then enable USB debugging.
    • Alternatively, you can navigate to Settings->Applications->Development and then enable the "USB debugging" option.
  • Setup host machine to detect the board. On Ubuntu Linux host machines this is done by adding a rules file to configure device vendor ID of on-board OMAP device.
  • For the EVMs and Boards covered here, the vendor ID is "18d1".
    • Log in as root and create this file: /etc/udev/rules.d/51-android.rules
    For Gusty/Hardy, edit the file to read:
    SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
    For Dapper, edit the file to read:
    SUBSYSTEM=="usb_device", SYSFS{idVendor}=="18d1", MODE="0666"
    • Execute the following to change the user mode for the rules file.
    $ chmod a+r /etc/udev/rules.d/51-android.rules
    • Verify the adb connectivity between host and target board
    $ adb devices 
    If device is connected, then output on screen should list the device, example:
       List of devices attached
       20100720    device

adb over USB Ethernet (Ethernet over USB)

  • Make sure that the mini-usb cable is connected between the host usb port and the target's USB OTG port.
  • Configure the Linux kernel to use Ethernet gadget. Enable USB support, configure the Inventra controller, and add USB gadget support.

IMPORTANT NOTE: Inventra configuration must occur in two places as shown in non-highlighted lines of the screen shots below.

    $ make ARCH=arm CROSS_COMPILE=arm-eabi- menuconfig

Device Drivers --- USB Support


Device Drivers --- USB Support --- USB Gadget Support

Android USBGadget ADB.JPG

Device Drivers --- USB Support --- USB Gadget Support --- Enable Gadget Ethernet support

Android USBEthernet ADB.JPG

  • Build the Kernel with the above configuration changes and use the uImage to boot the board. Refer to Kernel compiling instructions above.
  • Establish network connection
    • Assign an IP address to the usb ethernet adapter.

The USB network gadget g_ether is named usb0 (instead of eth0 or other network interface names). The normal set of Ethernet configuration tools should work, such as ifconfig, netstat, and route.

For example, the following commands will assign the network address to the target. Run this on the target:

    $ ifconfig usb0 netmask up

On Host machine, run the following commands to establish the connection to the target:

    $ sudo ifconfig usb0 netmask up
    $ sudo route add dev usb0

The target and the host machine should be connected, run ping command to test the same:

    $ ping -c 3
    PING ( 56(84) bytes of data.
    64 bytes from icmp_seq=1 ttl=64 time=6.08 ms
    64 bytes from icmp_seq=2 ttl=64 time=0.511 ms
    64 bytes from icmp_seq=3 ttl=64 time=0.485 ms
    --- ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2000ms
    rtt min/avg/max/mdev = 0.485/2.361/6.089/2.636 ms

  • Establish ADB connection

On the host machine execute following commands to establish adb connection

    $ export ADBHOST=<target's ip address>
    $ adb kill-server
    $ adb start-server
    $ adb connect <target_ip_address>:5555

Verify the connection by executing

    $ adb devices 

If connected, device name should be listed as a "emulator"

    $ adb devices
    List of devices attached
    emulator-5554    device
    $ adb shell

adb over Ethernet

  • Make sure Ethernet port on board and host machine are connected to the network
  • Check Ethernet configuration for the board
    target #> netcfg                                                                        
       lo       UP       0x00000049                       
       eth0     UP   0x00001043                       
  • If Ethernet was not configured, configure Ethernet of the board using ifconfig/netcfg as shown below.
    target #> netcfg eth0 dhcp
  • Configure the ADB Daemon to use an ethernet connection using setprop as shown below.
    target #> setprop service.adb.tcp.port 5555

  • If network is configured successfully (above steps) then Restart service adbd on the target,
    target #> stop adbd
    target #> start adbd
  • On the host machine use following commands to establish adb connection
    $> export ADBHOST=<target's ip address>
    $> adb kill-server
    $> adb start-server
    $> adb connect <target_ip_address>:5555
  • Verify for device connectivity, by executing the following commands
    $> adb devices If connected, you'll see the device name listed as a "emulator"
    $> adb devices
    If connected, find the device name listed as a "emulator"
    List of devices attached
    emulator-5554    device
    $ adb shell 

For more information about adb commands, see Android Debug Bridge page at

adb over USB on Windows Machine

Follow the below instructions to get ADB over USB work on a Windows PC

  • Download latest Android SDK

( and uncompress it in a local folder (i.e. c:\android_sdk).

  • Optionally, you may want to add the location of the SDK's primary tools directory to your system PATH. Right-click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path (under System Variables). Add the full path to the tools\ directory to the path.
  • Download Android USB Driver

( and uncompress it in a local folder (i.e. c:\android_sdk\usb_driver)

  • Edit (or create and then edit if it doesn't already exist) file in


  echo 0x18D1 > "%USERPROFILE%\.android\adb_usb.ini"
  • Edit android_winusb.inf to match EVM/Beagle vendor and product ids:

Under [Google.NTx86] section add:

  %SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_9018
  %CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_9018&MI_01

Note: Be careful to add it under Google.NTx86 and not under Google.NTamd64 unless your machine is AMD 64 bits. If you skip this step you won't be able to later install the driver as windows will reject it.

  • Boot the board as normal and wait until shell prompt is available (micro-B USB cable must be disconnected).
  • Connect micro-B USB cable between board and Windows PC.
  • If it is proceeding as planned, Windows will tell you it found a new hardware asks you to install the driver. Install driver that was downloaded as described in step 3 above:

Answer "No, not this time" to the question about running Windows Update to search for software.

    • Choose "Install the hardware that I manually select from a list (Advanced)" this is the 2nd option, then click "Next"
    • Select "Show All Devices", then click "Next"
    • You are going to see a grayed-out text box with "(Retrieving a list of all devices)", click the "Have Disk..." button
    • Browse" to your driver folder (c:\android_sdk\usb_driver). It will be looking of a .inf file so select "android_winusb.inf" and click "Open" then "OK". It's the only file there so you shouldn't go wrong.
    • Select "Android ADB Interface" then click the "Next" button.
    • A warning will appear, answer "Yes" but read the warning anyway.
    • Click the "Close" when the wizard is completed.
  • Disconnect and reconnect micro-B USB cable from Board(probably reboot it as well).
  • Open command prompt and restart adb server just to make sure it is in a proper state:
  adb kill-server
  adb start-server
  • List the attached devices with "adb devices". It should show your board/device with a random number.
  • Type "adb shell". You should see the "#" indicating it works.

Running Applications

The root File System provided in this DevKit releases contains only standard Android components and applications. User might be interested to download & run android applications (.apk) available in the market. The below procedure gives the steps to be followed to download any .apk file to the board and run it on the platform.

Installing (.apk files) application on Target Platform

  • From the host: You can use adb tool for package installation.
    $> adb install <package>.apk. 

NOTE: Use -s option with the adb tool, to install the package on external storage.

On successful installation adb tool will report SUCCESS on host terminal, and the application would be listed on the android main menu.

Un-installing applications (.apk) using adb

  • To un-install non-default components (that were installed later)
    • Method 1: On the host machine execute the following
    $> adb uninstall <package>.apk
    • Method 2: On target:
    Main menu -> Menu -> Settings -> Applications -> Manage applications -> Find the package 
    Tap on it -> Uninstall -> OK -> OK
    • On successful removal, the application would have been removed from the android main menu. All the short-cuts to the application also removed.
  • To un-install default components, use the following commands from abd on host machine
    $ adb shell
    #rm /system/app/app.apk

On successful removal, the application would have been removed from the android main menu.

Setup ADB for application Debugging

ADB and Eclipse, with ADT( Android Development Tools plug-in) allow users to create and debug Android applications. Follow Developing In Eclipse, with ADT at

Steps to connect Eclipse to the board.

  • Setup the adb connection with the board by following the instructions given above in connecting board ...
    Verify the connectivity by executing 
    $ adb devices
  • Open Eclipse IDE. Eclipse, with ADT plugin enable users to
    • Create an android project.
    • Build and Run the project on a connected board.
    • Debug the project using the Debug perspective.
    • Use DDMS (Dalvik Debug Monitor Server) to monitor the connected board.

For more detailed and complete information on the above follow Developing In Eclipse, with ADT at

  • Open DDMS(Dalvik Debug Monitor Server) perspective. This DDMS perspective can be opened from the eclipse menu via:
    Window -> Open Perspective -> Other -> DDMS; 
    Click on OK
  • DDMS provides port-forwarding services, screen capture on the device, thread and heap information on the device, logcat, process, and radio state information,incoming call and SMS spoofing, location data spoofing, and more.

Copy any files to and from the board over ADB

  • Using the adb commands "pull" and "push" user can copy files to and from the board.
  • Unlike the install command, which only copies an .apk file to a specific location, the pull and push commands let you copy arbitrary directories and files to any location on the board.
  • To copy a file or directory (recursively) from the board, use
    adb pull <remote> <local>
  • To copy a file or directory (recursively) to the board, use
    adb push <local> <remote>

In the commands, <local> and <remote> refer to the paths to the file or directory on your development host (local) and on the target instance (remote).

    Here's an example: 
    adb push foo.txt /sdcard/foo.txt


  • SDK – Software Development Kit
  • NDK – Native Development Kit (For more information, refer
  • ADT – Android Development Tools
  • ADB – Android Debug Bridge
  • DDMS – Dalvik Debug Monitoring System
  • AVD – Android Virtual Device

Quick References

Content Link Ref#
User Guide
Release Notes
Porting Guides


For further information or to report any problems, contact or
For community support join
For IRC #rowboat on