TI-Android-ICS-4.0.3-DevKit-3.0.1 UserGuide - Texas Instruments Wiki PDF
TI-Android-ICS-4.0.3-DevKit-3.0.1 UserGuide - Texas Instruments Wiki PDF
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
processors.wiki.ti.com. The site is now set to read only.
TI-Android-ICS-4.0.3-DevKit-3.0.1 UserGuide
From Texas Instruments Wiki
Jump to: navigation, search
Contents
TI-Android-ICS-4.0.3-DevKit-3.0.1 UserGuide
About this manual
Installation
Hardware Requirements
Software Host Requirements
Host PC requirements
TI Android DevKit Software Release
Setup
Getting Pre-built Images
Procedure to populate MMC/SD Card
Setting Up Hardware
Booting Android
Boot Arguments
Display Options
Using LCD output
Using DVI Monitor
Using VNC Viewer
Android Home Screen
UI Navigation
Keys mapping
Out of the Box Demo
Multimedia Experience
View Image
Play Video
Play Music
Control Volume
Record Sound
TI RowboPerf Experience
Running 2D/3D Demo
Running CPU Benchmark
Browser Experience
Ethernet Configuration
Enable Video Frame Per Second logs in Logcat
Wireless
Wi-Fi
Enabling Wi-Fi
Disabling Wi-Fi
Wi-Fi Hostspot (SoftAP)
Wi-Fi Direct
Changing WLAN MAC address
Bluetooth
Enabling Bluetooth
Disabling Bluetooth
Bluetooth Object Push profile
Sending files
Receiving files
Bluetooth A2DP
Bluetooth HID
Bluetooth Keyboard
Bluetooth Mouse
Bluetooth AVRCP
Accelerometer Sensor
Auto-rotate screen
Amazed Application
Light Sensor
Auto Brightness
Temperature Sensor
Temperature Widget
Power Management
Basic Settings
Enable PM
To go in suspend mode
To resume from suspend mode
To set the Screen Timeout to go suspend
To set set the screen always on preventing suspend
To set Screen Brightness
Auto brightness Control
To set Alarm in Android
Advanced Settings
To Disable Power Management
CPU Dynamic Voltage Frequency Scaling settings
Enabling ondemand frequency governor
Enabling performance frequency governor
Enabling powersave frequency governor
Enabling userspace frequency governor
CPU Idle settings
To minimize the power consumption in runtime
Power Consumption Analysis
Limitations
Booting Android over NFS
Prepare file system on network machine (PC/server)
Booting over Network Filesystem
NAND Booting
Booting NAND Prebuilt Images
Steps to install NAND images on AM335x EVM
Fastboot and UBI rootfs
Establishing Fastboot connectivity
Setup on Device
Setup on Linux host
Setup on Windows host
Creating ubifs images
Fastboot commands
Booting with UBIFS rootfs
ADB Android Debugger & Downloader
Downloading "ADB" & Host setup
Connecting Host machine & board through adb
adb over USB
adb over Ethernet
adb over USB on Windows Machine
Operations over ADB
Installing (.apk files) application on Target Platform
Un-installing applications (.apk) using adb
Copy any files to and from the board over ADB
Install the Rowboperf Appplication on Target Board
Compatibility Test Suite (CTS)
Building Android Sources
SD Card Recommendations
Versioning
Technical Support and Product Updates
TI-Android-ICS-4.0.3-DevKit-3.0.1 UserGuide
User Guide - April 05, 2012
Installation
This section describes the list of Software and Hardware requirements to evaluate the DevKit release.
Hardware Requirements
This release of TI Android ICS 4.0.3 DevKit 3.0.1 can be evaluated on the platforms listed below. This package should be easily portable to other platforms on similar TI devices.
TI Platform
Version Other Accessories
Device Supported
AM335x
Rev 1.1A or USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card
AM335x Evaluation
greater (2GB min)
Module
USB HUB, USB Keyboard, USB Mouse, Ethernet, Mini-B USB Cable, MMC/SD Card (2GB min). Also
AM335x BeagleBone Rev A3
tested with beaglebone cape for DVI-D and LCD.
This release is tested with beaglebone cape for DVI-D and LCD. Beaglebone capes provide additional functionality to the Beaglebone.
The LCD Cape adds 7-Inch LCD output, Touch Screen and 4-Key Keypad for BeagleBone.
Host PC requirements
If you are an Android application developer or would like to use Android SDK Tools then refer to Android SDK Requirements for Host PC requirements.
To evaluate this release we recommend you to have a Linux "Ubuntu 10.04 or above" Host machine, See Ubuntu Linux installation notes
TI Android DevKit Software Release
The TI Android ICS 4.0.3 DevKit 3.0.1 release for AM335x evm and BeagleBone is available as online download from http://software-
dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_ICS_4_0_3_DevKit_3_0_1/index_FDS.html
Setup
This section gives the instructions to quickly prepare an SD Card image and get an experience of TI Android ICS 4.0.3 DevKit 3.0.1 on TI AM335x platforms/devices.
TI_Android_ICS_4_0_3_DevKit_3_0_1 Release Page, for the platform you own AM335x EVM or BeagleBone
Use below commands to untar/uncompress the pre-built image
The tree structure for uncompressed pre-built image directory should be as:
<Board name>
|-- Boot_Images
| |-- MLO
| |-- START_HERE
| |-- u-boot.img
| |-- uEnv.txt
| `-- uImage
|-- Filesystem
| `-- rootfs.tar.bz2
|-- Media_Clips
| |-- Audio
| |-- Images
| `-- Video
|-- README.txt
`-- mkmmc-android.sh
NOTE: <Board name> will be am335xevm for AM335x EVM and beaglebone for BeagleBone.
Insert the USB SD Card reader (with SD Card) in your host Linux PC
Above step will create a bootable MMC/SD card which can be used to boot up the device.
Setting Up Hardware
This DevKit release supports two different platforms AM335x EVM and BeagleBone. While they are different devices the hardware setup will almost remain the same.
AM335x EVM
Connect the UART port (J12 of base board) on AM335x EVM to the Host PC and have a Terminal software like TeraTerm, Minicom or Hyperterminal.
Select Appropriate DIP Switch settings on AM335x EVM to boot over MMC/SD
For MMC/SD boot the DIP switch should be set as (SW3(1:8)=00010111) shown below:
Switch 1 2 3 4 5 6 7 8
State OFF OFF OFF ON OFF ON ON ON
Connect USB cable to the mini-USB port(P3) on BeagleBone to the Host PC and have a Terminal software like TeraTerm, Minicom or Hyperterminal.
Please refer BeagleBone-Android-DevKit Guide for detailed instructions for serial port setup.
Connect the Ethernet (P10) on BeagleBone.
Connect USB Host port (P2) on BeagleBone to USB Keyboard or USB Mouse.
Connect USB keyboard and USB Mouse to the USB HUB for use with BeagleBone.
Insert Micro SD card into MMC/SD slot on the BeagleBone.
Power ON the BeagleBone by connecting power cable to (P5).
Booting Android
Setup the board/platform
For AM335x EVM, Do the DIP switch settings to boot from SD Card, see the DIP switch setting under Setting Up Hardware section.
Insert the Micro/SD Card into the Board
Switch on the platform
Wait for 35sec to get Android up on the UI screen
NOTE: For the first time boot the System might take few minutes to boot.
NOTE: If your NAND flash is not empty the system might not boot with MMC, in that case do the following with Serial Console / Terminal prompt in u-boot
Boot Arguments
AM335X:
setenv bootargs 'console=ttyO0,115200n8 androidboot.console=ttyO0 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait init=/init ip=off'
BeagleBone:
setenv bootargs 'console=ttyO0,115200n8 androidboot.console=ttyO0 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait init=/init ip=off'
Display Options
Please refer to Android Display through VNC guide for more details.
UI Navigation
Note: The soft keyboard will not appear to enter text/data when USB keyboard is connected
Keys mapping
The below table lists the keypad and USB Keyboard mappings for using Android UI functionality.
Keypad
Keypad on
USB USB on
Functionality Beaglebone
Keyboard Mouse AM335x
LCD Cape
EVM
Home Screen Win+Esc
Left Left Arrow SW3
Right Right Arrow SW4
Up Up Arrow
Down Down Arrow SW6
Volume Up
Volume Up SW9
(Multimedia)
Volume
Volume Down Down SW10
(Multimedia)
Power SW5 S3
Esc, Back
Back SW2 S5
(Multimedia)
Menu SW1 S2
Left /
Right /
Select Enter
Middle
Click
Note: There is no keypad available on BeagleBone with DVI-D cape or without any cape, you need to use USB Keyboard/USB Mouse.
Multimedia Experience
Using browser and android applications
View Image
Select "App Launcher" -> "Gallery" -> "Images". Click any thumbnail to view the image.
Double click the image to zoom in/out. Slide the image to view next image.
Play Video
Select "App Launcher" -> "Gallery" -> "Video". Click any thumbnail to play the video.
You can use the UI controls to Pause/Play/Seek the video. To stop playback and exit press the back key button.
Play Music
Select "App Launcher" -> "Music" -> "<Artist>" -> "<song-name>" to experience the music.
Control Volume
Record Sound
Select "App Launcher" -> "Sound Recorder". Press Record button to start recording audio. Press Stop button to stop recording.
Playback the recorded audio by pressing Play button on Sound Recorder GUI.
TI RowboPerf Experience
Running 2D/3D Demo
Select "RowboPERF" -> "3D" -> "Chameleon" or "App Launcher" -> "RowboPERF" -> "3D" -> "Chameleon" to view 3D demo.
Select "RowboPERF" -> "RowboatBench" -> "2D Tests" -> "Run" to view 2D demo.
Select "RowboPERF" -> "0xBenchmark" -> "2D" -> "Run" to view 2D demo.
Browser Experience
Ethernet Configuration
Ethernet is configured by default for DHCP. Use below command to verify Ethernet configuration
# netcfg
e.g.
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 UP 172.24.191.26/22 0x00001043 96:cd:df:8b:c6:2b
Select Ethernet configuration. Here you can enable/disable ethernet and perform any additional configuration.
# setprop debug.video.showfps 1
# setprop debug.video.showfps 0
Wireless
AM335x EVM supports Wi-Fi and Bluetooth on Android.
Enabling Wi-Fi
Connect to desired AP by clicking on its name and enter required details (username/key etc) and click Connect
when successfully connected, you will see status as connected under the respective AP name
Disabling Wi-Fi
To turn off Wi-Fi, browse to "App Launcher" -> "Settings" -> "Wi-Fi".
Disable Wi-Fi by sliding the ON/OFF tab to the OFF position.
Following message appears on console and the Wi-Fi status is shown as OFF.
To turn on Wi-Fi hotspot, browse to "App Launcher" -> "Settings" -> "More..." -> "Portable hotspot"
Note: Do not enable Wi-Fi Hotspot before configuring the settings. Changing the settings after enabling Wi-Fi hotspot may result in hotspot malfunction
Click the checkbox next to "Portable Wi-Fi hotspot" to start hotspot. You will see the message "Tethering or hotspot active" in the notification bar once the hotspot is fully functional.
The following screenshot shows the hotspot being detected from another evm.
Note: Tethering with another network interface like ethernet is not currently supported in this DevKit release
Wi-Fi Direct
TI-Android-ICS-4.0.3-DevKit-3.0.1 supports Wi-Fi Direct with TI WL1271 Wireless module.
To turn on Wi-Fi direct, browse to "App Launcher" -> "Settings" -> "More..."
Click checkbox next to "Wi-Fi direct".
After Wi-Fi direct is enabled, click "Wi-Fi direct: Set up peer-to-peer connections". This window shows any nearby devices with Wi-Fi direct enabled.
Note: Wi-Fi station mode or SoftAP/hotspot mode, if enabled, shall be disabled when Wi-Fi direct is active. The earlier state is restored when Wi-Fi direct is
disabled
Note: Ensure that Wi-Fi (STA mode), hotspot (SoftAP) or Wi-Fi direct is not enabled when you are changing the MAC address
To change the MAC address, perform the following on the serial console of device:
You need to reboot the board after changing the MAC address.
Bluetooth
Enabling Bluetooth
Note: When pairing with Bluetooth headset, pin may not be displayed. Android attempts to pair automatically with Bluetooth headsets. Pin dialog will be shown
only if auto-pairing fails.
Disabling Bluetooth
To turn off Bluetooth, browse to "App Launcher" -> "Settings" -> "Bluetooth".
Disable Bluetooth by sliding the ON/OFF tab to the OFF position.
Sending files
Note: 'Share using Bluetooth' is not enabled by default in the Gallery app. You need to install a third party application like BlueFTP to enable the sharing option. Follow the instructions from
http://www.medieval.it/blueftp-android/menu-id-68.html to download BlueFTP
Receiving files
On paired device (e.g. phone), select send via Bluetooth, click on AM335XEVM.
On evm, notification appears about incoming connection.
Open the task bar and select "Bluetooth share: Incoming file".
A pop up appears asking for confirmation. On popup click Accept.
Bluetooth A2DP
You can listen to Media audio on Bluetooth A2DP headset.
Pair A2DP capable bluetooth headset with device. Android uses the stereo headset icon to denote A2DP headset.
After pairing succeeds, the status is updated to 'Connected'.
Open Music player and play any audio clip.
Audio will be heard on the Bluetooth headset.
Bluetooth HID
You can connect to Bluetooth keyboard or mouse.
Bluetooth Keyboard
Pair with the Bluetooth keyboard, by providing the suitable pass-code from the keyboard matching to the code shown on the device.
After the successful pairing of the keyboard with the device, the keyboard will be listed under the paired devices category.
The supported functionality of the paired keyboard can be used on the device.
For disconnecting the keyboard from the device, select the keyboard under paired devices category, and agree to disconnect message.
Bluetooth Mouse
Pair with the Bluetooth mouse, by providing the suitable pass-code from the device, matching to the supported code of the mouse.
After the successful pairing of the mouse with the device, the mouse will be listed under the paired devices category.
The supported functionality of the paired mouse can be used on the device.
For disconnecting the mouse from the device, select the mouse under paired devices category, and agree to the disconnect message.
Bluetooth AVRCP
You can control Media playback with Media player keys on Bluetooth headset with AVRCP capabilities.
NOTE: The following steps assume Bluetooth A2DP headset with AVRCP.
Open Music Player and go to playlist view. Check that there are multiple clips in the playlist.
Press the Play/Pause button on the BT headset - The currently queued clip begins playing on the headset.
Press the Play/Pause button again on the headset - The currently playing clip is paused.
Press the Next button on the headset; the next clip in the playlist begins to play on the headset.
Press the Prev button on the headset; the currently playing clip restarts from the beginning.
Accelerometer Sensor
TI Android ICS 4.0.3 DevKit 3.0.1 supports the accelerometer sensor on AM335x EVM.
Auto-rotate screen
Amazed Application
Launch the Amazed application by browsing to the "App Launcher" -> "Amazed".
The game starts. Tap the screen to begin.
Hold the device in different orientation to move the ball to the destination and hence test the accelerometer.
Light Sensor
TI Android ICS 4.0.3 DevKit 3.0.1 supports the light sensor on AM335x EVM.
Auto Brightness
Temperature Sensor
TI Android ICS 4.0.3 DevKit 3.0.1 supports the temperature sensor on AM335x EVM.
Temperature Widget
Note: The Suspend to memory feature can not be demonstrated on BeagleBone with DVI-D cape or BeagleBone without any cape. This is because there is no input key/device connected to
wakeup domain on these devices
BackLight Control
A PM feature to automatically increase / decrease frequency and drop voltage based on CPU usage.
There are four different governors which can be used to control this feature, namely ondemand, performance, powersave and userspace governors.
CPU Idle States
There are two deeper power states introduced by CPU Idle namely Wait for interrupt,WFI and DDR Self Refresh.
Basic Settings
Enable PM
By default we have disabled PM with the setting "setprop hw.nopm true" in init.rc.
Replace the line with "setprop hw.nopm false" to enable suspend/resume features.
Remove the selection "App Launcher" -> "Settings" -> "Developer options" -> "Stay awake" if selected already.
To go in suspend mode
Press POWER (SW5) key on the keypad or wait for screen time out.
Select "App Launcher" -> "Settings" -> "Developer options" -> "Stay awake"
Select "App Launcher" -> "Settings" -> "Display" -> "Brightness" > "Automatic brightness"
Advanced Settings
To Disable Power Management
#cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Application can select any of the available frequency from the above
#cat /sys/devices/system/cpu/cpu0/cpuidle/state*/time
#cat /sys/devices/system/cpu/cpu0/cpuidle/state*/usage
To minimize the power consumption in runtime
The maximum power reduction in runtime is achieved when dvfs option is set to “power save”.
Limitations
If "ondemand" governor enabled for Cpu Freq (a PM feature to automatically increase / decrease frequency and drop voltage based on CPU usage), then the system may hang anytime after
boot-up
The following messages are observed before crash.
platform mpu.0: omap_target: unable to set voltage to 1260000 uV (for 720 MHz)
Alarm to wake up the device from suspend will not work since there is no Real Time Clock functional when the device is put into suspend.
To wake the device from suspend, the user need to tap the touch the screen a little longer (2 seconds) or need to press the Volume keys hard.
System never enter "WFI and DDR Self Refresh" cpu idle state since display is always active and preventing this state to enter in runtime.
Some of the beagle bones are not resuming after they have been put in to suspend.
In BeagleBone with LCD cape, the keypad is not connected to the wake up domain. So wake up is not possible by pressing keys.
$ mkdir /home/workdir/Android_nfs
$ cd /home/workdir/Android_nfs
$ tar -xjvf ~/rootfs.tar.bz2
Change the permission of target rootfs else it will give permission denied errors
/home/workdir/Android_nfs *(rw,sync,no_subtree_check,no_root_squash)
Run exportfs command
$ sudo exportfs -a
AM335x:
setenv bootargs 'console=ttyO0,115200n8 androidboot.console=ttyO0 mem=256M root=/dev/nfs nfsroot=<server-ip>:/home/workdir/Android_nfs rw rootwait init=/init ip=dhcp'
Beaglebone:
setenv bootargs 'console=ttyO0,115200n8 androidboot.console=ttyO0 mem=256M root=/dev/nfs nfsroot=<server-ip>:/home/workdir/Android_nfs rw rootwait init=/init ip=dhcp'
NAND Booting
The tree structure for uncompressed pre-built image directory should be as:
AM335xEVM_UBIFS
|-- START_HERE
|-- Boot_Images
| |-- MLO
| |-- u-boot.img
| |-- uEnv.txt
| |-- boot.scr
| `-- uImage
|-- Filesystem
| `-- ubi.img
|-- Media_Clips
| |-- Audio
| |-- Images
| `-- Video
|-- README.txt
`-- mkmmc-android-ubifs.sh
Switch 1 2 3 4 5 6 7 8
State ON OFF ON ON OFF ON ON ON
Setup on Device
$ cd $ANDROID_ROOT/out/host/linux-x86/bin
Proceed installing, with the difference that device to be selected is "Android Bootloader Interface" instead of "Android ADB Interface".
Important extract with sudo permissions, otherwise you may face issues with booting of Android.
Download and build mtd-utils. For more information on mtd-utils, follow the link: http://processors.wiki.ti.com/index.php/MTD_Utilities
Create/Edit ubinize.cfg:
$ vim ubinize.cfg
[ubifs]
mode=ubi
image=ubifs.img
vol_id=0
vol_size=192MiB
vol_type=dynamic
vol_name=rootfs
vol_flags=autoresize
Fastboot commands
$ export ANDROID_ROOT=<rowboat_top_level_build_directory>
$ cd $ANDROID_ROOT/out/host/linux-x86/bin
Update xloader:
Updating u-boot:
Updating kernel:
Updating filesystem:
Erasing partition:
$ sudo ./fastboot
resuming boot...
OKAY [ 0.001s]
finished. total time: 0.001s continue
# setenv bootargs 'console=ttyO0,115200n8 androidboot.console=ttyO0 mem=256M root=ubi0:rootfs rootfstype=ubifs ubi.mtd=7,2048 rw rootwait init=/init ip=off'
For example the boot arguments for the AM335x EVM, will look like:
# setenv nandboot 'echo Booting from nand ... ; nandecc hw 2 ; nand read 0x81000000 0x00280000 0x00500000 ; bootm 0x81000000;'
# setenv bootcmd 'run nandboot'
# setenv bootargs 'console=ttyO0,115200n8 androidboot.console=ttyO0 mem=256M root=ubi0:rootfs rootfstype=ubifs ubi.mtd=7,2048 rw rootwait init=/init ip=off'
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
.
|-- SDK Readme.txt
|-- add-ons
|-- google-market_licensing
|-- platform-tools
| |-- NOTICE.txt
| |-- aapt
| |-- adb
| |-- aidl
| |-- dexdump
| |-- dx
| |-- lib
| `-- source.properties
|-- platforms
|-- temp
`-- tools
|-- NOTICE.txt
|-- adb_has_moved.txt
|-- android
|-- ant
|-- apkbuilder
|-- ddms
|-- dmtracedump
|-- draw9patch
|-- emulator
|-- etc1tool
|-- hierarchyviewer
|-- hprof-conv
|-- layoutopt
|-- lib
|-- mksdcard
|-- monkeyrunner
|-- proguard
|-- source.properties
|-- sqlite3
|-- traceview
`-- zipalign
The adb tool is located in paltform-tools/ directory under the Android SDK installation. Export the platform-tools and tools directory path as shown below.
$ export PATH=<android_sdk_path>/platform-tools/:<android_sdk_path>/tools/:$PATH
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)-
Execute the following to change the user mode for the rules file.
$ adb devices
If device is connected, then output on screen should list the device, example:
Make sure Ethernet port on board and host machine are connected to the network
Check Ethernet configuration for the board
# netcfg
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
eth0 UP 172.24.191.26/22 0x00001043 96:cd:df:8b:c6:2b
If Ethernet was not configured, ensure that Ethernet is enabled and configured correctly in Android Settings and reboot. See Ethernet Configuration section for more details.
Configure the ADB Daemon on target to use an Ethernet connection using setprop as shown below.
If network is configured successfully (above steps) then Restart service adbd on the target,
# stop adbd
# start adbd
$ adb devices
$ adb shell
For more information about adb commands, see Android Debug Bridge page at Android ADB
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.
Edit (or create and then edit if it doesn't already exist) file in
"%USERPROFILE%\.android\adb_usb.ini":
;TI EVM
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D002
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D002&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).
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:
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.
From the host: You can use adb tool for package installation.
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.
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.
Copy any files to and from the board over ADB
Using the adb commands "pull" and "push" 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.
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
Pre-requisites
Refer to Google CTS Guide for information on setting up the host and android device for CTS testing.
Setup an ADB connection between Host and platform as mentioned in ADB section above.
Launch the CTS.
android-cts$ ./tools/cts-tradefed
On CTS prompt check the available plans
Once all the tests are executed, the results can be browsed in an browser by opening [android-cts/repository/results/<session-name>/testResult.xml] and use the results to adjust your design.
Note: Sometimes when CTS is restarting the board, adb connection to CTS, may not happen automatically. In that case, execute the following command on the
console, soon after the board has restarted.
# stop adbd;sleep 1;start adbd;
TI provides Android sources for all the supported devices in multiple locations, developers can download the sources from the rowboat repository or use the pre-packaged repo in the DevKit TI-
Android-ICS-4.0.3_AM335x_3.0.1.bin.
SD Card Recommendations
Some brands or models of SD cards are observed with poor performance on AM335x platforms. The symptom could be one or some of the followings.
the boot-up time is much longer than normal (3x of normal or even longer);
the reaction of UI operations is unacceptably delayed;
the Gallery app cannot find the media files to create the albums;
the video playback is sluggish.
The table below lists the SD cards tested which have no issue on performance.
Sony SD 4 2GB
The table below lists the SD cards tested which have poor performance.
Versioning
This release is available from http://software-dl.ti.com/dsps/dsps_public_sw/sdo_tii/TI_Android_DevKit/TI_Android_ICS_4_0_3_DevKit_3_0_1/index_FDS.html
The release notes is available at http://processors.wiki.ti.com/index.php/TI-Android-ICS-4.0.3-DevKit-3.0.1_ReleaseNotes
Navigation menu
Personal tools
Log in
Request account
Namespaces
Page
Discussion
Variants
Views
Read
View source
View history
More
Search
Search Texas Instruments Search Go
Navigation
Main Page
All pages
All categories
Recent changes
Random page
Help
Toolbox
What links here
Related changes
Special pages
Printable version
Permanent link
Page information
Privacy policy
About Texas Instruments Wiki
Disclaimers
Terms of Use