Ashwin,
I appreciate if you can point me further
I successfully compiled u-boot.bin, uImage, system.img, ramdisk.img,
userdata.img for Marvell Littleton. And my MTD partitions look like
this
# cat /proc/mtd
# dev:size erasesize name
# mtd0: 0010 0002 "Bootloader"
# mtd1: 0030
Ashwin,
I appreciate if you can point me further
I successfully compiled u-boot.bin, uImage, system.img, ramdisk.img,
userdata.img for Marvell Littleton. And my MTD partitions look like
this
# cat /proc/mtd
# dev:size erasesize name
# mtd0: 0010 0002 "Bootloader"
# mtd1: 0030
Hi,
Followed the steps as explained but got the following error.
Warning: unable to open an initial console.
init: cannot open '/initlogo.rle'
Sending SIGBUS to "app_process" due to unaligned access (PC 7000ec36 PR
70001830)
Sending SIGBUS to "installd" due to unaligned access (PC 7000ec36 PR
Hi all,
I compiled st linux (android patch )kernel for sh4 architecture ( ST7109
) and got uImage.
Also I compiled android sdk for sh4 architecture and got three images
ramdisk.img,system.img,userdata.img.
I have the board up and running with my u-boot and St linux2.4 (patched
for android) a
> *How do i use the images ramdisk.img,system.img,userdata.img to boot android
> through _NFS_*_.
For NFS Boot, boot args should be some thing like this:
root=/dev/nfs rw nfsroot=:
ip=dhcp init=/init console=ttyS2, 115200n8 noinitrd
Make sure that you have exported your NFS server in /etc/exports
>1) now the question is should i write all my RFS specific img's ie system.img,
> userdata.img, ramdisk.img to the same "ROOT" partition or should it be in
> different partition.
See a sample NAND MTD partition table from the kernel logs:
Creating 7 MTD partitions on "NAND 256MiB 3,3V 8-bit":
0x0
