www.dfi.com
Appendix A BSP User Guide
27
Appendix A
Generate uRamdisk to be loaded by uboot
The following steps generate a RAMDISK image recognized by uboot:
Assumed that you had already built up the uboot. The mkimage was generated under
~/Android_2_3_7_sources_v115_3G/bootable/bootloader/uboot-imx/tools/
$ cd
~/Android_2_3_7_sources_v115_3G/
out/target/product/imx53_smd
$
~/Android_2_3_7_sources_v115_3G/
bootable/bootloader/uboot-imx/tools/mkimage
-A arm -O linux -T ramdisk -C none -a 0x70308000 -n "Android Root Filesystem"
-d ./ramdisk.img ./uramdisk.img
Please use the mfgtool to program these images to the corresponding partitions in the android
system.
System on MMC/SD and eMMC
Android system supports running on the MMC/SD card, or the onboard eMMC device.
Currently, it supports eMMC device for booting on the FS200 board.
We need images listed below to create an android system on MMC/SD or eMMC device:
• u-boot image: u-boot.bin
• kernel image: uImage
• ramdisk image: uramdisk.img
• Android system root image: system.img
• Recovery root image: recovery.img
You can get all the images from the release package, or build up by yourself as the section 1
described.
If you want to boot it from the SD card, please change the init.rc in the uramdisk.img and
modify all the ‘mmcblk0px’ to ‘mmcblk1px’, as we take the eMMC block device as mmcblk0,
but the external SD slot as mmcblk1.
The following table describes how to modify the ‘mmcblk0px’ to ‘mmcblk1px’ for booting the
SD card.
Note:
FS200 takes eMMC as the default storage for android system, so the default images in
the release package only support android boot from the onboard eMMC device.
# dd if=uramdisk.img of=ramdisk.img.gz skip=64 bs=1
# gunzip ramdisk.img.gz
# mkdir ramdisk; cd ramdisk
# cpio -i < ../ramdisk.img
# vim init.rc (modify the init.rc, change the mmcblk0 to mmcblk1)
# find . | cpio --create --format=’newc’ | gzip > ../ramdisk.img
# mkimage -A arm -O linux -T ramdisk -C none -a 0x70308000 -n “Android Root
Filesystem” -d ./ramdisk.img ./uramdisk.img
