In message <EF9B29C78F41FA488927FCBC7750AF0E011DA5D1 at hyd-mdp-msg.wipro.com> you wrote: > > cramfs is 2.7MB where as the RAM size is 32MB. While building ofcourse > the RAMDISK size was told as 8MB. This I mentioned in the devrocket
What has the ramdisk to do here? Either you are using a cramfs filesystem, or a ramdisk (probably with an ext2 filesystem in it). Putting cramfs filesystem in a ramdisk image is a pretty bad idea. > Here I have one doubt while building the uBoot image using mkImage with > multi option where was the FileSystem image getting downloaded ? and how A multi-file image in U-Boot indeed requires a ramdisk image. Then you should not use a cramfs filesystem. The method for loading tha ramdisk image is described in the U-Boot "README" file; search for "positioning of initrd images". > the downloaded location was known to the kernel Image for pointing out > the File System image location. The options -a and -e are applicable > only for first image, isn't it? First image I mean the kernel Image. I Yes. Only the kernel is executable code and has an entry point. > YES. You are right I am building the image on x86 (Windows platform). > But I checked the build log it used the -r option. The default build was > cpio format and after that using fstool converting to CRAMS and the > option -r was present .I believe that devrocket of MountaVista has > makefiles specific to OS i.e for Windows, because while installation it > asks for what type of OS do you want to have the Image Development > environment. Maybe you should ask MV support, then. Best regards, Wolfgang Denk -- See us @ Embedded World, Nuremberg, Feb 22 - 24, Hall 10.0 Booth 310 Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de It is clear that the individual who persecutes a man, his brother, because he is not of the same opinion, is a monster. - Voltaire
