Dear "Ioannis Kyriakopoulos",
In message SNT111-DS83CB13AA8D729B0D4A82FA79B0@phx.gbl you wrote:
OMAP3 beagleboard.org # setenv bootargs 'console=ttyS2,115200n8, root=/dev/ram0 rw initrd=0x81600000,8M, init=/linuxrc'
OMAP3 beagleboard.org # mmcinit; fatload mmc 0 0x80002000 uImage; fatload mmc 0 0x81600000 ramdisk.gz; bootm 0x80002000 0x81600000
This is obviously wrong, isn't it?
If you store the U-Boot image file with the file header and the ramdisk image as payload at address 0x81600000, you _cannot_ use the same address in the "initrd=0x81600000" argument, as this address is the image header and not the ramdisk.
And anyway - why are you passing "initrd=" at all? Which part of the documentation shows such an example? None, because it's wrong.
The weird thing is that by using the very same uImage and ramdisk.gz but without using the mkimage tool to convert ramdisk.gz to a U-boot compatible type and without passing the ramdisk.gz memory address at "bootm" command, the filesystem gets mounted and the kernel boots successfully.
I am not surprised.
Does anyone has any clue of what is getting wrong in the first case?
You pass incorrect parameters to the kernel.
Best regards,
Wolfgang Denk