L27.IS.1 OMAP4 Icecream Sandwich Release Notes

From OMAPpedia

(Difference between revisions)
Jump to: navigation, search
m (Introduction)
m (Downloading Release Software)
 
(14 intermediate revisions not shown)
Line 38: Line 38:
mkdir ~/bin -p
mkdir ~/bin -p
sudo apt-get install curl
sudo apt-get install curl
-
curl http://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
+
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
chmod a+x ~/bin/repo
export PATH=~/bin:$PATH
export PATH=~/bin:$PATH
Line 62: Line 62:
mkdir -p 27.IS.1/mydroid; cd 27.IS.1/mydroid
mkdir -p 27.IS.1/mydroid; cd 27.IS.1/mydroid
export MYDROID=`pwd`
export MYDROID=`pwd`
-
repo init -u git://git.omapzoom.org/repo/android/platform/omapmanifest.git -b 27.x -m RLS27.IS.1_IcecreamSandwich.xml  
+
repo init -u git://git.omapzoom.org/repo/android/platform/omapmanifest.git -b 27.x -m RLS27.IS.1_IcecreamSandwich.xml --repo-branch=master --repo-url=git://git.omapzoom.org/tools/repo
repo sync
repo sync
</pre>
</pre>
Line 82: Line 82:
git fetch origin
git fetch origin
git checkout 042a2c41c2445220892ac0562de286dd955ebed9
git checkout 042a2c41c2445220892ac0562de286dd955ebed9
 +
</pre>
 +
 +
'''Kernel Driver Update for SMC 1.6.4 support''' <br>
 +
 +
Modify to use a different kernel commit ID <br>
 +
 +
To clone kernel source from scratch do:
 +
<pre>
 +
cd ${YOUR_PATH}
 +
mkdir kernel
 +
git clone git://git.omapzoom.org/kernel/omap.git kernel/android-3.0
 +
cd kernel/android-3.0
 +
git checkout 444fae442f417d56d09fd3fee4bb00a4ea3882e4
 +
</pre>
 +
If you already have kernel source cloned then just update it:
 +
<pre>
 +
cd $YOUR_PATH/kernel/android-3.0
 +
git fetch origin
 +
git checkout 444fae442f417d56d09fd3fee4bb00a4ea3882e4
</pre>
</pre>
Line 178: Line 197:
cd $MYDROID/hardware/ti/wlan/mac80211/compat
cd $MYDROID/hardware/ti/wlan/mac80211/compat
export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.0
export KERNEL_DIR=${YOUR_PATH}/kernel/android-3.0
-
export KLIB=kernel/android-3.0
+
export KLIB=${KERNEL_DIR}
-
export KLIB_BUILD=kernel/android-3.0
+
export KLIB_BUILD=${KERNEL_DIR}
make ARCH=arm
make ARCH=arm
</pre>
</pre>
-
The above step will produce compat.ko, cfg80211.ko, mac80211.ko, wl12xx.ko, wl12xx_sdio.ko  
+
The above step will produce compat.ko, cfg80211.ko, mac80211.ko, wl12xx.ko, wl12xx_sdio.ko
===Building Android Filesystem (AFS) with TI Codecs enabled===
===Building Android Filesystem (AFS) with TI Codecs enabled===
Line 221: Line 240:
export BOARD_TYPE="blaze_tablet" #or "blaze" depending on your board type
export BOARD_TYPE="blaze_tablet" #or "blaze" depending on your board type
-
cd $MYDROID/out/target/product/blaze_tablet
+
cd $MYDROID/out/target/product/$BOARD_TYPE
mkdir -p system/lib/modules
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/compat/compat.ko system/lib/modules/
Line 248: Line 267:
if [ -e ${YOUR_PATH}/27.IS.1/u-boot/u-boot.bin ] ; then  
if [ -e ${YOUR_PATH}/27.IS.1/u-boot/u-boot.bin ] ; then  
   cp -f ${YOUR_PATH}/27.IS.1/u-boot/u-boot.bin omap4_emmc_files
   cp -f ${YOUR_PATH}/27.IS.1/u-boot/u-boot.bin omap4_emmc_files
-
   cp -f ${YOUR_PATH}/27.IS.1/x-loader/Blaze_Tablet_GP_ES1.1_MLO omap4_emmc_files  (or Blaze_GP_ES1.1_MLO)
