游聚玩不了求大神告知解决方法
急急急_游聚吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0可签7级以上的吧50个
本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：1,886贴子：
游聚玩不了求大神告知解决方法
我是英文，装了绿色游聚和全套roms（包括pgm和neogeo）到解压后的根目录下。进入游聚平台没有问题，除了出现一个错误提示“it's not a valid GUP input xml”, 推测是gup.xml格式有误，虽然不知道什么地方有问题，但仍然可以进入。然后游戏还需要下载 点下载出现乱码！！
求解决办法
熬了两个通宵两个狐狸复...
进入游戏，选完英雄（...
懂的大神知个招
RT 从昨天就会了 一直显...
第一次玩这类游戏
拜托大大们了
去论坛问吧 这里大神太少---------------------只要是活着的东西，就算是神也杀给你看！我出去杀人了 但没找到合适的对象只要有你在，只要有你微笑，那就是幸福。明明感到不安，却可以安心。只要是有你在，光是并肩走路我都觉得高兴。 我并不是那样拥有良知的优秀之人，放任我这样的家伙在没关系吗？是吗，那就没办发啦，式的罪就由我来代替你背负吧。我不是想杀你，只是不能容忍你的存在。我唯独无法忍受的就是堕入那样的黑暗。总有一天我们能站在同样的地方。我一直希望有人能这样跟我说。这样你就跑不掉了。我要杀掉软弱的自己，才不会把两仪式交给你这种东西。人一生只能背负一个人的死原来我所以来的东西并没有我原本以为的那么糟糕，这让我有一点高兴 很小一点 只有很小一点。
内&&容:使用签名档&&
保存至快速回贴c# - The input is not a valid Base-64 string as it contains a non-base 64 character - Stack Overflow
to customize your list.
Stack Overflow is a community of 4.7 million programmers, just like you, helping each other.
J it only takes a minute:
Join the Stack Overflow community to:
Ask programming questions
Answer and help your peers
Get recognized for your expertise
I have a REST service that reads a file and sends it to another console application after converting it to Byte array and then to Base64 string. This part happens correct but when the same stream is received at the application, it gets manipulated and is no more a valid Base64 string. Some junk characters are getting introduced into the stream.
The exception that i get while converting the stream back to Byte is “The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or a non-white space character among the padding characters”.
At Service:
[WebGet(UriTemplate = "ReadFile/Convert", ResponseFormat = WebMessageFormat.Json)]
public string ExportToExcel()
string filetoexport = "D:\\SomeFile.xls";
byte[] data = File.ReadAllBytes(filetoexport);
var s = Convert.ToBase64String(data);
At Application:
var client = new RestClient("http://localhost:56877/User/");
var request = new RestRequest("ReadFile/Convert", RestSharp.Method.GET);
request.AddHeader("Accept", "application/Json");
request.AddHeader("Content-Type", "application/Json");
request.OnBeforeDeserialization = resp =& {resp.ContentType =
"application/Json";};
var result = client.Execute(request);
byte[] d = Convert.FromBase64String(result.Content);
Very possibly it's getting converted to a modified Base64, where the + and / characters are changed to - and _. See
If that's the case, you need to change it back:
string converted = base64String.Replace('-', '+');
converted = converted.Replace('_', '/');
81.4k778169
to create my base64 encoding.
But it puts some header information at the top:
imageCode = "data:image/base64,iVBORw0KGgoAAAANSUhEUgAAAMgAAABkC...
Which cause the above error.
Just remove everything infront of and including the first comma, and you good to go.
imageCode = "iVBORw0KGgoAAAANSUhEUgAAAMgAAABkC...
I arranged a similar context as you described and I faced the same error. I managed to get it working by removing the " from the beginning and the end of the content and by replacing
\/ with /.
Here is the code snippet:
var result = client.Execute(request);
var response = result.Content
.Substring(1, result.Content.Length - 2)
.Replace(@"\/","/");
byte[] d = Convert.FromBase64String(response);
As an alternative, you might consider using XML for the response format:
[WebGet(UriTemplate = "ReadFile/Convert", ResponseFormat = WebMessageFormat.Xml)]
public string ExportToExcel() { //... }
On the client side:
request.AddHeader("Accept", "application/xml");
request.AddHeader("Content-Type", "application/xml");
request.OnBeforeDeserialization = resp =& { resp.ContentType = "application/xml"; };
var result = client.Execute(request);
var doc = new System.Xml.XmlDocument();
doc.LoadXml(result.Content);
var xml = doc.InnerT
byte[] d = Convert.FromBase64String(xml);
18.4k12545
Since you're returning a string as JSON, that string will include the opening and closing quotes in the raw response. So your response should probably look like:
"abc123XYZ=="
or whatever...You can try confirming this with Fiddler.
My guess is that the result.Content is the raw string, including the quotes. If that's the case, then result.Content will need to be deserialized before you can use it.
22.2k43880
Your Answer
Sign up or
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Post as a guest
By posting your answer, you agree to the
Not the answer you're looking for?
Browse other questions tagged
Upcoming Events
Top questions and answers
Important announcements
Unanswered questions
By subscribing, you agree to the
Stack Overflow works best with JavaScript enabledFrom Texas Instruments Wiki
User Guide - March 31, 2011
This document describes how to install and work with Texas Instruments' Android GingerBread DevKit release for OMAP35x, AM37x, DM37x, AM35x platforms running Android. This release package provides a stable Android distribution with integrated SGX (3D graphics) drivers, TI hardware abstraction for video overlay, multimedia DSP acceleration (on DM37x only), and standard applications from Android. The package also includes Linux Android kernel, tools and documentation to ease development, deployment and execution of Android based systems. The product forms the basis for all Android application development on OMAP35x, AM37x, DM37x, AM35x platforms. In this context, the document contains instructions to:
Install the release
Setting up the hardware
Steps to use pre-built binaries in the package
Running Android on the supported platforms
Setting up the Android debugger “adb” with the hardware platform
Installing and executing Android (out of market) applications hardware platforms
This section describes the list of Software and Hardware requirements to evaluate the DevKit release.
This release of TI Android GingerBread 2.3 DevKit 1.0 is evaluated on the below given list of platforms. This package should be easily portable on other platforms on similar TI devices.
Platform Supported
Other Accessories
DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)
DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)
DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)
DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)
DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min)
(1GHz for 720P video decoding)
DVI Monitor, USB HUB, USB Keyboard, USB Mouse, Ethernet, UART Cable, Audio Speakers, MMC/SD Card (2GB min, Class4 min for 720P video decoding)
If you are a Android application developer or would like to use Android SDK Tools then refer to
for Host PC requirements.
To evaluate this release we recommend you to have a Linux "Ubuntu 8.04 or above" Host machine, See
TI_Android_GingerBread_2_3_DevKit_1_0
|-- Android_Source_Manifest
|-- TI-Android-GingerBread-2.3-DevKit-1.0.xml
`-- TI-Android-GingerBread-DSP-2.3-DevKit-1.0.xml
|-- Documents
|-- RowboPERF_User_Guide.pdf
|-- Software_Manifests
|-- Test_Performance_Results
|-- CTS_Report.tar.gz
|-- Performance_Results.pdf
`-- Test_Results.pdf
|-- TI-Android-GingerBread-2.3-DevKit-1.0_ReleaseNotes.pdf
|-- TI-Android-GingerBread-2.3-DevKit-1.0_UserGuide.pdf
`-- TI-Android-GingerBread-2.3-DevKit-1.0_DeveloperGuide.pdf
|-- Performance_Apps
|-- 0xbench
|-- Launcher2
|-- rowboatBench
|-- RowboPERF
`-- StorageIO
|-- Prebuilt_Images
|-- beagleboard-rev-c4
|-- beagleboard-xM
`-- OMAP35X
|-- flash-utility.tar.gz
|-- mk-bootscr
|-- mk-mmc
|-- pinmux-utility.tar.gz
|-- signGP
`-- Wireless
`-- WL1271Android-patches.tar.gz
This section gives the instructions to quickly prepare an SD Card image and get an experience of TI Android GingerBread 2.3 DevKit 1.0 on TI platforms/devices.
Download the pre-built Image from
for the platform you own, can be AM35x EVM, AM37x EVM, DM37x EVM, Beagleboard Rev C4/XM, OMAP35x EVM.
Get an SD Card of minimum size 2GBytes (Class4 minimum) and a USB Card reader
Insert the USB SD Card reader (with SD Card) in your host Linux PC
Prepare the MMC/SD card Image
tar -xzvf &Board name&.tar.gz
cd &Board name&
sudo ./mkmmc-android /dev/sd&device&
The above step prepares the SD Card.
Setup the board/platform
Do the DIP switch settings to boot from SD Card, see the section on DIP switch setting below.
Insert the 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
#& mmc init
#& fatload mmc 0 0x boot.scr
#& source 0x
Click on the TI logo and run the apps you are interested in, look at the RowboPerf user guide for more details about this app .
Booting Android on any TI platform requires following software components
Kernel Image (uImage)
Bootloader (u-boot.bin)
Bootstrapping (x-load.bin.ift for NAND or MLO for MMC)
Filesystem (rootfs)
The above listed software components or images can be populated by
Building sources from this package
Using the pre-built images in this package
This section describes the procedure to compile and integrate all the required software components to boot Android on TI platforms.
Download the tool chain and export it in the default Linux Path. The ARM tool chain can be downloaded from Android pre-built repository.
#& export PATH=&tool chain install path&/linux-x86/toolchain/arm-eabi-4.4.0/bin/:$PATH
Untar the kernel source located in the sources directory
#& tar -xzvf Android_Linux_Kernel_2_6_32.tar.gz
Execute the following commands to the kernel sources
#& make ARCH=arm CROSS_COMPILE=arm-eabi- distclean
#& make ARCH=arm CROSS_COMPILE=arm-eabi- &default config&
Where default config is
omap3_evm_android_defconfig
 : For OMAP35x, AM37x, DM37x EVM
am3517_evm_android_defconfig
 : For AM35x EVM
omap3_beagle_android_defconfig
 : For Beagleboard Rev Cx, XM
#& make ARCH=arm CROSS_COMPILE=arm-eabi- uImage
This command will build the Linux Kernel Image in arch/arm/boot "uImage"
Untar the u-boot sources located in the sources directory
#& tar -xzvf u-boot.tar.gz
Execute the following commands to the kernel sources
#& make CROSS_COMPILE=arm-eabi- distclean
#& make CROSS_COMPILE=arm-eabi- &default config&
Where default config is
omap3_evm_config
 : For OMAP35x, AM37x EVM, AM37x EVM
am3517_evm_config
 : For AM35x EVM
omap3_beagle_config
 : For Beagleboard Rev Cx, XM
#& make CROSS_COMPILE=arm-eabi-
This command will build the u-boot Image "u-boot.bin"
Untar the x-loader sources located in the sources directory
#& tar -xzvf x-loader-03.00.02.07.tar.gz
Execute the following commands to the kernel sources
#& make CROSS_COMPILE=arm-eabi- distclean
#& make CROSS_COMPILE=arm-eabi- &default config&
Where default config is
omap3evm_config
 : For OMAP35x, AM37x EVM, DM37x EVM
am3517evm_config
 : For AM35x EVM
omap3beagle_config
 : For Beagleboard Rev Cx, XM
#& make CROSS_COMPILE=arm-eabi-
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 directory of the Devkit.
#& ./signGP ./x-load.bin
The signGP tool will create a .ift file, that can be renamed to MLO.
- The Pre-built images are provided in this package to help users boot android without building the sources
This DevKit release supports six different platforms, OMAP35x EVM, AM37x EVM, DM37x EVM, AM35x EVM, Beagleboard Rev Cx, Beagleboard XM. While they are different devices the hardware setup will almost remain the same.
Connect the UART port of the platform to the Host PC and have a Terminal software like TeraTerm, Minicom or Hyperterminal.
Connect the Ethernet (on Beagle Rev C4 we don't have an Ethernet port)
Connect Audio Speakers
For Beagle board you need to connect DVI Monitor through HDMI connector.
Use self powered USB HUB and connect it to USB Host port of the platform, mainly for Beagle and AM35x EVM. For AM37x, DM37x, and OMAP35x EVM the onboard keypad can be used
Connect USB keyboard and USB Mouse to the USB HUB for use with Beagle or EVM
- Beagleboard have no keypad mappings, user is recommended to use USB Keyboard over a self powered USB HUB connected to the Host port of Beagleboard.
Select Appropriate DIP Switch settings on EVM(s) to boot over MMC/SD
For MMC/SD boot - On OMAP35x, DM37x and AM37x EVM the DIP switch SW4 should be set as shown below
For MMC/SD boot - On AM35x EVM the DIP switch S7 should be set as shown below
TI platforms (Beagle or EVM) can be booted over MMC or NAND or UART. We follow and prefer MMC based booting of platforms.
Use the mk-mmc utility provided in the tools folder of this package to populate the SD Card. This utility helps users create a MMC/SD Card with required Images to boot Android on any given TI platform.
This will partition the SD card to three partitions namely boot, rootfs and data. 1) The boot partition will get populated with the images required for booting. 2) The rootfs partition will be used as android root filesystem partition. 3) The Media inside the folder Media_Clips will get copied to the data partition. The data partition will get mounted as EXTERNAL storage when Android boots up.
Execute the following command
#&./mkmmc-android /dev/sdc MLO u-boot.bin uImage boot.scr rootfs.tar.bz2 Media_Clips
This populates the SD/MMC card with all the images.
To create the boot.scr boot script use the mkbootscr tool found in the Tools directory provided in the DevKit.
If you want to use the pre built images in the DevKit you have to adjust the above mentioned command to take them into account, as a more direct example the commands below will generate a SD card for an OMAP3 EVM. Ensure you have your SD card connected to the Linux machine you are using and that it is in /dev/sdb for this command otherwise adjust the command accordingly (WARNING: if you get this wrong it can wipe your HDD). Note that this assumes you installed the SDK in your home (~) directory and that the command is run with sudo (or your preferred way of getting super user privileges) to allow for the reformatting of the SD card.
HOST $ cd ~/TI_Android_GingerBread_2_3_DevKit_1_0/OMAP35X
HOST $ sudo ../../Tools/mk-mmc/mkmmc-android.sh /dev/sdb
To play media after booting Android on any platform, the content must be included in the MMC/SD card's FAT32 partition. If you use the mk-mmc script included in the release package then it creates 3 partitions. The media content should be placed into the 3rd (FAT32) partition.
#& sudo mount /dev/sdd3 /mnt
#& sudo cp &all media files& /mnt
#& sudo umount /mnt
- This release supports all the standard Android media formats, listed here
Booting over MMC using boot.scr
- If the board has bootargs configured already, then the board will not boot for Android automatically,
- It is suggested to either delete the bootargs or use the following commands on u-boot prompt through UART console.
#& mmc init
#& fatload mmc 0 0x boot.scr
#& source 0x
If the board is not configured for bootargs, then it automatically boots.
On DM37x EVM, by default, the display is configured to the on-board LCD panel and the 720P video playback will be cropped. To watch the full size 720P video, run the instructions below in the serial console to switch the display to the DVI port.
# dispsw -c
Running the commands above again will switch back display to the LCD panel.
Boot arguments for various boards are as follows.
setenv bootargs 'console=ttyS2, androidboot.console=ttyS2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=600 omap_vout.vid1_static_vrfb_alloc=y'
setenv bootargs 'console=ttyS0, androidboot.console=ttyS0 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=1000 omap_vout.vid1_static_vrfb_alloc=y'
display on LCD:
setenv bootargs 'mem=76M@0x mem=128M@0x console=tty0 console=ttyS0, androidboot.console=ttyS0 root=/dev/mmcblk0p2 rw rootfstype=ext3 init=/init rootwait ip=off omap_vout.vid1_static_vrfb_alloc=y omap_vout.video2_numbuffers=0 mpurate=1000'
display on DVI:
setenv bootargs 'mem=76M@0x mem=128M@0x console=tty0 console=ttyS0, androidboot.console=ttyS0 root=/dev/mmcblk0p2 rw rootfstype=ext3 init=/init rootwait ip=off omap_vout.vid1_static_vrfb_alloc=y omap_vout.video2_numbuffers=0 omapdss.def_disp=dvi omapfb.mode=dvi:MR-16 mpurate=1000'
Beagleboard-rev-c4:
setenv bootargs 'console=ttyS2, androidboot.console=ttyS2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=720 omap_vout.vid1_static_vrfb_alloc=y'
Beagleboard-xm:
setenv bootargs 'console=ttyS2, androidboot.console=ttyS2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=1000 omap_vout.vid1_static_vrfb_alloc=y'
OMAP35XEVM:
setenv bootargs 'console=ttyS0, androidboot.console=ttyS0 mem=128M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=720 omap_vout.vid1_static_vrfb_alloc=y'
The below table lists the keypad and USB Keyboard mappings to Android UI functionality.
Functionality
USB Keyboard/Mouse
Keypad on OMAP35x/AM37x EVM
Keypad on AM35x EVM
Home Screen
Left Arrow
Right Arrow
Down Arrow
Volume Down
Volume Down
Mouse right
Android filesystem can be mounted over network, the bootargs for doing the same should include below text instead of MMC
ip=dhcp rw root=/dev/nfs nfsroot=&your NFS server ipaddr&:/home/USER/FILESYSTEM_DIR,nolock noinitrd
Example: Complete bootargs for OMAP35x board using NFS and LCD output
setenv bootargs init=/init console=ttyS0, ip=dhcp rw root=/dev/nfs nfsroot=192.168.133.01:/home/user/targetfs,nolock mem=256M noinitrd androidboot.console=ttyS0
Android boot images x-loader and u-boot etc can be flashed to NAND from windows host, using flashing utility provided in tools.
Flashing utility is tested on USB connection with AM37X Pre-built images. For instructions on flashing utility please refer the steps at .
In some cases the flashing utility's recommended settings of HWECC, 4-bit for flashing Uboot and the kernel image may not work and the board displays a bad CRC message. If this happens re-flash the components again using the SWECC setting of the utility for Uboot and kernel.
On OMAP35x, AM37x, DM37x and AM35x EVMs the on board LCD is used as output device by default. User is allowed to configure DVI port as output device, by changing the boot arguments as shown below.
Append the boot arguments with following text
omapfb.mode=dvi:MR-16 omapdss.def_disp="dvi"
To boot over MMC and use DVI at resolution
on OMAP35x EVM, the complete bootargs would be,
setenv bootargs init=/init console=ttyS0, ip=dhcp rw root=/dev/mmcblk0p2 rw init=/init rootwait mem=256M androidboot.console=ttyS0 omapfb.mode=dvi:MR-16 omapdss.def_disp="dvi"
We have noticed on few monitors the below bootargs works for DVI.
setenv bootargs console=ttyS0, androidboot.console=ttyS0 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=1000 omap_vout.vid1_static_vrfb_alloc=y vram=16M omapfb.vram=0:8M,1:4M,2:4M omapfb.mode=dvi:hd720 omapdss.def_disp=dvi
- On beagleboard the DVI port is configured as default output device.
On OMAP35x, AM37x and AM35x EVMs the on board LCD is used as output device by default. User is allowed to configure S-video port as output device, by changing the boot arguments as shown below.
Append the boot arguments with following text
omapdss.def_disp="tv"
To boot over MMC and use S-video port as output device on OMAP35x EVM, the complete bootargs would be,
setenv bootargs 'console=ttyS0, androidboot.console=ttyS0 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=720 omap_vout.vid1_static_vrfb_alloc=y omapdss.def_disp="tv"'
Boot the device with LCD as default output device.
To boot over MMC and use lcd as output device on OMAP35x EVM, the complete bootargs would be,
setenv bootargs 'console=ttyS0, androidboot.console=ttyS0 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off mpurate=720 omap_vout.vid1_static_vrfb_alloc=y'
Use the following procedure to display video on s-video device.
Disable overlay1. Before changing any overlay attributes, it should first be disabled.
#echo 0 & /sys/devices/platform/omapdss/overlay1/
Reset overlay1 manager which is set to lcd by default
#echo "" & /sys/devices/platform/omapdss/overlay1/
Disable display1/tv
#echo 0 & /sys/devices/platform/omapdss/display1/
Set overlay manager to tv
#echo "tv" & /sys/devices/platform/omapdss/overlay1/
Enable display1/tv
#echo 1 & /sys/devices/platform/omapdss/display1/enabled
Open gallery application and play video. Video will be played on s-video device and graphics will be displayed on the lcd.
Use the following procedure to display video on lcd device.
Disable overlay1. Before changing any overlay attributes, it should first be disabled.
#echo 0 & /sys/devices/platform/omapdss/overlay1/
Disable display1/tv
#echo 0 & /sys/devices/platform/omapdss/display1/
Disable display0/lcd
#echo 0 & /sys/devices/platform/omapdss/display0/
Reset overlay1 manager which is previously set to tv
#echo "" & /sys/devices/platform/omapdss/overlay1/
Set overlay manager to lcd
#echo "lcd" & /sys/devices/platform/omapdss/overlay1/
Enable display0/lcd
#echo 1 & /sys/devices/platform/omapdss/display0/enabled
Open gallery application and play video. Video and graphics will be displayed on the lcd.
Graphics and Video rotation is managed by software.
Use standard android API to rotate screen in portrait or landscape mode.
Currently portrait and landscape graphics rotation mode is supported.
Ti Android GingerBread 2.3 Devkit 1.0 supports camera sensor (mt9v113) for beagleboard-xm.
Mt9v113.jpeg
Feature supported:
Image Capture
Go to application/activity view luncher & open camera
Click on camera capture.By default images will get stored at - /sdcard/DCIM
Video recording
Go to application/activity view luncher & open camera
Press 'F1' to switch to video recording view
Press 'Enter' to start/stop video recording
Note : All recording will be done using default stagefright encoders.
Format : .3gpp
Video Encoder : H.263
Audio Encoder : AMR
AM37x evm revG with the wireless module supports WLAN and Bluetooth on Android.
For steps on installing the wireless module see .
Menu-&Settings-&Wireless & networks-&Wi-Fi settings
click Wi-Fi and wait for few seconds. The following logs appear on serial console output
TIWLAN: driver init
TIWLAN: 977.211973: wlanDrvIf_Open()
TIWLAN: 977.331480: pInitParams-&RoamingScanning_2_4G_enable 0
SDIO clock Configuration is now set to 24Mhz
TIWLAN: 977.543120: CHIP VERSION... set 1273 chip top registers
TIWLAN: 977.549559: Working on a 1273 PG 2.0 board.
TIWLAN: 977.554228: Starting to process NVS...
TIWLAN: 977.558470: No Nvs, Setting default MAC address
TIWLAN: 977.563444: pHwInit-&uEEPROMCurLen: 1c
TIWLAN: 977.567656: ERROR: If you are not calibating the device, you will soon get errors !!!
TIWLAN: 977.576109: Chip ID is 0x4030111.
TIWLAN: 977.580198: FEM Type 1
TIWLAN: 977.583342: Starting to download firmware...
TIWLAN: 977.665770: Starting to download firmware...
TIWLAN: 977.693602: Starting to download firmware...
TIWLAN: 977.698454: Starting to download firmware...
TIWLAN: 977.710875: Starting to download firmware...
TIWLAN: 977.719420: Starting to download firmware...
TIWLAN: 977.725706: Finished downloading firmware.
TIWLAN: 977.730314: Firmware running.
TIWLAN: 977.749785:
TIWLAN: 977.751707: --------------------------------------------------------------------
TIWLAN: 977.759611: Driver Version  : WiLink_Driver_6.1.0.0.144
TIWLAN: 977.765318: Firmware Version: Rev 6.1.0.0.335
TIWLAN: 977.770170: Station ID
 : 08-00-28-12-34-56
TIWLAN: 977.775145: --------------------------------------------------------------------
TIWLAN: 977.783018:
TIWLAN: 977.799376: Interrogate TX/RX parameters
On the UI, Green check-mark appears and status shows scanning
After scan completes, available APs are listed
connect to desired AP by clicking on its name and enter required details (username/key etc) and click connect
The following appears on console
TIWLAN: : ************ NEW CONNECTION ************
TIWLAN: : -- SSID
TIWLAN: : -- BSSID = xx-xx-xx-xx-xx-xx
TIWLAN: : ****************************************
when successfully connected, you will see status as connected to APNAME
To turn off Wi-Fi, click Wi-Fi in Menu-&Settings-&Wireless & networks
Following message appears on console and the green check mark is not visible on UI
TIWLAN: : wlanDrvIf_Release()
TI WLAN: driver unloaded
NOTE: For information on WLAN calibration refer to
section of Android wireless porting guide.
Menu-&Settings-&Wireless & networks-&Bluetooth settings
Click Bluetooth and wait for few seconds
LED LD3 turns ON on the wireless module and the Bluetooth icon appears on taskbar. The following appears on the debug console
Set BT_EN of WL1271
WL1271: Powering on
If BT is enabled green check-mark appears and status shows scanning
available bt devices are listed
click on desired device to pair with
popup with pin will appear
click Pair button to confirm pairing
verify that the desired device shows the same pin. click ok. devices paired
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.
To turn off Bluetooth, click Bluetooth in Menu-&Settings-&Wireless & networks
LED LD3 turns OFF on the wireless module, Bluetooth icon is not displayed on taskbar and the following messages appear on console:
Set BT_EN of WL1271
WL1271: Powering off
Using Bluetooth, it is possible to send receive files (pictures, media files etc).
go to Menu -&Gallery
Select a picture to share
click Menu (bottom right)
click share, select bluetooth from the options
select paired bt device to send to
the bt device will prompt to accept. accept incoming file
once download finished. check file
on paired device (e.g. phone), select send to bt, click on omap3evm
on evm, notification appears about incoming connection (top left)
open task bar. click on note
in popup click accept
once download complete. check file
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 to phone and media audio'.
Open Music player and play any audio clip
Audio will be heard on the Bluetooth headset
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.
Pair the BT headset
The following text appears on the debug serial when the pairing is successfully completed. This confirms that AVRCP feature is registered with android
input: AVRCP as /devices/virtual/input/input3
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 b the next clip in the playlist begins to play on the headset
Press the Prev b the currently playing clip restarts from the begining
Android supports the Bluetooth Headset Profile/HandsFree Profile Audio Gateway (HSP/HFP AG). Bluetooth SCO connection is used to play/capture audio in these profiles.
It is possible to record audio from Bluetooth headset over SCO.
Pair Bluetooth headset with device
After pairing succeeds, the status is updated to 'Connected to phone audio'. If using A2DP headset, the status is 'Connected to media and phone audio'
Menu -& BluetoothSCOApp. BluetoothSCOApp is a sample app to establish SCO connectivity with a Bluetooth headset
Tap once so that check mark appears against 'Enable Music via Media Player'
NOTE: If using A2DP headset, you need to disable the A2DP profile before BluetoothSCOApp can be used. To disable A2DP follow the steps below
Menu -& Settings -& Wireless & networks -& Bluetooth settings
Long tap on the entry for A2DP headset, a menu appears
Tap Options
Uncheck Media. This stops android from using A2DP profile of the headset
To re-enable A2DP, repeat the above steps and check-mark Media
Menu -& Sound Recorder
Tap record button
Speak into the bluetooth headset mic, the VU meter display moves as per the sound. This confirms that audio is being recorded from bluetooth headset
Stop recording and save the clip.
Turn-off and Turn-on the Headset to come out of SCO mode. (This is a limitation of the current version of BluetoothSCOApp)
The audio is recorded in 3gpp format and can be played back by the Music player.
NOTE: The audio from Music player can be heard only over audio jack or A2DP. Headsets supporting only HSP/HFP cannot be used as audio playback device with Music Player or Gallery app. Please see
section in the porting guide for information about using alsa_aplay tool to playback audio over SCO.
Below are the features supported in TI-Android-GingerBread-2.3-DevKit-1.0
AM37X, DM37x, OMAP35X
Change of LCD backlights based on Wake Locks and Screen Timeouts (DIM,OFF)
LCD back light brightness control from Settings Application
Suspending the device to Memory.The device can be suspended in two ways.
Pressing the POWER key on the keypad
Allowing the system go to suspend after a screen timeout
Prevent Suspend based on Wake Locks
System Resume on Key Press 
CPU Dynamic Voltage and Frequency Scaling (ondemand, performance, powersave and userspace governors)
CPU Idle States
Enabling system for hitting retention during idle
Enabling system for hitting OFF
Suspending the device to Memory.The device can be suspended in two ways.
Pressing the POWER key on the keypad
Allowing the system go to suspend after a screen timeout
Prevent Suspend based on Wake Locks
System Resume on Key Press 
Android Early Suspend Feature for frame buffer driver
To go in suspend mode
Press POWER key on the keypad
To resume from suspend mode
Press any button on the key pad
To set the Screen timeout to go suspend
Select Settings-&Display-& Screen Timeout
Select one of the options from the list
To set set the screen always on preventing suspend
Select Settings-& Applications-& Development-& Stay awake
To set Screen brightness
Select Settings-&Display-& Brightness
To Disable Power Management
Edit init.rc file on the root directory.
Set the property hw.nopm to true
This will prevent POWER key suspend
Select Settings-& Applications-& Development-& Stay awake
The above will prevent screen timeout suspend
Enabling system for hitting retention during idle
#echo 1 & /debug/pm_debug/sleep_while_idle
Enabling system for hitting OFF
#echo 1 & /debug/pm_debug/enable_off_mode
By default sleep_while_idle is set to false and enable_off_mode is set to true
CPU Dynamic Voltage Frequency Scaling settings
Enabling ondemand frequency governor
The ondemand governor enables DVFS(frequency/OPP) transitions based on CPU load.
#echo ondemand & /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Enabling performance frequency governor
The performance governor keeps the CPU always at the highest frequency.
#echo performance & /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Enabling powersave frequency governor
The powersave governor keeps the CPU always at the lowest frequency.
#echo powersave & /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Enabling userspace frequency governor
Once this governor is enabled, DVFS( frequency) transitions will be manually triggered by a userspace application by using the CPUfreq sysfs interface
#echo userspace & /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
See all the available operating points
#cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
Application can select any of the available frequency from the above
&Desired Frequancy& & /sys/devices/system/cpu/cpu0/cpufreq/ scaling_setspeed
Checking CPU IDLE states usage
There are seven power states introduced by CPU Idle
The usage and time count for these different states can be checked via
#cat /sys/devices/system/cpu/cpu0/cpuidle/state*/time
#cat /sys/devices/system/cpu/cpu0/cpuidle/state*/usage
In beagle and am35x platforms there is no keypad connected to the wake up domain. So wake up is not possible by pressing keys. So power management is disabled by default in am35x and beagle platforms.
To enable power management in am35x platform, set Settings -& Applications -& Development -& Stay Awake to true. In this case, you can wake up am35x platform like below    Press ENTER on Serial Port console and then press any key on the keypad to wake up the device.
If the usb device connected to the USB EHCI port when suspending the device, it might not work properly after resume.
    So Disconnect any usb device connected to USB EHCI port when suspending the device.
Display starts flashing sometimes, once sleep_while_idle and enable_off_mode both enabled in AM37X.
Fastboot flashing utility is for updating the different software components of Android. Here is a guide to reflash the xloader, u-boot, kernel and root-filesystem (UBIFS image). This guide assume that Rowboat has been compiled before trying out these instructions.
Connect serial port to host PC via null modem cable.
Serial port settings: N1, No flow control.
Apply power to the board.
Press any key in serial port utility during boot and get U-boot command prompt.
Run "fastboot" on u-boot command prompt (u-boot will echo "fastboot initialized").
Connect USB cable between USB OTG port of the board and host PC.
On command prompt, run
$ export ANDROID_ROOT=&rowboat top level directory&
$ cd $ANDROID_ROOT/out/host/linux-x86/bin
$ sudo ./fastboot devices
if a device number is echoed, fastboot is working.
Edit android_winusb.inf - under section [Google.NTx86], add line as below:
 %SingleBootLoaderInterface% = USB_Install, USB\VID_0451
Proceed installing, with the difference that device to be selected is "Android Bootloader Interface" instead of "Android ADB Interface".
Make sure you have all the necessary tools to build the UBI image.
$ sudo apt-get install mtd-utils
Create a self explanatory ubinize.cfg configuration file. For example:
$ cat ubinize.cfg
image=ubifs.img
vol_size=200MiB
vol_type=dynamic
vol_name=rootfs
vol_flags=autoresize
Create a placeholder for the android filesystem. This will be the source for the UBI image
$ mkdir temp
The temp directory can be populated by extracting the tarball of the prebuilt image (*.tar.bz2).
$ tar xvjf &rootfs tarball& --numeric-owner -C temp/
To populate the temp directory with the filesystem created by building from sources
$ cp -r &android_src_top&/out/target/platfrom/&target_product&/root/* temp
$ cp -r &android_src_top&/out/target/platfrom/&target_product&/system temp
Add all the permissions to the filesystem. Android will eventually re-assign the correct/necessary permissions on first boot.
$ chmod -R 777 temp/
Create ubifs.img. Note it will not be the one which will be used for flashing. On Am37x board it will be,
$ sudo mkfs.ubifs -r temp/ -m 2048 -e 129024 -c 1948 -o ubifs.img
Create ubi.img for flashing.
$ ubinize -o ubi.img -m 2048 -p 128KiB -s 512 ubinize.cfg
$ export ANDROID_ROOT=&rowboat_top_level_build_directory&
$ cd $ANDROID_ROOT/out/host/linux-x86/bin
List connected devices
$ sudo ./fastboot devices
Update xloader.
$ sudo ./fastboot flash xloader &xloader_binay_path&/MLO
Updating u-boot.
$ sudo ./fastboot flash bootloader &uboot_binary_path&/u-boot.bin
sending 'bootloader' (203 KB)... OKAY [
writing 'bootloader'... OKAY [
finished. total time: 1.093s
Updating kernel.
$ sudo ./fastboot flash boot &kernel_image_path&/uImage
sending 'boot' (2537 KB)... OKAY [
writing 'boot'... OKAY [
finished. total time: 9.796s
Updating filesystem.
$ sudo ./fastboot flash system &rootfs_image_path&/ubi.img
sending 'system' (72320 KB)... OKAY [183.758s]
writing 'system'... OKAY [ 84.040s]
finished. total time: 267.819s
Erasing partition.
$ sudo ./fastboot erase &partition name& (eg. xloader)
$ sudo ./fastboot reboot
Display fastboot variable
$ sudo ./fastboot getvar &variable&
Exit fastboot mode in uboot
$ sudo ./fastboot continue
Set the bootarguments from u-boot prompt.
# setenv nandboot 'echo Booting from nand ...; nand read ${loadaddr} ${boot_nand_offset} ${boot_nand_size}; bootm ${loadaddr}'
# setenv bootcmd 'run nandboot'
# setenv bootargs 'init=/init console=ttyS0, noinitrd ip=off androidboot.console=ttyS0 rootwait mem=256M \
omap_vout.vid1_static_vrfb_alloc=y rw ubi.mtd=4 rootfstype=ubifs root=ubi0:rootfs bootdelay=2'
AM3517evm u-boot doesn't support Full Speed USB mode(USB 1.1) and it expects HOST machine USB port to be High Speed USB (USB 2.0).
Following the official(?) procedure
to write/flash the YAFFS2 image i.e flash_erase &mtd_partition&, mount the &mtd_partition& and copy/untar the Android rootfs, from a running system (MMC/NFS), onto the mount_point to boot from NAND partition.
Copy the rootfs.tar.bz2 file-system to the rootfs partition of MMC/SD card.
Now boot the device from MMC/SD card and determine the MTD device for the file system partition of you Flash device
target# cat /proc/mtd
mtd0: 20000 "U-Boot"
mtd1: 20000 "U-Boot Env"
mtd2: 20000 "Kernel"
mtd3: 0c20000 "File System"
mtd4: 20000 "Reserved"
The file system partition of the flash device is /dev/mtd/mtd3
Erase the file system partition
target# flash_eraseall /dev/mtd/mtd3
Erasing 16 Kibyte @ 3b9c000 -- 99 % complete.
Mount the Flash file system partition using the block device node on a temporary directory /tempd.
target# mkdir /tempd
Note: For small block NAND devices (i.e. DM6446) you must mount the file system as a YAFFS file system.
For large block NAND devices (i.e. DM355/AM389X) the file system should be mounted as YAFFS2.
Using the wrong version of YAFFS will result in error messages similar to:
target# mount -t yaffs2 /dev/block/mtdblock3 /tempd
yaffs: dev is
name is "mtdblock3"
yaffs: Attempting MTD mount on 31.3, "mtdblock3"
yaffs: MTD device does not support have the right page sizes
mount: wrong fs type, bad option, bad superblock on /dev/mtdblock3,
or too many mounted file systems
Untar the contents of the tarball file system image to the Flash device
target# cd /tempd
target# busybox tar xjf /rootfs.tar.gz
Unmount the Flash file system partition
target# cd /
target# umount /tempd
Now the target is ready to mount the rootfs from NAND.
target# reboot
Set the YAFFS2 bootarguments from u-boot prompt.
# setenv bootargs 'init=/init console=ttyS0, noinitrd ip=off androidboot.console=ttyS0 rootwait mem=256M \
omap_vout.vid1_static_vrfb_alloc=y rw root=/dev/mtdblock3 rootfstype=yaffs2 bootdelay=2'
Fastboot flashing support for YAFFS2
Android sources (filesystem) can be built by following the instructions documented here
We recommend to use Ubuntu 10.04+ (32-bit) , but also you can use CentOS 5.3 (32 bit).
Install DHCP server
Install tftp server (actual for OMAP3EVM)
Install repo tool
Set up your Linux development environment, make sure you have the following:
Required packages:
Git 1.5.4 or newer and the GNU Privacy Guard. JDK 6.0 (32-bit). JDK 5 is not supported. flex, bison, gperf, libsdl-dev, libesd0-dev, libwxgtk2.6-dev (optional), build-essential, zip, curl, minicom, tftp-server, uboot-mkimage
For Ubuntu 32-bit use such command:
$ 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
Ubuntu Intrepid (8.10) users may need a newer version of libreadline:
$ sudo apt-get install lib32readline5-dev
Configure your network
Configure your host Ethernet adapter
sudo ifconfig ethX 10.10.10.1 netmask 255.255.255.0 up
Configure DHCP server for target's network
 ; Example dhcpd.conf
default-lease-time 600;
max-lease-time 7200;
subnet 10.10.10.0 netmask 255.255.255.0 {
range 10.10.10.2 10.10.10.10;
host beagleboard_rev_c3 {
hardware ethernet 00:80:C8:xx:xx:
fixed-address 10.10.10.2;
host omap3evm_rev_d {
hardware ethernet 00:50:c2:xx:xx:
fixed-address 10.10.10.3;
filename "evm/uImage"; &- this string actual for boot with tftp
Configure TFTP-server
/etc/xinet.d/tftpd:
service tftp
socket_type
= /usr/sbin/in.tftpd
server_args
= /tftpboot
Clone the Sources (While build android for DM37x EVM, replace TI-Android-GingerBread-2.3-DevKit-1.0.xml with TI-Android-GingerBread-DSP-2.3-DevKit-1.0.xml in the instructions below, which has multimedia DSP acceleration enabled.)
#& mkdir rowboat-android
#& cd rowboat-android
#& repo init -u
-m TI-Android-GingerBread-2.3-DevKit-1.0.xml
#& repo sync
(For DM37x EVM only) download TI DM37x DVSDK 4.01 () and place it under external/ti-dsp/.
Build the root file system for AM37x or DM37x (Beagle XM, AM/DM37x REV G EVM)
#& make TARGET_PRODUCT=omap3evm OMAPES=5.x -j8
Build the root file system for AM3517
#& make TARGET_PRODUCT=am3517evm OMAPES=3.x -j8
Build the root file system for OMAP35x
#& make TARGET_PRODUCT=omap3evm OMAPES=3.x -j8
Install the SGX (Open GL drivers) libraries and package into filesystem
This step is not needed, but still given here to explain how SGX components gets added into a Filesystem.
For more details,
Prepare the root filesystem
Follow the steps below to populate the Android filesystem.
#& cd out/target/product/omap3evm
#& mkdir android_rootfs
#& cp -r root/* android_rootfs
#& cp -r system android_rootfs
#& sudo ../../../../build/tools/mktarball.sh ../../../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 over NFS.
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
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.
platforms/
&platform&/
templates/
android.jar
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
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.
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
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
Device Drivers --- USB Support --- USB Gadget Support --- Enable Gadget Ethernet support
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 192.168.194.2 to the target. Run this on the target:
$& ifconfig usb0 192.168.194.2 netmask 255.255.255.224 up
On Host machine, run the following commands to establish the connection to the target:
$& sudo ifconfig usb0 192.168.194.1 netmask 255.255.255.224 up
$& sudo route add 192.168.194.2 dev usb0
The target and the host machine should be connected, run ping command to test the same:
$ ping -c 3 192.168.194.2
PING 192.168.194.2 (192.168.194.2) 56(84) bytes of data.
64 bytes from 192.168.194.2: icmp_seq=1 ttl=64 time=6.08 ms
64 bytes from 192.168.194.2: icmp_seq=2 ttl=64 time=0.511 ms
64 bytes from 192.168.194.2: icmp_seq=3 ttl=64 time=0.485 ms
--- 192.168.194.2 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
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
$ adb shell
Make sure Ethernet port on board and host machine are connected to the network
Check Ethernet configuration for the board
target #& netcfg
172.24.190.59
255.255.252.0
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
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
$ adb shell
For more information about adb commands, see Android Debug Bridge page at
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
"%USERPROFILE%\.android\adb_usb.ini":
echo 0x18D1 & "%USERPROFILE%\.android\adb_usb.ini"
Edit android_winusb.inf to match EVM/Beagle vendor and product ids:
Under [Google.NTx86] section add:
 ;TI EVM
 %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.
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.
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.
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.
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.
For more information on DDMS and to use it, follow Using the Dalvik Debug Monitor page at
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
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.
Download the flashplayer installer “Flash10.1_Android_Webkit_Plugin-0.4-Linux-x86-Install.bin” from
Execute the installer
#& ./ Flash10.1_Android_Webkit_Plugin-0.4-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
install_flash_player.apk
Install flash player plug in on target via adb
#& adb install install_flash_player.apk
Do the browser configuration
Explained in the below section
Test the Adobe Flash installation
Browse the link
Should display Adobe Flash Player Successfully Installed
This section describe the procedure to run CTS on any platform.
Pre-requisites
Download and extract (untar) the CTS package from
Download and extract (untar) Google Android SDK from
NOTE: Only the SDK mentioned on the above link will work with CTS.
Setup an ADB connection between Host and platform as mentioned in ADB section above.
Setup your platform to run the accessibility tests:
adb install -r android-cts/repository/testcases/CtsDelegatingAccessibilityService.apk
On the device enable Settings & Accessibility & Accessibility & Delegating Accessibility Service
Launch the CTS.
Edit android-cts/tools/startcts to point SDK_ROOT to android sdk installation location.
Run ./tools/startcts
On CTS prompt check the available plans
cts_host & ls –plan
Start a specific Test Plan
cts_host & start --plan &plan name&
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.
#&sleep 1;
To browse web pages user should configure the Internet connection as given below.
#& netcfg eth0 dhcp
#& getprop net.eth0.dns1
This prints the dns for the ethernet port, do the following to configure the DNS entries on board.
#& setprop net.dns1 &your_dns_server_ip&
If the platform is behind proxy, then following command should be executed to set the proxy settings
#& setprop net.gprs.http-proxy
NOTE: If network is behind a proxy, in this DevKit release, we have NOT found a method to set the proxy server. We tried using "setprop net.eth0.http-proxy hostname:port" and "setprop net.gprs.http-proxy hostname:port", but neither could get us through the proxy. Also, the option of adding an entry of (99,'http_proxy','hostname:port") to the 'system' and 'secure' tables in the /data/data/com.android.providers.settings/databases/settings.db database has also been tried, but failed.
The Android GingerBread 2.3 supports USB Mass storage functionality, however the external storage can be mounted either on SD Card or a USB mass storage device. The user is allowed to choose one of the two options.
By default the TI Android DevKit chooses SD card as the external storage device.
If a user is interested to use storage over USB (USB mass storage) then following changes have to be done in the default root filesystem
1)Create some directory on Android Filesystem via adb shell or console
# mkdir /partition
2) Insert the usb mass storage device, Assume the device node created at /dev/block/sda1 and the device has fat partition.
#mount –t vfat /dev/block/sda1 /partition
3) Now usb mass storage device is mounted at /partition. You can careate browse the filr
Limitations
Auto mounting usb mass storage device not supported
The gallery app/Android Settings doesn't recognize the mass storage mounted
Some brands or models of SD cards are observed with poor performance on AM37x EVMs and other 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
the Gallery app cannot find the media files
the video playback is sluggish.
The table below lists the SD cards tested which have no issue on performance.
Brand/Model
SanDisk Ultra
SanDisk Ultra
micro SDHC
The table below lists the SD cards tested which have poor performance.
Brand/Model
micro SDHC
Lexar MULTI-USE
Lexar PLANTINUM II
PNY Optima
This is Release DevKit-V2.3 The release is available from
The release notes is available at
For further information or to report any problems, contact
For community support join
For IRC #rowboat on irc.freenode.net