Talk:BeagleBone-Android-DevKit Guide

From Texas Instruments Wiki
Jump to: navigation, search
For technical support please post your questions at Please post only comments about the article BeagleBone-Android-DevKit Guide here.

Comments on BeagleBone-Android-DevKit Guide

Bobrecny said ...

The FTDI ftdibus.inf file only needs the following lines below for [FtdiHw], [FtdiHw.NTamd64] and [Strings]. The other lines should be deleted as they are for other FTDI chips and not the FT2232H that's on the BeagleBone.


[FtdiHw] %USB\VID_0403&PID_A6D0&MI_00.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_A6D0&MI_00 %USB\VID_0403&PID_A6D0&MI_01.DeviceDesc%=FtdiBus.NT,USB\VID_0403&PID_A6D0&MI_01

[FtdiHw.NTamd64] %USB\VID_0403&PID_A6D0&MI_00.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_A6D0&MI_00 %USB\VID_0403&PID_A6D0&MI_01.DeviceDesc%=FtdiBus.NTamd64,USB\VID_0403&PID_A6D0&MI_01


[Strings] Ftdi="BeagleBone" DESC="CDM Driver Package - Bus/D2XX Driver" DriversDisk="FTDI USB Drivers Disk" USB\VID_0403&PID_A6D0&MI_00.DeviceDesc=" XDS100v2 compatible USB Serial Converter A" USB\VID_0403&PID_A6D0&MI_01.DeviceDesc="XDS100v2 compatible USB Serial Converter B" SvcDesc="USB Serial Converter Driver" ClassName="USB"

Note that this will break the signature. 64-bit Windows 7 and Vista will need to boot with the <F8> menu and disable the driver signature requirement until the file can be regenerated.

--Bobrecny 02:44, 29 November 2011 (CST)

Bobrecny said ...

OK - the formatting isn't showing correctly (line breaks missing), but the information itself is correct.

--Bobrecny 02:47, 29 November 2011 (CST)

Xxiao said ...

could not get rowboperf compiled:

make[1]: Entering directory `/home/xxiao/devel/android/rowboat/rowboperf/3D/SDKPackage_OGLES2/Demos/ChameleonMan/OGLES2/Build/Android' ../../../../../Builds/OGLES2/AndroidGeneric/make_shared_lib.mak:16: No such file or directory Makefile:24: warning: overriding commands for target `clean' ../../../../../Builds/OGLES2/AndroidGeneric/make_shared_lib.mak:149: warning: ignoring old commands for target `clean' make[1]: *** No rule to make target `'. Stop. make[1]: Leaving directory `/home/xxiao/devel/android/rowboat/rowboperf/3D/SDKPackage_OGLES2/Demos/ChameleonMan/OGLES2/Build/Android' make: *** [rowboperf/3D/SDKPackage_OGLES2/Demos/ChameleonMan/OGLES2/Build/Android/libs/armeabi/] Error 2

--Xxiao 12:20, 4 December 2011 (CST)

Eric.fort said ...

notes on:

Ubuntu 12.04 LTS

card install went flawlessly, however the following did not go as expected.

$ sudo modprobe ftdi_sio vendor=0x0403 product=0xa6d0

1. rather than using this, much better to simply add a udev rule. is a pretty good guide for setting up a development environment for android on ubuntu. 2. Failed initially with device busy, no explaination of why that may be or how to find and remedy the issue

$ minicom -D /dev/`dmesg | grep FTDI | grep "now attached to" | tail -n 1 | awk '{ print $NF }'`

1. Had to run this command with sudo as aparently I have no rights to access the port as a mortal user. 2. Failed initially with device busy, no explaination of why that may be or how to find and remedy the issue.

Powering on to Android Terminal

Put the Micro SD card to the slot on the BeagleBone. Press the reset button again. See X-loader and Uboot loading. Allow the boot loader to run the boot script uEve.txt to run.Kernel boots up and Android shell is activated. Wait till Android init to start the zygote thread. See the below message appearing on the shell.

warning: `zygote' uses 32-bit capabilities (legacy support in use)

1. above message never displays 2. gives what looks like a brief # prompt that never echos anything back 3. after above "false prompt" goes on to start adb server.

Finally got shell prompt after getting the basic sdk installed and figured out how to use adb -s <serial-number> <adb-command> with the proper incantation being 'adb -s 0123456789ABCDEF shell'

keyboard and mouse on the host failed to "unloak" the home screen. plugging in a usb hub to the bone (target) and then attaching a usb keyboard and mouse got me a display on the host and working keyboard and mouse directly connected to the target (bone)

found later that it's just really sloooow over vnc. need to light up hdmi at a res the display likes....

yea, after a week to 2 weeks of steadily chipping away at this project I can almost start building my android beaglebone based cellular communicator and smartphone.

usefull reference webpages that made this possible: http://<address-of-your-beaglebone>:5801

--Eric.fort 16:43, 23 May 2012 (CDT)

There are no threads on this page yet.