+
   cp -f ${YOUR_PATH}/27.IS.1/x-loader/Blaze_Tablet_GP_ES1.1_MLO omap4_emmc_files  #(or Blaze_GP_ES1.1_MLO)
   cp -f ${YOUR_PATH}/27.IS.1/kernel/android-3.0/arch/arm/boot/zImage omap4_emmc_files
   cp -f ${YOUR_PATH}/27.IS.1/kernel/android-3.0/arch/arm/boot/zImage omap4_emmc_files
else
else
   cp -f ${YOUR_PATH}/u-boot/u-boot.bin omap4_emmc_files
   cp -f ${YOUR_PATH}/u-boot/u-boot.bin omap4_emmc_files
-
   cp -f ${YOUR_PATH}/x-loader/Blaze_Tablet_GP_ES1.1_MLO omap4_emmc_files  (or Blaze_GP_ES1.1_MLO)
+
   cp -f ${YOUR_PATH}/x-loader/Blaze_Tablet_GP_ES1.1_MLO omap4_emmc_files  #(or Blaze_GP_ES1.1_MLO)
   cp -f ${YOUR_PATH}/kernel/android-3.0/arch/arm/boot/zImage omap4_emmc_files
   cp -f ${YOUR_PATH}/kernel/android-3.0/arch/arm/boot/zImage omap4_emmc_files
fi
fi
-
cp -f <your_signing_path>/Blaze_Tablet_HS_ES1.1_MLO omap4_emmc_files (or Blaze_HS_ES1.1_MLO)
+
cp -f <your_signing_path>/Blaze_Tablet_HS_ES1.1_MLO omap4_emmc_files #(or Blaze_HS_ES1.1_MLO)
</pre>
</pre>
Line 290: Line 309:
mkfs.ext4 -F cache.img -L cache
mkfs.ext4 -F cache.img -L cache
</pre>
</pre>
 +
 +
===Flashing the OMAP4 Hardware===
 +
After the emmc files are available you then can use the fastboot.sh script to upload binaries to your Blaze or Blaze_Tablet <br>
 +
You will need to copy the fastboot.sh script to the location of the eMMC files. <br>
 +
 +
<pre>
 +
cd $YOUR_PATH/omap4_emmc_files
 +
cp $MYDROID/device/ti/$BOARD_TYPE/boot/fastboot.sh .
 +
 +
sed -i 's/${FASTBOOT-".\/..\/..\/..\/..\/out\/host\/linux-x86\/bin\/fastboot"}/.\/fastboot/g' fastboot.sh
 +
sed -i 's/${PRODUCT_OUT-".\/"}/.\//g' fastboot.sh
 +
</pre>
 +
Connect the Blaze or Blaze_Tablet micro USB port to your Linux box 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.
 +
You need to boot the board and start fastboot server on the target (OMAP4 board).
 +
 +
    # fastboot
 +
 +
You should see a message
 +
    Fastboot started
 +
 +
When running the fastboot script the command should be issued as super user when run:
 +
 +
  ./fastboot.sh
 +
This will detect your board and flash the images to the board.
 +
 +
 +
'''First time flashing on eMMC''' <br>
 +
<br>
 +
If there is no u-boot on your board's eMMC, 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 using the following SYSBOOT switch settings to boot from external SD card: 01011101
 +
 +
    For Blaze & Blaze_Tablet board: Switch S2-(1:8): OFF ON OFF ON ON ON OFF ON
 +
 +
 +
Note: S8-(6:1) corresponds to SYSBOOT[5:0] in TRM. (ON=0, OFF=1)
 +
 +
Once you boot the board, start fastboot server on the target (OMAP4 board).
 +
 +
    # fastboot
 +
 +
You should see a message
 +
    Fastboot started
 +
 +
Now from the PC execute following commands to flash MLO and u-boot to eMMC
 +
    ./fastboot oem format
 +
    ./fastboot flash xloader ./MLO
 +
    ./fastboot flash bootloader ./u-boot.bin
 +
 +
 +
Now change the following SYSBOOT switch settings to boot out of EMMC: 11111101 whenever the board is restarted.
 +
 +
    For Blaze & Blaze_Tablet board: Switch S2-(1:8): ON ON ON ON ON ON OFF ON
Line 405: Line 475:
</pre>
</pre>
-
 
-
'''First time flashing on eMMC'''
 
-
http://omapedia.org/wiki/Using_EMMC_on_OMAP4_devices#First_time_flashing_on_eMMC
 
='''Resources'''=
='''Resources'''=
Line 415: Line 482:
===WLAN Firmware files===
===WLAN Firmware files===
-
Wi-Fi firmware files are noe part of repo.
+
Wi-Fi firmware files are now part of repo.
-
 
+
-
===Additional Notes===
+
-
 
