[U-Boot-Users] Ramdisk with u-boot
dzu at denx.de
Wed Sep 24 17:02:56 CEST 2003
> I am trying to boot the linux kernel with ramdisk support.
> The details of the ramdisk image are
> Image Name: RAm Disk
> Created: Wed Sep 24 11:55:02 2003
> Image Type: ARM Linux RAMDisk Image (gzip compressed)
> Data Size: 3038830 Bytes = 2967.61 kB = 2.90 MB
> Load Address: 0x10800000
> Entry Point: 0x10800000
> The kernel is
> Image Name: Linux Kernel Image
> Created: Wed Sep 24 11:56:19 2003
> Image Type: ARM Linux Kernel Image (gzip compressed)
> Data Size: 686909 Bytes = 670.81 kB = 0.66 MB
> Load Address: 0x10C08000
> Entry Point: 0x10C08000
> The bootargs :
> setenv bootargs console=ttyS0,115200n8 initrd=0x10800000,8M root=/dev/ram
If you use U-Boot (at least on PowerPC) you do _not_ need an "initrd"
argument, the RAM disk address is passed by U-Boot for you if a second
parameter to bootm appears.
> The kernel is compiled with ramdisk support. I store my kernel in the flash
> at location 0x100000 and I download the ramdisk in the ram at location
> 0x10000000 ( this is starting of my RAM). Now when I boot the kernel with
> $ bootm 0x100000 0x10000000
You are aware that U-Boot takes its input in hexadecimal per default,
so this should rather be "bootm 100000 10000000". But as a kernel is
started this might be a copy and paste problem.
> I get the following error
> RAMDISK: Couldn'find valid RAM disk image starting at 0.
Address 0 - looks bogus.
> Freeing initrd memory: 8192K
> cramfs: wrong magic
> Kernel panic: Unable to mount root fs on 01:00
> Am I missing some thing in my steps ?? Any comments will be greatly
It would help a lot if you could provide us with a complete transcript
of the failing attempt.
Life is complex. It has real and imaginary components.
More information about the U-Boot