wd at denx.de
Fri Jul 22 17:08:11 CEST 2005
In message <550E696EB903B74E84CF33CF8D64DFC206B153 at vlbse301.eu.infineon.com> you wrote:
> what is to be put in the bootargs?
The correct root device, of course.
> the error message is :
> Root-NFS : no NFS server available.
And what was the other boot messages?
> -setenv bootargs "root=/dev/mtdblock0 mem=128M ether=27,0,0xfc800000,0xfc800010,eth0 mtdparts=versatile:0x5c0000 at 0x1c0000(cramfs) video=vc:1-2clcdfb:"
Did the boot messages indcate that the kernel really created a MTD0
device as per your request? Did you enable command line partitioning
in your kernel configuration? Did you enable cramfs support in your
> -setenv bootargs "setenv bootargs root=/dev/mtdblock0 mtdparts=armflash.0:0x65d000 at 0x2200000(cramfs) ip=none mem=128 console=ttyAMA0 video=vc:1-2clcdfb:"
This is obviously wrong but the kernel will ignore the bogus
additional arguments "setenv" and "bootargs".
> my cramfs is in flash at address 0x341c0000 while the basis of my flash
> memory is 0x34000000.
And does your kernel acknowledge this?
[BTW: this has nothing to do with U-Boot and it off topic at least on
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"I haven't lost my mind - it's backed up on tape somewhere."
More information about the U-Boot