+
-
Whenever you are connecting HDMI for any demos, please ensure that you run this command on console. Otherwise, L3 will lock up and device will reboot
+
-
 
+
-
echo 1 > /sys/module/cpuidle44xx/parameters/max_state
+

Latest revision as of 14:46, 16 January 2012

Contents

[edit] Introduction

This software release has been developed and verified in the following software and hardware environment.

OS Kernel: Linux® 3.0
Android: Android IcecreamSandwich 4.0.1
Toolchain: CodeSourcery compiler version Sourcery G++ Lite 2010q1-202 for ARM GNU/Linux
Reference hardware platforms: TI OMAP4 4460 ES1.1 HS blaze_tablet and also TI OMAP4 4460 ES1.1 HS blaze
Build Host OS: Ubuntu
Daily Build Blaze_Tablet Version: IceCream_Blaze_Tablet_DailyBuild_270
Daily Build Blaze Version: IceCream_Blaze_DailyBuild_327

[edit] Tools & Dependency packages

Pre-requisite packages for building the Android Filesystem (Note this is with reference to Ubuntu 10.04 64-bit). Ubuntu 64-bit is required by Ice Cream Sandwich.

If you are behind 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 x-dev 
sudo apt-get install lib32readline5-dev libstdc++6 lib32z1 lib32z1-dev ia32-libs g++-multilib libx11-dev libncurses5-dev 

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 tool chain can be obtained from [2]

[edit] Downloading Release Software

Android Filesystem Sources

You can get the Android source for this release by doing:

cd <your work directory>
export YOUR_PATH=`pwd`
mkdir -p 27.IS.1/mydroid; cd 27.IS.1/mydroid
export MYDROID=`pwd`
repo init -u git://git.omapzoom.org/repo/android/platform/omapmanifest.git -b 27.x -m RLS27.IS.1_IcecreamSandwich.xml --repo-branch=master --repo-url=git://git.omapzoom.org/tools/repo
repo sync


Kernel & Driver Sources

To clone kernel source from scratch do:

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

If you already have kernel source cloned then just update it:

cd $YOUR_PATH/kernel/android-3.0
git fetch origin
git checkout 042a2c41c2445220892ac0562de286dd955ebed9

Kernel Driver Update for SMC 1.6.4 support

Modify to use a different kernel commit ID

To clone kernel source from scratch do:

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

If you already have kernel source cloned then just update it:

cd $YOUR_PATH/kernel/android-3.0
git fetch origin
git checkout 444fae442f417d56d09fd3fee4bb00a4ea3882e4

U-Boot Sources

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


X-loader Sources

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

[edit] Release Content

This release has the below content - Kernel and Drivers tested with OMAP4 4460 ES1.1 HS Blaze_Tablet @1.5GHz and verified with Ice Cream Sandwich UI - A9 source code for accelerating Video

[edit] Build Instructions

[edit] Setting up build environment

From your work directory (where your 27.IS.1 folder resides):

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

[edit] Building U-BOOT

cd ${YOUR_PATH}/u-boot
make distclean
make ARCH=arm omap44XXtablet_config (for Blaze_Tablet)
make ARCH=arm omap4430sdp_config (for Blaze)
make 2>&1 |tee $MYDROID/logs/u-boot_make.out

[edit] Building X-LOADER for OMAP4460

cd ${YOUR_PATH}/x-loader
make distclean	
make ARCH=arm omap44XXtablet_config (for Blaze_Tablet)
make ARCH=arm omap4430sdp_config (for Blaze)
make ift 2>&1 |tee $MYDROID/logs/x-loader_make.out
### For fastboot.sh flashing script purpouse rename MLO: ####
mv MLO Blaze_Tablet_GP_ES1.1_MLO (for Tablet)
mv MLO Blaze_GP_ES1.1_MLO (for Blaze)


Signing X-LOADER for HS devices

The tool for signing x-loader is provided on TI's package, (MShield). Please contact TI customer representative to get access to this tool.

cd ${YOUR_PATH}/mshield-dk
cp -f ${YOUR_PATH}/x-loader/x-load.bin .
./generate_MLO OMAP4460 ES1.1 x-load.bin


### For fastboot.sh flashing script purposes rename MLO: ####
cp MLO Blaze_Tablet_HS_ES1.1_MLO  #(For Blaze_Tablet)
mv MLO Blaze_HS_ES1.1_MLO  #(For Blaze)

