Hi,

I tried to start the android image from a SDCard on a SAM9G45-based Board (http://www.ic-board.de/product_info.php ... c725b0e7d6). But my board is that i dont have the right uboot config to start it (i think so...). My actual bootcmd is this: bootcmd=mtdparts default; mmc rescan 0; fatload mmc 0 0x71000000 ramImage; fatload mmc 0 0x70400000 uImage; bootm 0x70400000 0x71000000; setenv bootargs $bootargs rootfstype=ubifs root=ubi0:root ubi.mtd=1; mtdparts default; nand read 0x70400000 nand0,0; bootm.

I think the problem a file named ramImage is not on the sdcard. My main question is which files should i load to which adress (i think 0x71000000 is maybe not the right one...). Maybe someone can post his/her bootcmd.

Actually i can successfully boot the linux image from the nand but not the android. This is the actual uboot output:
ICnova> boot
reading ramImage

** Unable to read "ramImage" from mmc 0:1 **
reading uImage

2090384 bytes read
## Booting kernel from Legacy Image at 70400000 ...
Image Name: Linux-2.6.30
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2090320 Bytes = 2 MB
Load Address: 70008000
Entry Point: 70008000
Verifying Checksum ... OK
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid

NAND read: device 0 offset 0x0, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 70400000 ...
Image Name: Linux-2.6.33.2
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2100244 Bytes = 2 MB
Load Address: 70008000
Entry Point: 70008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Thanks for your help and best regards

We did not use u-boot to start kernel in the latest release of demo package. Just try the latest at91bootstrap.The boot command for bootstrap is: mem=128M console=ttyS0,115200 root=/dev/mmcblk0p2 rw rootfstype=/dev/mmcblk0p2 rw rootfstype=ext2 init=/init nohz=off rootdelay=1
,bootstrap will find kernel file by :CONFIG_OS_IMAGE_NAME="uImage"

You could change it if needed.May it help.

Thanks for your help. I tried to use my AT91Bootstrap & Uboot combination again, because i dont want to flash the nand if it's not really necessary. Now i can boot the kernel with your bootargs but i have the problem that the kernel can not find the root partition or mmcblk0p2. When i boot my current linux image from the nand i can mount /dev/mmcblk0p2 and see the content.

My U-Boot commands are now:
setenv bootargs "mem=128M console=ttyS0,115200 root=/dev/mmcblk0p2 rw rootfstype=ext2 init=/init nohz=off rootdelay=2"
setenv bootcmd "mmc rescan 0; fatload mmc 0 0x70400000 uImage; bootm 0x70400000;"

This is the error message in the kernel log:
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "mmcblk0p2" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 5120 mtdblock0 (driver?)
1f01 97280 mtdblock1 (driver?)
1f02 65536 mtdblock2 (driver?)
1f03 94208 mtdblock3 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<c0031b40>] (unwind_backtrace+0x0/0xec) from [<c004335c>] (panic+0x6c/0xec)
[<c004335c>] (panic+0x6c/0xec) from [<c0008f04>] (mount_block_root+0x1c4/0x204)
[<c0008f04>] (mount_block_root+0x1c4/0x204) from [<c000919c>] (prepare_namespace+0x154/0x1ac)
[<c000919c>] (prepare_namespace+0x154/0x1ac) from [<c0008784>] (kernel_init+0x114/0x15c)
[<c0008784>] (kernel_init+0x114/0x15c) from [<c002cf00>] (kernel_thread_exit+0x0/0x8)

Do someone have a glue what's the problem here?

Best regards

We put the /root in the mmcblk0p2,that is the second partition of our SD card,you need to change it for your file system.