Introduction
This software release has been developed and verified in the following software and hardware environment.
Known Issues - AV playback -- not available at this time --TODO: need ducati binaries
- Mic not tested
- First start up is slow
- Screen black out after 30sec. Edit display timing to fix or use ALT-F1 then ALT-F7 to bring back up
- mouse is slow for first start up
- android's keyboard does not show up
- music.apk and other apps are crashing -- latest pre-built-binary release does not have the fix required.
Please note Toolchain is upgraded since L27.7.0 release.
OMAP4 SGX hardware Graphics Accelerator libraries are required to boot AFS.
OS Kernel: Linux® 2.6.35
Android: Gingerbread public project
SGX version: 1.1.17.4403
Toolchain: CodeSourcery compiler version Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux
Reference hardware platform: PandaBoard A1 -- ES2.1, PandaBoard A2
Build Host OS: Ubuntu 10.04, Ubuntu 11.04
HDMI Display: HP2159m, DELL 2408WFP, DELL ST2220L
SD Card: 2GB Kingston Technology, 2GB SanDisk microSD (using ADAPTER)
Prebuilt binaries
Download binaries: Gingerbread Pre-Built "DRAFT" Release Package - Pre-Built Release (WLAN/GFX included)
- Launcher2.apk
- kernel and android patches required for building
- WLAN/BT patches -- Note: to rebuild wlan you need to pull the source and then apply patches
Visit:
Create_Android_Rootfs_Directory for more information
- Release Details
-
- WLAN is functional
- HDMI to DVI functional
- GFX functional
- Audio working
- ADB enabled
- Ethernet working
- Mic not tested
- TI Video playback -- not working -- requires the release of binaries
- ARM Video playback -- not tested
- music.apk and other apps are crashing -- latest pre-built-binary release does not have the fix required. Patch is available within pre-built-binary to fix this on build
Proceed to: Booting Android from SD card Building Pandroid
Tools & Dependency for Building
Pre-requisite packages for build Android Filesystem (Note this is with reference to uBuntu 8.04) If you are behind firewall, you will have to set-up firewall using the instructions in
Support Tools For higher versions of U-buntu please refer to
Host PC COnfiguration The following commands will install the correct packages to your server:
sudo apt-get install git-core flex bison gperf libesd0-dev libwxgtk2.6-dev zlib1g-dev build-essential libstdc++5 tofrodos
sudo apt-get install x-dev
sudo apt-get install libx11-dev
sudo apt-get install libncurses5-dev
sudo apt-get install sun-java6-jdk
64-bit environment users must install g++.multilib:
sudo apt-get install g++-multilib
“Intrepid (8.10) users may need a newer version of libreadline:
sudo apt-get install lib32readline5-dev”
Android Environment Setup
Use the example below to setup your environment. Your environment may vary...
export YOUR_PATH=`pwd`
mkdir -p $YOUR_PATH/L27.12.1-P2/mydroid
mkdir -p $YOUR_PATH/L27.12.1-P2/build_tools
mkdir -p $YOUR_PATH/L27.12.1-P2/wlan
mkdir -p $YOUR_PATH/L27.12.1-P2/wlan_firmware
cd $YOUR_PATH/L27.12.1-P2/mydroid
export MYDROID=`pwd`
cd $YOUR_PATH/L27.12.1-P2/build_tools/arm-2010q1
Tool Chain for building Kernel and Drivers
The Kernel and Driver sources are built using Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux version.
Download:
arm-2010q1-202 to $Your_PATH/L27.12.1-P2/build_tools/
cd $Your_PATH/L27.12.1-P2/build_tools/
wget http://www.codesourcery.com/sgpp/lite/arm/portal/package6488/public/arm-none-linux-gnueabi/arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
tar jxvf arm-2010q1-202-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
cd $YOUR_PATH/L27.12.1-P2/build_tools/arm-2010q1/
export PATH=$PATH:$YOUR_PATH/L27.12.1-P2/build_tools/arm-2010q1/bin
Downloading Release Software
Installing repo
For detail information regarding repo visit:
Using Repo and Git Other reference links on Git can be found in
Techincal References page Download repo to environment
$ cd $YOUR_PATH/L27.12.1-P2/mydroid
$ curl http://android.git.kernel.org/repo > ./repo
$ chmod a+x repo
Download Android source
cd $YOUR_PATH/L27.12.1-P2/
cd $MYDROID
repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 27.x -m RLS27.12.1-P2_Gingerbread.xml
repo sync
Update PandaBoard device directory---
TODO: clean up and remove Blaze items
cd $MYDROID/device/ti/pandaboard
git fetch http://review.omapzoom.org/p/device/ti/pandaboard refs/changes/12/13612/1 && git cherry-pick FETCH_HEAD
Adding Mouse and Keyboard support cd $MYDROID/frameworks/base
git remote add rowboat git://gitorious.org/rowboat/frameworks-base.git
git fetch rowboat
git cherry-pick 17128d44ab04c5b7cb2911e8b1c9f837aa9b36a5
git cherry-pick 174cb50436065dc092114d69fb40d5a7712e3ca0
Adding Audio Support cd $MYDROID/hardware/ti/omap3
git fetch http://review.omapzoom.org/p/platform/hardware/ti/omap3 refs/changes/76/13276/5 && git cherry-pick FETCH_HEAD
diff --git a/modules/alsa/Android.mk b/modules/alsa/Android.mk
index 31d4890..b2c1e6b 100644
--- a/modules/alsa/Android.mk
+++ b/modules/alsa/Android.mk
@@ -39,6 +39,7 @@ ifeq ($(strip $(BOARD_USES_ALSA_AUDIO)),true)
endif
ifeq ($(strip $(TARGET_BOARD_PLATFORM)), omap4)
ifeq ($(strip $(TARGET_BOOTLOADER_BOARD_NAME)), pandaboard)
+ LOCAL_CFLAGS += -DOMAP4_PANDA
LOCAL_SRC_FILES:= alsa_panda.cpp
else
LOCAL_SRC_FILES:= alsa_omap4.cpp
diff --git a/modules/alsa/alsa_omap4.h b/modules/alsa/alsa_omap4.h
index cde2a3e..40bb63f 100644
--- a/modules/alsa/alsa_omap4.h
+++ b/modules/alsa/alsa_omap4.h
@@ -26,12 +26,18 @@
#endif
// alsa devices
+#ifdef OMAP4_PANDA
+#define MM_DEFAULT_DEVICE "plughw:0,4"
+#define MM_LP_DEVICE "hw:0,4"
+#define HDMI_DEVICE "plughw:0,6"
+#else
#define MM_DEFAULT_DEVICE "plughw:0,0"
#define BLUETOOTH_SCO_DEVICE "plughw:0,0"
#define FM_TRANSMIT_DEVICE "plughw:0,0"
#define FM_CAPTURE_DEVICE "plughw:0,1"
#define MM_LP_DEVICE "hw:0,6"
#define HDMI_DEVICE "plughw:0,7"
+#endif
// omap4 outputs/inputs
#define OMAP4_OUT_SCO (\
Adding WLAN support cd $YOUR_PATH/L27.12.1-P2/
git clone git://git.omapzoom.org/platform/hardware/ti/wlan.git
cd $YOUR_PATH/L27.12.1-P2/wlan
git reset --hard 456971003aaa94a6b863b7a368aac8415ff32f8c
Patch for Google apps crashing -- Courtesy of
Always Innovating --- a/frameworks/base/libs/ui/InputReader.cpp
+++ b/frameworks/base/libs/ui/InputReader.cpp
@@ -426,7 +426,7 @@
{ // acquire state lock
AutoMutex _l(mStateLock);
- int32_t touchScreenConfig = InputConfiguration::TOUCHSCREEN_NOTOUCH;
+ int32_t touchScreenConfig = InputConfiguration::TOUCHSCREEN_FINGER;
int32_t keyboardConfig = InputConfiguration::KEYBOARD_NOKEYS;
int32_t navigationConfig = InputConfiguration::NAVIGATION_NONAV;
{ // acquire device registry reader lock
Kernel & Driver Source
To clone kernel source from scratch do:
cd $YOUR_PATH/L27.12.1-P2/
git clone git://git.omapzoom.org/kernel/omap.git kernel/android-2.6.35
cd kernel/android-2.6.35
git checkout ec895072ad0b686d2c130e5d80a3076a03042033
If you already have kernel source cloned then just update it (and add a remote if it is the first time):
cd $YOUR_PATH/L27.12.1-P2/kernel/android-2.6.35
git fetch origin
git checkout ec895072ad0b686d2c130e5d80a3076a03042033
- Kernel Patches
cd ${YOUR_PATH}/L27.12.1-P2/kernel/android-2.6.35
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/01/13001/2 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/02/13002/2 && git cherry-pick FETCH_HEAD
cd ${YOUR_PATH}/L27.12.1-P2/kernel/android-2.6.35
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/17/13617/1 && git cherry-pick FETCH_HEAD
cd ${YOUR_PATH}/L27.12.1-P2/kernel/android-2.6.35
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/22/13722/2 && git cherry-pick FETCH_HEAD
cd ${YOUR_PATH}/L27.12.1-P2/kernel/android-2.6.35
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/02/12002/2 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/03/12003/1 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/64/14064/1 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/67/14067/1 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/68/14068/1 && git cherry-pick FETCH_HEAD
- update panda_defconfig -- TODO:get this merged:
cd ${YOUR_PATH}/L27.12.1-P2/kernel/android-2.6.35
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/29/13029/3 && git cherry-pick FETCH_HEAD
git fetch http://review.omapzoom.org/p/kernel/omap refs/changes/61/13861/1 && git cherry-pick FETCH_HEAD
U-Boot Source
cd $YOUR_PATH/L27.12.1-P2/
git clone git://git.omapzoom.org/repo/u-boot.git u-boot
cd u-boot
git checkout 601ff71c8d46b5e90e13613974a16d10f2006bb3
- u-boot patch
a patch is available that changes the bootdelay as well as configures the correct bootargs:
bootargs patch X-loader Source
cd $YOUR_PATH/L27.12.1-P2/
git clone git://git.omapzoom.org/repo/x-loader.git x-loader
cd x-loader
git checkout c8855fa6b85bd44073bd1b25dbffa99f02cbeeed
Build Instructions
Setting up build environment
cd $YOUR_PATH/L27.12.1-P2/
mkdir $MYDROID/logs
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export CROSS_COMPILE=arm-none-linux-gnueabi-
export PATH=$YOUR_PATH/L27.12.1-P2/build_tools/arm-2010q1/bin:$PATH
Building u-boot
Before building u-boot adjust the bootdelay and bootargs in omap4430panda.h
Note: Anyone wanting to try Fastboot do not adjust the BOOTDELAY - changing bootdelay
vim $YOUR_PATH/L27.12.1-P2/u-boot/include/configs/omap4430panda.h
- #define CONFIG_BOOTDELAY 0
+ #define CONFIG_BOOTDELAY 5
- build u-boot
cd $YOUR_PATH/L27.12.1-P2/u-boot
make distclean
make ARCH=arm omap4430panda_config
make 2>&1 |tee $MYDROID/logs/u-boot_make.out
For information regarding Fastboot visit:
Android_eMMC_Booting Building x-loader
cd $YOUR_PATH/L27.12.1-P2/x-loader
make distclean
make ARCH=arm omap4430panda_config
make ift 2>&1 |tee $MYDROID/logs/x-loader_make.out
Building Kernel
- Build Kernel
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable. "mkimage" is located in your u-boot/tools/ directory.
cd $YOUR_PATH/L27.12.1-P2/kernel/android-2.6.35
make ARCH=arm distclean #(required for rebuild only)
make ARCH=arm panda_defconfig
make ARCH=arm uImage 2>&1 |tee $MYDROID/logs/kernel_make.out
- Building Kernel modules
cd $YOUR_PATH/L27.12.1-P2/kernel/android-2.6.35
make ARCH=arm modules 2>&1 |tee $MYDROID/logs/kernel_modules.out
Building WLAN driver
- Build 127x station driver
cd $YOUR_PATH/L27.12.1-P2/wlan/wl1283/platforms/os/linux
export KERNEL_DIR=$YOUR_PATH/L27.12.1-P2/kernel/android-2.6.35
make clean
make TNETW=1273
- Build 127x softAp driver
cd $YOUR_PATH/L27.12.1-P2/wlan/wl1283_softAP/platforms/os/linux
make TNETW=1273
Building Android Filesystem (AFS) with TI Codecs enabled
on step below use the number of cores you have available; i.e. -j4 or -j12:
cd $MYDROID
cp -Rfp device/ti/pandaboard/buildspec.mk.default buildspec.mk
make clean #(required for rebuild only)
make TARGET_PRODUCT=pandaboard -j4 2>&1 |tee $MYDROID/logs/android_make.out
Preparing Android binaries SD Setup
This step will prepare a directory, called myfs, containing all necessary Android files that you must include within your SD card.
Create Android Rootfs Directory
cd $YOUR_PATH/L27.12.1-P2/
mkdir myfs
cd myfs
cp -Rfp $YOUR_PATH/L27.12.1-P2/kernel/android-2.6.35/drivers/staging/ti-st/*.ko $MYDROID/out/target/product/pandaboard/root
cp -Rfp $YOUR_PATH/L27.12.1-P2/kernel/android-2.6.35/drivers/bluetooth/btwilink.ko $MYDROID/out/target/product/pandaboard/root
cp -Rfp $YOUR_PATH/L27.12.1-P2/wlan/wl1283/platforms/os/linux/tiwlan_drv.ko $MYDROID/out/target/product/pandaboard/system/etc/wifi/
cp -Rfp $YOUR_PATH/L27.12.1-P2/wlan/wl1283_softAP/platforms/os/linux/tiap_drv.ko $MYDROID/out/target/product/pandaboard/system/etc/wifi/softap/
cp -ax $MYDROID/device/ti/proprietary-open/graphics/omap4/* $MYDROID/out/target/product/pandaboard/
cp -Rfp $MYDROID/out/target/product/pandaboard/root/* .
cp -Rfp $MYDROID/out/target/product/pandaboard/system .
cp -Rfp $MYDROID/out/target/product/pandaboard/data .
- Adding BT/WLAN support
Download:
GingerBread_L27.12.1-P2_Connectivity_127x-Install to your $YOUR_PATH/L27.12.1-P2/wlan_firmware
- create diretory within rootfs for firmware
cd $YOUR_PATH/L27.12.1-P2/myfs
mkdir -p system/etc/firmware
cd $YOUR_PATH/L27.12.1-P2/myfs
cp -rfp $YOUR_PATH/L27.12.1-P2/wlan/wl1283/platforms/os/linux/*.ko system/etc/wifi/
cp -rfp $YOUR_PATH/L27.12.1-P2/wlan/wl1283_softAP/platforms/os/linux/*.ko system/etc/wifi/softap
- adding firmware to rootfs
cd $YOUR_PATH/L27.12.1-P2/myfs
cp -rfp $YOUR_PATH/L27.12.1-P2/wlan_firmware/BT_Firmware/* system/etc/firmware/
cp -rfp $YOUR_PATH/L27.12.1-P2/wlan_firmware/WLAN_config/Station_config/tiwlan.ini system/etc/wifi
cp -rfp $YOUR_PATH/L27.12.1-P2/wlan_firmware/WLAN_config/AP_Config/tiwlan_ap.ini system/etc/wifi/softap
cp -rfp $YOUR_PATH/L27.12.1-P2/wlan_firmware/WLAN_Firmware/Station_FW/firmware.bin system/etc/wifi
cp -rfp $YOUR_PATH/L27.12.1-P2/wlan_firmware/WLAN_Firmware/AP_FW/firmware_ap.bin system/etc/wifi/softap
- Edit init.omap4430.rc for PandaBoard
cd $YOUR_PATH/L27.12.1-P2/myfs/
vim init.omap4430.rc
on fs
-mount ext4 /dev/block/platform/mmci-omap-hs.0/by-name/system /system wait ro
-mount ext4 /dev/block/platform/mmci-omap-hs.0/by-name/userdata /data wait noatime nosuid nodev
-mount ext4 /dev/block/platform/mmci-omap-hs.0/by-name/cache /cache wait noatime nosuid nodev
on fs
+#mount ext4 /dev/block/platform/mmci-omap-hs.0/by-name/system /system wait ro
+#mount ext4 /dev/block/platform/mmci-omap-hs.0/by-name/userdata /data wait noatime nosuid nodev
+#mount ext4 /dev/block/platform/mmci-omap-hs.0/by-name/cache /cache wait noatime nosuid nodev
#Load IVA firmware
-service baseimage /system/bin/syslink_daemon.out -f /data/base_image_sys_m3.xem3 /data/base_image_app_m3.xem3
- critical
- user media
- group media
#Load IVA firmware
+#service baseimage /system/bin/syslink_daemon.out -f /data/base_image_sys_m3.xem3 /data/base_image_app_m3.xem3
+# critical
+# user media
+# group media
- Edit init.rc for PandaBoard
cd $YOUR_PATH/L27.12.1-P2/myfs
vim init.rc
# once everything is setup, no need to modify /
- mount rootfs rootfs / rw remount
+#mount rootfs rootfs / rw remount
- Replace Launcher apk
Take this from L27.12.1-P2 binary release.
cd $YOUR_PATH/L27.12.1-P2/myfs
cp -Rfp Patches/android/Launcher2.apk system/app
Booting Kernel and Android from SD
You will need to format your SD for the Linux file system. Connect your SD memory card reader with memory card inserted to a USB port on your Linux Ubuntu PC. You must login as Super User.
$ su
$ fdisk -l
Match the device to the size of your memory card. Look for the /dev/*** device which matches the memory card in the card reader. Use the matching device’s letter prefix in the next command. For example if the device for memory card reader card example was: /dev/sdb1, then use only /dev/sdb in the fdisk command.
Take note of the size in bytes of your SD Card. You will need this to calculate the number of cylinders in a future step.
$ fdisk /dev/sdb (replace sdb with the letter prefix for your device)
(Delete all partitions on the card if they exist)
Command (m for help): d
Partition number (1-4): 1
Command (m for help): d
Selected partition 2
Command (m for help): x
(Change the number of heads, sectors and cylinders on the device)
Expert command (m for help): h
Number of heads (1-256, default 255): 255
Expert command (m for help): s
Number of sectors (1-63, default 63): 63
Expert command (m for help): c
Number of cylinders (1-1048576, default 248): <You must calculate the number of cylinders for your SD card. To do this, use the following formula:
new_cylinders = (Size in bytes from your fdisk –l command)/8225280
Drop any fractional values and enter the whole number in this command.
Use this number all the steps that refer to the number of cylinders>
(Now return to the main menu)
Expert command (m for help): r
(Create the first partition)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-248, default 1): 1
Last cylinder or +size or +sizeM or +sizeK (1-248, default 248): +64M
If you plan to use this SD card partition for storing media your can use +1024M assuming a 2+ GB SD card.
(Create the second partition)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (10-248, default 10): 10
Last cylinder or +size or +sizeM or +sizeK (124-248, default 248): <use the cylinder value you calculated earlier>
(Change the first partition to at FAT32 partition)
Command (m for help): t
Partition number (1-4): 1
Hex code (type L to list codes): c
Changed system type of partition 1 to c (W95 FAT32 (LBA))
(Toggle the bootable flag for partition 1)
Command (m for help): a
Partition number (1-4): 1
(Print the partition table to confirm your settings)
Command (m for help): p
(Sample Output – your output may differ depending on your SD card’s size and brand)
Disk /dev/sdb: 2041 MB, 2041577472 bytes
255 heads, 63 sectors/track, 248 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 9 72261 c W95 FAT32 (LBA)
/dev/sdb2 10 248 1919767+ 83 Linux
(Write your changes to the SD Card)
Command (m for help): w
(You will see the following output)
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk manual page for additional information.
Syncing disks.
Format your partitions typing the following commands (logged as root@ubuntu-box):
$ mkfs.vfat -F 32 -n boot /dev/<your device’s first partition’s name – see the print output from the previous step>
$ mkfs.ext3 -L android_fs /dev/<your device’s second partition’s name – see the print output from the previous step>
There is a shell script that all calculations above automatically; to get it do:
$ wget http://cgit.openembedded.org/cgit.cgi/openembedded/plain/contrib/angstrom/omap3-mkcard.sh
Add execution permission:
$ chmod +x omap3-mkcard.sh
And you are ready to use it by just typing:
$sudo ./omap3-mkcard.sh <your_device (e.g. /dev/sdb)>
Copying Binaries onto SD Card
Now type the following to mount your SD Card on your Linux box:
mkdir /tmp/mmc1
mkdir /tmp/mmc2
sudo mount /dev/<your device’s first partition’s name> /tmp/mmc1
sudo mount /dev/<your device’s second partition’s name> /tmp/mmc2
Load the appropriate software to the SD Card:
sudo cp $YOUR_PATH/L27.12.1-P2/x-loader/MLO /tmp/mmc1 #(if you are using EMU or HS device, plese copy signed MLO instead)
sudo cp $YOUR_PATH/L27.12.1-P2/u-boot/u-boot.bin /tmp/mmc1
sudo cp $YOUR_PATH/L27.12.1-P2/kernel/android-2.6.35/arch/arm/boot/uImage /tmp/mmc1
sudo cp -Rfp $YOUR_PATH/L27.12.1-P2/myfs/* /tmp/mmc2
sudo chmod -R 777 /tmp/mmc2/*
sync
sudo umount /tmp/mmc1
sudo umount /tmp/mmc2
SD Booting
Insert your SD card (with u-boot, x-loader and uImage loaded in FAT partition and ) into PandaBoard SD/MMC card slot, then plug the PandaBoard mini USB port to your PC and open a serial terminal (baudrate:115200, no parity, 8 bits). Power your board up and in your terminal window you should be able to see the ‘New’ u-boot prompt:
“PANDA #”
In your serial terminal define the bootargs and boot as mentioned in the bootarg section.</br>
Right after this your PandaBoard should start booting using the kernel image and loading the Android filesystem from your SD
Bootargs
Note that parameter mem=456M@0x80000000 mem=512M@0xA0000000 should be used in the bootargs L27.12.1-P2 Bootargs for SD card bootsetenv bootargs 'console=ttyO2,115200n8 androidboot.console=ttyO2 mem=456M@0x80000000 mem=512M@0xA0000000 root=/dev/mmcblk0p2 rw rootdelay=2 init=/init vram="32M" omapfb.vram=0:16M omapdss.def_disp=hdmi consoleblank=0'
setenv bootcmd 'mmcinit 0;fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
boot
NOTE: some people have reported problems with copy-n-paste with the single line bootargs listed above. use this set of bootargs for paste functions: setenv console console=ttyO2,115200n8 androidboot.console=ttyO2
setenv memory mem=456M@0x80000000 mem=512M@0xA0000000
setenv rootfs root=/dev/mmcblk0p2 rw rootdelay=2 init=/init
setenv vmem vram="32M" omapfb.vram=0:16M
setenv display omapdss.def_disp=hdmi consoleblank=0
setenv bootargs ${console} ${memory} ${rootfs} ${vmem} ${display}
printenv bootargs
setenv bootcmd 'mmcinit 0;fatload mmc 0 0x80000000 uImage; bootm 0x80000000'
boot
Preparing Android using Fastboot Bootup
Booting into fastboot
Hold down the the input button (button located furthest away from SD card) during bootup. This will bring pandaboard up into fastboot. Below is what you should see:
Texas Instruments X-Loader 1.41 (May 17 2011 - 10:31:50)
Starting OS Bootloader from MMC/SD1 ...
U-Boot 1.1.4-L27.13.1^0-dirty (May 17 2011 - 10:31:23)
Load address: 0x80e80000
DRAM: 1024 MB
Flash: 0 kB
Using default environment
In: serial
Out: serial
Err: serial
efi partition table:
256 128K xloader
512 256K bootloader
2048 8M recovery
18432 8M boot
34816 512M system
1083392 256M cache
1607680 512M userdata
2656256 589M media
Net: KS8851SNL
Panda: GPIO_121 pressed: entering fastboot....
Device Serial Number: 1D62000300000001
Fastboot entered...
Creating SD GPT Partitions
- on Host
-
cd $MYDROID/out/target/product/pandaboard/
sudo ./../../../host/linux-x86/bin/fastboot oem format
new partition table:
256 128K xloader
512 256K bootloader
2048 8M recovery
18432 8M boot
34816 512M system
1083392 256M cache
1607680 512M userdata
2656256 589M media
Flashing bootloader, xloader and boot image.
This step is only done once. This simply creates the GPT table required for booting. If you have a new SD card you should preform this step. If you have already preform this step you can easily just flash binaries to the SD card.
cd $MYDROID/out/target/product/pandaboard/
sudo ./../../../host/linux-x86/bin/fastboot flash bootloader boot/u-boot.bin
sudo ./../../../host/linux-x86/bin/fastboot flash xloader boot/MLO
sudo ./../../../host/linux-x86/bin/fastboot flash boot boot.img
Power down and restart --hold down button during boot and re-enter fastboot
Flashing complete environment
This step will flash the entire android system to the SD card.
cd $MYDROID/out/target/product/pandaboard/
sudo ./fastboot.sh
4430 and OMAP4440 in February. At the same time TI introduced a Linux- and Android-compatible "Blaze" hardware/software development platform in smartphone format. The Blaze (pictured) sports a pico projector, dual 3.7-inch displays, three cameras, an HDMI output, a compass, plus a barometer and other sensors. 
