Steve Poulsen wrote: > 1) Use hexdump to view the first bit of the bootloader and note the > data values. 2) Load a filesystem into filesystem2. > 3) Use hexdump to view the first bit of the bootloader and note the > changes. 4) hexdump filesystem2 and search for the pattern. ( you > might dump it to NFS filesystem for easier searching)
Good suggestions - Krunal note if you try this first one, you may have to write a lot of data to filesystem2 before you see it overwrite the bootloader. If it's completely erased then writing about 512MB (0x20000000) should cross into the second chip select. But wear levelling abstration layers may move things around or leave gaps. I would try Steve's u-boot approach: > 1) In u-boot, use the nand commands to erase, write, and dump. You > should be able to narrow it down to "writing to block N causes block > M to also change". -- Jon Povey jon.po...@racelogic.co.uk Racelogic is a limited company registered in England. Registered number 2743719 . Registered Office Unit 10, Swan Business Centre, Osier Way, Buckingham, Bucks, MK18 1TB . The information contained in this electronic mail transmission is intended by Racelogic Ltd for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email so that the sender's address records can be corrected. The views expressed by the sender of this communication do not necessarily represent those of Racelogic Ltd. Please note that Racelogic reserves the right to monitor e-mail communications passing through its network _______________________________________________ Davinci-linux-open-source mailing list Davinci-linux-open-source@linux.davincidsp.com http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