[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 blaze_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 compat.ko, cfg80211.ko, mac80211.ko, wl12xx.ko, wl12xx_sdio.ko

[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

Now depending on your platform use either:

lunch blaze_tablet-userdebug  # (for Blaze Tablet)

or

lunch full_blaze-userdebug  # (for Blaze)
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. Camera based applications need TI proprietary drivers. Please contact TI customer representative to get access to proprietary sources

[edit] Preparing Android binaries

The following binaries are required by the Blaze Tablet® board. This step will prepare a directory, called myfs, containing all necessary Android files that you

must include within your SD card.


export BOARD_TYPE="blaze_tablet" #or "blaze" depending on your board type

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/


cd $YOUR_PATH
mkdir myfs
cd myfs
cp -Rfp $MYDROID/out/target/product/$BOARD_TYPE/root/* .
cp -Rfp $MYDROID/out/target/product/$BOARD_TYPE/system/ .
cp -Rfp $MYDROID/out/target/product/$BOARD_TYPE/data/ .

[edit] Preparing eMMC images

cd $YOUR_PATH
mkdir omap4_emmc_files
cp -f $MYDROID/out/host/linux-x86/bin/fastboot omap4_emmc_files
cp -f $MYDROID/out/host/linux-x86/bin/mkbootimg omap4_emmc_files
if [ -e ${YOUR_PATH}/27.IS.1/u-boot/u-boot.bin ] ; then 
  cp -f ${YOUR_PATH}/27.IS.1/u-boot/u-boot.bin omap4_emmc_files
  cp -f ${YOUR_PATH}/27.IS.1/x-loader/Blaze_Tablet_GP_ES1.1_MLO omap4_emmc_files  #(or Blaze_GP_ES1.1_MLO)
  cp -f ${YOUR_PATH}/27.IS.1/kernel/android-3.0/arch/arm/boot/zImage omap4_emmc_files
else
  cp -f ${YOUR_PATH}/u-boot/u-boot.bin omap4_emmc_files
  cp -f ${YOUR_PATH}/x-loader/Blaze_Tablet_GP_ES1.1_MLO omap4_emmc_files  #(or Blaze_GP_ES1.1_MLO)
  cp -f ${YOUR_PATH}/kernel/android-3.0/arch/arm/boot/zImage omap4_emmc_files
fi

cp -f <your_signing_path>/Blaze_Tablet_HS_ES1.1_MLO omap4_emmc_files #(or Blaze_HS_ES1.1_MLO)


Creating img files: (For blaze build instead of blaze_tablet, just replace blaze_tablet with blaze)

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_emmc_files

This build should not take too much time and will re-generate a new *.img files with the modified init.rc file in it (If you built and installed GFX after

compiling AFS, system.img and data.img will also be updated with the GFX files).

Now from this new directory we will create the eMMC 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_emmc_files
$MYDROID/device/ti/support-tools/boot/omap4/umulti2.sh 

Now create cache partition:

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

[edit] Flashing the OMAP4 Hardware

After the emmc files are available you then can use the fastboot.sh script to upload binaries to your Blaze or Blaze_Tablet
You will need to copy the fastboot.sh script to the location of the eMMC files.

cd $YOUR_PATH/omap4_emmc_files
cp $MYDROID/device/ti/$BOARD_TYPE/boot/fastboot.sh .

sed -i 's/${FASTBOOT-".\/..\/..\/..\/..\/out\/host\/linux-x86\/bin\/fastboot"}/.\/fastboot/g' fastboot.sh
sed -i 's/${PRODUCT_OUT-".\/"}/.\//g' fastboot.sh 

Connect the Blaze or Blaze_Tablet micro USB port to your Linux box 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. You need to boot the board and start fastboot server on the target (OMAP4 board).

   # fastboot

You should see a message

    Fastboot started

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

  ./fastboot.sh 

This will detect your board and flash the images to the board.


First time flashing on eMMC

If there is no u-boot on your board's eMMC, 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 using the following SYSBOOT switch settings to boot from external SD card: 01011101

   For Blaze & Blaze_Tablet board: Switch S2-(1:8): OFF ON OFF ON ON ON OFF ON


Note: S8-(6:1) corresponds to SYSBOOT[5:0] in TRM. (ON=0, OFF=1)

Once you boot the board, start fastboot server on the target (OMAP4 board).

   # fastboot

You should see a message

    Fastboot started

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

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


Now change the following SYSBOOT switch settings to boot out of EMMC: 11111101 whenever the board is restarted.

   For Blaze & Blaze_Tablet board: Switch S2-(1:8): ON ON ON ON ON ON OFF ON


Formatting SD Card

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)>

[edit] Resources

[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