In message 3D9FDCA910DD4445896A0BE5ECF009D40176845A@bla.satyam.com you wrote:
and Device Integrity Test. For SDRAM each and every thing is OK, but for EEPROM and Flash Memory No such test Cases are their using which the user can check the correctness of these Devices at the command prompt. It would be highly appreciated if any one will describe the process of Flash memory and EEPROM Testing by modifying the U-Boot Code.
It is up to you to define your requirements that such tests must meet.
It makes no real sense to perform a write testing on flash memory, for example, as you must erase the flash to write it, and erase it again to write it again, and the fact that you can write it now is no guarantee that it is still erasable the next time.
U-Boot offers to check the integrity of the stiored data using CRC32 checksums; this is even integral part of the U-Boot images.
If you need more or other features: feel free to add those.
Best regards,
Wolfgang Denk