4AI.1.4 OMAP4 Icecream Sandwich Panda Notes

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
(Preparing images)
m (Videos)
 
(38 intermediate revisions not shown)
Line 23: Line 23:
<pre>
<pre>
sudo apt-get install git-core flex bison gperf libesd0-dev zip libwxgtk2.6-dev zlib1g-dev build-essential tofrodos
sudo apt-get install git-core flex bison gperf libesd0-dev zip libwxgtk2.6-dev zlib1g-dev build-essential tofrodos
-
sudo apt-get install lib32readline5-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev lib32ncurses5-dev
+
sudo apt-get install lib32readline6-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev lib32ncurses5-dev
</pre>
</pre>
Line 77: Line 77:
To obtain '''Kernel & Driver Sources''' follow:
To obtain '''Kernel & Driver Sources''' follow:
-
 
-
To clone kernel source from scratch do:
 
<pre>
<pre>
cd ${YOUR_PATH}
cd ${YOUR_PATH}
Line 136: Line 134:
===Patching KERNEL===
===Patching KERNEL===
-
Download and apply [https://gforge.ti.com/gf/download/user/9174/5770/kernelpanda1.patch kernelpanda1.patch]
+
Download and apply [https://gforge.ti.com/gf/download/user/9174/5770/kernelpanda1.patch kernelpanda1.patch] [https://gforge.ti.com/gf/download/user/9174/5771/kernelpanda2.patch kernelpanda2.patch] [https://gforge.ti.com/gf/download/user/9174/5772/kernelpanda3.patch kernelpanda3.patch] [https://gforge.ti.com/gf/download/user/9174/5775/kernelpanda4.patch kernelpanda4.patch] [https://gforge.ti.com/gf/download/user/9174/5882/kernelpanda5.patch kernelpanda5.patch] [https://gforge.ti.com/gf/download/user/9174/5892/kernelpanda6.patch kernelpanda6.patch] [https://gforge.ti.com/gf/download/user/9174/5961/kernelpanda7.patch kernelpanda7.patch]
-
Download and apply [https://gforge.ti.com/gf/download/user/9174/5771/kernelpanda2.patch kernelpanda2.patch]
+
-
Download and apply [https://gforge.ti.com/gf/download/user/9174/5772/kernelpanda3.patch kernelpanda3.patch]
+
<pre>
<pre>
Line 145: Line 141:
git am kernelpanda2.patch
git am kernelpanda2.patch
git am kernelpanda3.patch
git am kernelpanda3.patch
 +
git am kernelpanda4.patch
 +
git am kernelpanda5.patch
 +
git am kernelpanda6.patch
 +
git am kernelpanda7.patch
 +
</pre>
 +
 +
===Patching MYDROID===
 +
Download and apply [https://gforge.ti.com/gf/download/user/9174/5778/devicepanda1.patch devicepanda1.patch] [https://gforge.ti.com/gf/download/user/9174/5779/devicepanda2.patch devicepanda2.patch] [https://gforge.ti.com/gf/download/user/9174/5780/devicepanda3.patch devicepanda3.patch] [https://gforge.ti.com/gf/download/user/9174/5883/devicepanda4.patch devicepanda4.patch] [https://gforge.ti.com/gf/download/user/9174/5891/devicepanda5.patch devicepanda5.patch] [https://gforge.ti.com/gf/download/user/9174/5894/devicepanda6.patch devicepanda6.patch] [https://gforge.ti.com/gf/download/user/9174/5777/proprietaryopenpanda.patch proprietaryopenpanda.patch] [https://gforge.ti.com/gf/download/user/9174/5776/commonopenpanda.patch commonopenpanda.patch] [https://gforge.ti.com/gf/download/user/9174/5893/hardwarepanda.patch hardwarepanda.patch]
 +
 +
<pre>
 +
cd ${MYDROID}/device/ti/panda
 +
git am devicepanda1.patch
 +
git am devicepanda2.patch
 +
git am devicepanda3.patch
 +
git am devicepanda4.patch
 +
git am devicepanda5.patch
 +
git am devicepanda6.patch
 +
cd ${MYDROID}/device/ti/proprietary-open
 +
git am proprietaryopenpanda.patch
 +
cd ${MYDROID}/device/ti/common-open
 +
git am commonopenpanda.patch
 +
cd ${MYDROID}/hardware/ti/wlan/mac80211/compat
 +
git am hardwarepanda.patch
</pre>
</pre>
Line 194: Line 213:
===Building WLAN driver===
===Building WLAN driver===
 +
<pre>
<pre>
cd $MYDROID/hardware/ti/wlan/mac80211/compat
cd $MYDROID/hardware/ti/wlan/mac80211/compat
Line 202: Line 222:
</pre>
</pre>
-
The above step will produce the following kernel WLAN modules: ''compat.ko'', ''cfg80211.ko'', ''mac80211.ko'', ''wl12xx.ko'' and ''wl12xx_sdio.ko''. These modules are pushed into the ''/system/lib/modules'' directory on the flashed image.
+
The above step will produce the following kernel WLAN modules: ''compat.ko'', ''cfg80211.ko'', ''mac80211.ko'', ''wl12xx.ko'' and ''wl12xx_sdio.ko''. These modules are pushed into the ''/system/lib/modules'' directory on the system image.
===Building Android Filesystem (AFS) with TI Codecs enabled===
===Building Android Filesystem (AFS) with TI Codecs enabled===
Line 218: Line 238:
This release was not verified with Android codecs.
This release was not verified with Android codecs.
 +
 +
===Building SGX driver===
 +
<pre>
 +
cd $MYDROID/device/ti/proprietary-open/omap4/sgx/src/eurasia_km/eurasiacon/build/linux2/omap4430_android
 +
export KERNELDIR=${YOUR_PATH}/kernel/android-3.0
 +
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- TARGET_PRODUCT="blaze_tablet" BUILD=release TARGET_SGX=540 PLATFORM_VERSION=4.0
 +
</pre>
 +
 +
The above step will produce the following kernel SGX modules: ''pvrsrvkm_sgx540_112.ko'' and ''omaplfb_sgx540_112.ko''. These modules are pushed into the ''/system/lib/modules'' directory on the system image.
===Preparing Android binaries===
===Preparing Android binaries===
Line 233: Line 262:
cp $MYDROID/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/wl12xx/wl12xx.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/wl12xx/wl12xx.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/wl12xx/wl12xx_sdio.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/wl12xx/wl12xx_sdio.ko system/lib/modules/
 +
 +
cp $MYDROID/out/target/product/$BOARD_TYPE/target/kbuild/omaplfb_sgx540_120.ko system/lib/modules/
 +
cp $MYDROID/out/target/product/$BOARD_TYPE/target/kbuild/pvrsrvkm_sgx540_120.ko system/lib/modules/
</pre>
</pre>
===Updating Ducati===
===Updating Ducati===
-
For hardware accelerated video playback and camera usage you have to use proper Ducati binary.
+
For hardware accelerated video playback and camera usage you have to use proper Ducati binary. Found here [http://omappedia.org/wiki/Android:_Working_with_pre-built_binaries ducati-m3.bin]
 +
 
 +
Download the ducati-m3.bin for the 4AI.1.4 release and place binary in system/vendor/firmware/ :
 +
 
 +
cp <location-of-downloaded-ducati-bin>/4AI.1.4_Blaze_ducati-m3.bin ${MYDROID}/out/target/product/panda/system/vendor/firmware/ducati-m3.bin
===Preparing images===
===Preparing images===
Line 284: Line 320:
===Flashing the OMAP4 Hardware===
===Flashing the OMAP4 Hardware===
-
After the emmc files are available you then can use the ''fastboot'' to upload binaries to your Panda or Panda ES.
+
====First time flashing on SD====
-
Connect the Panda or Panda ES mini USB port to your Linux machine and go to where the eMMC files are. Previous partitions created will be deleted and eMMC will be flashed with new u-boot and MLO.
+
If there is no u-boot on your board, you will have to boot using SD card. Copy u-boot.bin and MLO files to an SD card (boot partition) and then boot the target board from this external SD card. Once you boot the board, start fastboot server on the target (Pandaboard).  
-
You need to boot the board and start fastboot server on the target (OMAP4 board).  
+
  # fastboot
  # fastboot
Line 293: Line 328:
You should see a message such as:
You should see a message such as:
-
  "Fastboot started..." or "Fastboot entered..."
+
  "Fastboot entered..."
 +
 
 +
Now from the PC execute following commands to flash MLO and u-boot to SD
 +
 
 +
sudo ./fastboot oem format
 +
sudo ./fastboot flash xloader MLO
 +
sudo ./fastboot flash bootloader u-boot.bin
 +
sudo ./fastboot reboot
 +
 
 +
This will create several partitions on your SD card that has specific proposes for the Panda board
 +
 
 +
For '''Formatting the SD Card''':
 +
 
 +
See [http://omappedia.org/wiki/Android_Build_SD_Configuration Android Build SD Configuration] page
 +
 
 +
====Not first time flashing on SD====
 +
 
 +
After the SD files are available you then can use the ''fastboot'' to upload binaries to your Panda or Panda ES.
 +
 
 +
Connect the Panda or Panda ES mini USB port to your Linux machine and go to where the SD files are. Previous partitions created will be deleted and SD will be flashed with new u-boot and MLO.
 +
You need to boot the board and start fastboot server on the target (Pandaboard) by keeping the USER button press.
 +
 
 +
You should see a message such as:
 +
 
 +
"Fastboot entered..."
When running the fastboot the command should be issued as super user then run:
When running the fastboot the command should be issued as super user then run:
Line 305: Line 364:
  sudo ./fastboot reboot
  sudo ./fastboot reboot
-
Pandaboard will boot up on its own with the new image in a few minutes. Until the user interface is ready for use, please avoid interrupting it by pressing any keys etc.
+
Panda board will boot up on its own with the new image in a few minutes. Until the user interface is ready for use, please avoid interrupting it by pressing any keys etc.
This will detect your board and flash the images to the board.
This will detect your board and flash the images to the board.
 +
='''Resources'''=
-
'''First time flashing on SD'''
+
===4AI.1.4 Release===
 +
To get a stable release as base for the porting the 4AI.1.4 Texas Instrument release for Blaze and Blaze Tablet was considered [http://www.omappedia.com/wiki/4AI.1.4_OMAP4_Icecream_Sandwich_Release_Notes 4AI.1.4 OMAP4 Icecream Sandwich Release Notes]
-
If there is no u-boot on your board's, you will have to boot using SD card. Copy u-boot.bin and MLO files to an SD card (boot partition) and then boot the target board from this external SD card. Once you boot the board, start fastboot server on the target (OMAP4 board).  
+
===Prebuilt Binaries===
 +
[https://gforge.ti.com/gf/download/user/9174/5962/omap4_sd_files_panda.tar.gz August 2012]
-
# fastboot
+
===Panda Porting===
 +
The porting to Panda progress can be track at [http://isrcepeda.blogspot.com/ isrccepeda blogspot]
-
You should see a message such as:
+
===Videos===
-
"Fastboot started..." or "Fastboot entered..."
+
'''Don't forget to give like, thanks!'''
-
Now from the PC execute following commands to flash MLO and u-boot to eMMC
+
First video about Panda Porting: [http://www.youtube.com/watch?v=59rZEvElkLQ 4AI on Panda ES Multimedia]
-
sudo ./fastboot oem format
+
Second video about Panda Porting: [http://www.youtube.com/watch?v=1vyqHnIhSH8 4AI on Panda ES Connectivity]
-
sudo ./fastboot flash xloader ./MLO
+
-
sudo ./fastboot flash bootloader ./u-boot.bin
+
-
sudo ./fastboot reboot
+
-
This will create several partitions on your SD card that has specific proposes for the Pandaboard
+
Third video about Panda Porting: [https://www.youtube.com/watch?v=lrA0Dd8mqZY 4AI on Panda ES Google apps]
-
 
+
-
For '''Formatting the SD Card''':
+
-
 
+
-
See [http://omappedia.org/wiki/Android_Build_SD_Configuration Android Build SD Configuration] page
+
-
 
+
-
='''Resources'''=
+
===WLAN Calibration===
===WLAN Calibration===

Latest revision as of 04:08, 7 March 2013

These Notes are an effort from the community to port the 4AI.1.4 Release from Texas Instruments to the Panda and Panda ES platforms without any warranty of any kind
Texas Instruments is not responsable for supporting these notes, it is up to the community.
Feel free to use this instructions under your own risk being aware that if you face any issue you have to fix it by yourself

Contents

[edit] Introduction

This software has been tested in the following software and hardware environment:

OS Kernel: Linux® 3.0
Android: Android IcecreamSandwich 4.0.4(MR1.1)
Toolchain: CodeSourcery compiler version Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux
Reference hardware platforms: TI OMAP4 4430/60 Pandaboard and Pandaboard ES
Build Host OS: Ubuntu

[edit] Tools & Dependency packages

Pre-requisite packages for building the Android Filesystem (Note: This is with reference to Ubuntu 12.04 64-bit). Ubuntu 64-bit is required for the cross-compilation of Android Ice Cream Sandwich Filesystem.

If you are behind a firewall, you will have to set-up firewall using the instructions in [1].

The following commands will install the correct packages to your server:

sudo apt-get install git-core flex bison gperf libesd0-dev zip libwxgtk2.6-dev zlib1g-dev build-essential tofrodos
sudo apt-get install lib32readline6-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev lib32ncurses5-dev

The following commands will install the host compilers needed in your server:

sudo apt-get install gcc-4.4 gcc-4.4-multilib g++-4.4 g++-4.4-multilib
cd /usr/bin
sudo ln -sf gcc-4.4 gcc
sudo ln -sf g++-4.4 g++

Add the partner repositories and install the JDK:

sudo add-apt-repository "deb http://archive.canonical.com/ lucid partner"
sudo apt-get update
sudo apt-get install sun-java6-jdk

Install repo tool:

mkdir ~/bin -p
sudo apt-get install curl
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH=~/bin:$PATH

If you do not have sudo rights to your machine, contact your System Administrator for assistance.


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 (This particular version is needed for the AFS to work properly).

This tool chain can be obtained from [2].

[edit] Downloading Release Software

To obtain Android Filesystem Sources follow:

cd <your work directory>
mkdir -p 4AI.1.4; cd 4AI.1.4
export YOUR_PATH=`pwd`
mkdir -p mydroid; cd mydroid
export MYDROID=`pwd`
repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b 27.x -m RLS4AI.1.4_IcecreamSandwich.xml
repo sync


To obtain Kernel & Driver Sources follow:

cd ${YOUR_PATH}
git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.0
cd kernel/android-3.0
git checkout d5e6ee8b7b648094892e501b4ee6e2424d59f7d1


To obtain U-Boot Sources follow:

cd ${YOUR_PATH}
git clone git://git.omapzoom.org/repo/u-boot.git u-boot
cd u-boot
git checkout b2f9ce5c0c2747f1af86d26f9cadbc36af9b7da6


To obtain X-loader Sources follow:

cd ${YOUR_PATH}
git clone git://git.omapzoom.org/repo/x-loader.git x-loader
cd x-loader
git checkout 835089cdb52288fcf1ca2f14018ae756842be724

[edit] Release Content

This release has the below content: - A9 source code for accelerating Video

[edit] Patching for Pandaboard Support

[edit] Setting up environment

From your work directory (where your 4AI.1.4 folder resides):

export YOUR_PATH=`pwd`
export MYDROID=${YOUR_PATH}/mydroid

[edit] Patching X-LOADER

Download and apply xloaderpanda.patch

cd ${YOUR_PATH}/x-loader
git am xloaderpanda.patch

[edit] Patching U-BOOT

Download and apply ubootpanda.patch

cd ${YOUR_PATH}/u-boot
git am ubootpanda.patch

[edit] Patching KERNEL

Download and apply kernelpanda1.patch kernelpanda2.patch kernelpanda3.patch kernelpanda4.patch kernelpanda5.patch kernelpanda6.patch kernelpanda7.patch

cd ${YOUR_PATH}/kernel/android-3.0
git am kernelpanda1.patch
git am kernelpanda2.patch
git am kernelpanda3.patch
git am kernelpanda4.patch
git am kernelpanda5.patch
git am kernelpanda6.patch
git am kernelpanda7.patch

[edit] Patching MYDROID

Download and apply devicepanda1.patch devicepanda2.patch devicepanda3.patch devicepanda4.patch devicepanda5.patch devicepanda6.patch proprietaryopenpanda.patch commonopenpanda.patch hardwarepanda.patch

cd ${MYDROID}/device/ti/panda
git am devicepanda1.patch
git am devicepanda2.patch
git am devicepanda3.patch
git am devicepanda4.patch
git am devicepanda5.patch
git am devicepanda6.patch
cd ${MYDROID}/device/ti/proprietary-open
git am proprietaryopenpanda.patch
cd ${MYDROID}/device/ti/common-open
git am commonopenpanda.patch
cd ${MYDROID}/hardware/ti/wlan/mac80211/compat
git am hardwarepanda.patch

[edit] Build Instructions

[edit] Setting up build environment

From your work directory (where your 4AI.1.4 folder resides):

export YOUR_PATH=`pwd`
export PATH=$PATH:<toolchain_parent_dir>/arm-2010q1/bin
export MYDROID=${YOUR_PATH}/mydroid
mkdir $MYDROID/logs
export CROSS_COMPILE=arm-none-linux-gnueabi-
export PATH=${YOUR_PATH}/u-boot/tools:$PATH

[edit] Building X-LOADER

cd ${YOUR_PATH}/x-loader
make distclean	
make ARCH=arm omap44XXpanda_config
make ift 2>&1 |tee $MYDROID/logs/x-loader_make.out

[edit] Building U-BOOT

cd ${YOUR_PATH}/u-boot
make distclean
make ARCH=arm omap44XXpanda_config
make 2>&1 |tee $MYDROID/logs/u-boot_make.out

[edit] Building Kernel

Note: If you are building for a GP device it is recommended not to build the SMC kernel driver.
To create kernel uImage you need to add "mkimage" directory path to your "PATH" environment variable:

cd ${YOUR_PATH}/kernel/android-3.0
make ARCH=arm distclean
make ARCH=arm panda_defconfig
make ARCH=arm uImage 2>&1 |tee $MYDROID/logs/kernel_make.out

[edit] Building Kernel modules

cd ${YOUR_PATH}/kernel/android-3.0
make ARCH=arm modules 2>&1 |tee $MYDROID/logs/kernel_modules.out

[edit] Building WLAN driver

cd $MYDROID/hardware/ti/wlan/mac80211/compat
export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.0
export KLIB=${KERNEL_DIR}
export KLIB_BUILD=${KERNEL_DIR}
make ARCH=arm

The above step will produce the following kernel WLAN modules: compat.ko, cfg80211.ko, mac80211.ko, wl12xx.ko and wl12xx_sdio.ko. These modules are pushed into the /system/lib/modules directory on the system image.

[edit] Building Android Filesystem (AFS) with TI Codecs enabled

In the make step below use the number of cores you have available; i.e. -j4 (for 4 cores) or -j12 (for 12 cores)

cd $MYDROID
source build/envsetup.sh
lunch full_panda-eng
make clean ;#(required for rebuild only)
make -j4 2>&1 |tee $MYDROID/logs/android_make.out

[edit] Building AFS with Android Codecs

This release was not verified with Android codecs.

[edit] Building SGX driver

cd $MYDROID/device/ti/proprietary-open/omap4/sgx/src/eurasia_km/eurasiacon/build/linux2/omap4430_android
export KERNELDIR=${YOUR_PATH}/kernel/android-3.0
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- TARGET_PRODUCT="blaze_tablet" BUILD=release TARGET_SGX=540 PLATFORM_VERSION=4.0

The above step will produce the following kernel SGX modules: pvrsrvkm_sgx540_112.ko and omaplfb_sgx540_112.ko. These modules are pushed into the /system/lib/modules directory on the system image.

[edit] Preparing Android binaries

The following binaries maybe are not required by the Panda board.

export BOARD_TYPE="panda"

cd $MYDROID/out/target/product/$BOARD_TYPE
mkdir -p system/lib/modules
cp $MYDROID/hardware/ti/wlan/mac80211/compat/compat/compat.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat/net/wireless/cfg80211.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat/net/mac80211/mac80211.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/wl12xx/wl12xx.ko system/lib/modules/
cp $MYDROID/hardware/ti/wlan/mac80211/compat/drivers/net/wireless/wl12xx/wl12xx_sdio.ko system/lib/modules/

cp $MYDROID/out/target/product/$BOARD_TYPE/target/kbuild/omaplfb_sgx540_120.ko system/lib/modules/
cp $MYDROID/out/target/product/$BOARD_TYPE/target/kbuild/pvrsrvkm_sgx540_120.ko system/lib/modules/

[edit] Updating Ducati

For hardware accelerated video playback and camera usage you have to use proper Ducati binary. Found here ducati-m3.bin

Download the ducati-m3.bin for the 4AI.1.4 release and place binary in system/vendor/firmware/ :

cp <location-of-downloaded-ducati-bin>/4AI.1.4_Blaze_ducati-m3.bin ${MYDROID}/out/target/product/panda/system/vendor/firmware/ducati-m3.bin

[edit] Preparing images

cd $YOUR_PATH
mkdir omap4_sd_files_$BOARD_TYPE
cd omap4_sd_files_$BOARD_TYPE
cp -f $MYDROID/out/host/linux-x86/bin/fastboot .
cp -f $MYDROID/out/host/linux-x86/bin/mkbootimg .
cp -f $MYDROID/out/host/linux-x86/bin/simg2img .
cp -f $MYDROID/out/host/linux-x86/bin/make_ext4fs .

cp -f ${YOUR_PATH}/x-loader/MLO .
cp -f ${YOUR_PATH}/u-boot/u-boot.bin .
cp -f ${YOUR_PATH}/kernel/android-3.0/arch/arm/boot/zImage .


Creating img files:

cd ${MYDROID}
find out/target/product/$BOARD_TYPE -name *.img -exec rm -f {} \;  
make
cp -f ${MYDROID}/out/target/product/$BOARD_TYPE/*.img $YOUR_PATH/omap4_sd_files_$BOARD_TYPE

This build should not take too much time and will re-generate a new *.img files.

Now from this new directory we will create the SD images which will be flashed using fastboot protocol (described later). First create boot.img image using kernel image we copied previously:

cd $YOUR_PATH/omap4_sd_files_$BOARD_TYPE
$MYDROID/device/ti/support-tools/boot/omap4/umulti2.sh 

Now create cache partition:

cd $YOUR_PATH/omap4_sd_files_$BOARD_TYPE
dd if=/dev/zero of=./cache.img bs=1048510 count=128
mkfs.ext4 -F cache.img -L cache

[edit] Flashing the OMAP4 Hardware

[edit] First time flashing on SD

If there is no u-boot on your board, you will have to boot using SD card. Copy u-boot.bin and MLO files to an SD card (boot partition) and then boot the target board from this external SD card. Once you boot the board, start fastboot server on the target (Pandaboard).

# fastboot

You should see a message such as:

"Fastboot entered..."

Now from the PC execute following commands to flash MLO and u-boot to SD

sudo ./fastboot oem format
sudo ./fastboot flash xloader MLO
sudo ./fastboot flash bootloader u-boot.bin
sudo ./fastboot reboot

This will create several partitions on your SD card that has specific proposes for the Panda board

For Formatting the SD Card:

See Android Build SD Configuration page

[edit] Not first time flashing on SD

After the SD files are available you then can use the fastboot to upload binaries to your Panda or Panda ES.

Connect the Panda or Panda ES mini USB port to your Linux machine and go to where the SD files are. Previous partitions created will be deleted and SD will be flashed with new u-boot and MLO. You need to boot the board and start fastboot server on the target (Pandaboard) by keeping the USER button press.

You should see a message such as:

"Fastboot entered..."

When running the fastboot the command should be issued as super user then run:

sudo ./fastboot flash xloader MLO
sudo ./fastboot flash bootloader u-boot.bin
sudo ./fastboot flash boot boot.img
sudo ./fastboot flash system system.img
sudo ./fastboot flash cache cache.img
sudo ./fastboot flash userdata userdata.img
sudo ./fastboot reboot

Panda board will boot up on its own with the new image in a few minutes. Until the user interface is ready for use, please avoid interrupting it by pressing any keys etc. This will detect your board and flash the images to the board.

[edit] Resources

[edit] 4AI.1.4 Release

To get a stable release as base for the porting the 4AI.1.4 Texas Instrument release for Blaze and Blaze Tablet was considered 4AI.1.4 OMAP4 Icecream Sandwich Release Notes

[edit] Prebuilt Binaries

August 2012

[edit] Panda Porting

The porting to Panda progress can be track at isrccepeda blogspot

[edit] Videos

Don't forget to give like, thanks!

First video about Panda Porting: 4AI on Panda ES Multimedia

Second video about Panda Porting: 4AI on Panda ES Connectivity

Third video about Panda Porting: 4AI on Panda ES Google apps

[edit] WLAN Calibration

For optimal Wi-Fi performance calibration of Wi-Fi hardware is mandatory, follow the procedure from http://omappedia.org/wiki/Android_Mac80211#WLAN_Calibration_Instruction

[edit] WLAN Firmware files

Wi-Fi firmware files are now part of repo.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox