Yes, WD,
After u-boot places the cramfs image to the expected location without wrapped by mkimage, the filesystem is mounted. (My uClinux port does not use MTD driver. Instead, it uses ramdisk driver to load cramfs image to ram. Hence, I now use u-boot cp command to copy cramfs image from flash to ram directly.) Originally, I hope to use mkimage to add header to cramfs image to gain crc32 check protection. Whatever, it is good to have one solution at least.
Thanks. Wayne
-----Original Message----- From: wd@denx.de [mailto:wd@denx.de] Sent: Friday, May 06, 2005 3:43 PM To: Wayne Lee Cc: 'u-boot-users' Subject: Re: [U-Boot-Users] mkimage parameters for cramfs.img
In message 200505060449.j464nU8R011009@ismp.csie.ncku.edu.tw you wrote:
mkimage -A arm -O linux -T ramdisk -C none -n "Cramfs Image" -a 0x02000000 -d cramfs.img ucramfs Image Name: Cramfs Image Created: Fri May 6 12:31:51 2005 Image Type: ARM Linux RAMDisk Image (uncompressed)
^^^^^^^^
This makes no sense. A cramfs image should go directly to flash, and be accessed through the Linux kernel's MTD layer. Treating it as a ramdisk is not a good idea.
However, the uClinux kernel cannot find the filesystem to mount.
Don't do this, then.
What is the correct mkimage parameters for cramfs.img ?
There is none. Only "initial ramdisks" are wrapped by mkimage; all other filesystem images go directly to flash. Use MTD to access these.
Best regards,
Wolfgang Denk