Dear Rahanesh, In message <4ab0dfca.4040...@tataelxsi.co.in> you wrote: > > When i executed fw_printenv on an embedded board , it threw an error > > > IOCTL error : Cannot get MTD information!! Any idea why this error > occurred?
Well, looking in the source code, I see a single place with a similar error message: 786 rc = ioctl (fd, MEMGETINFO, &mtdinfo); 787 if (rc < 0) { 788 perror ("Cannot get MTD information"); 789 return -1; 790 } But then, the error message would be: Cannot get MTD information: XXX XXX XXX with "XXX XXX XXX" giving an explanation of what goes wrong. What was the "XXX XXX XXX" that got printed in your case? > The contents of config file which i used shown below > > > > # MTD device name Device offset Env. size Flash sector size > Number of sectors > /dev/mtd0 0x0000 0x1000 0x10000 Are you sure this is correct? Your environment size is only 4 KiB? And your flash secor size is 64 KiB? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de The so-called "desktop metaphor" of today's workstations is instead an "airplane-seat" metaphor. Anyone who has shuffled a lap full of papers while seated between two portly passengers will recognize the difference -- one can see only a very few things at once. - Fred Brooks, Jr. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot