Hi Lancer,If you look at drivers/mtd/maps/uclinux.c - you'll see there is some code in there that attempts to probe the root FS image to see how big it is.
My guess is that you are using CRAMFS as your root filesystem type? The default uclinux.c MTD map doesn't know how to probe CRAMFS, so it gets the size wrong.
The version of the uclinux.c MTD mapping in PetaLinux has been fixed to handle this. You can browse it here to compare:
http://developer.petalogix.com/browser/software/uClinux-2.4.x/drivers/mtd/maps/uclinux.cThe get_romfs_len() function is defined in the platform-specific machine.c - e.g.
http://developer.petalogix.com/browser/software/uClinux-2.4.x/arch/microblaze/platform/microblaze-auto/machine.c Regards, John Lancer Evo wrote:
Hi all,on my little system, with 1MB RAM and no flash, I can only activate the minimal settings. I've set a RAM disk of 96K (but I've tried 128K without positive outcome...).My start RAM address is 0x20000000, therefore the message uclinux[mtd]: RAM probe address=0x200c6a20is corrected second me. But when it says size=0x9b17f000 I think it's wrong. 9b17f000 in decimal is 2,42GB!!! Every time that I boot the board, the size is different, but always too much large!Why this boot error and how can I solve it?At the next instruction, uclinux[mtd]: root filesystem index=0 the system freeze!Many thanks Lancer ------------------------------------------------------------------------
___________________________ microblaze-uclinux mailing list microblaze-uclinux@xxxxxxxxxxxxxx Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/