John Tobias wrote: > Since, the ubl default block in DVFlasher is block 1, I modified the > DVFlasher to write the ubl data onto block 5 . By doing this, I can > dump the contents of the failing block since the DVFlasher won't > erase it. > > After making sure that the ubl would be written on block 5, I > re-program my device. Then, I modified my kernel to expose the ubl > block1 - block5 in linux userspace and from there, I dumped the > information of my failing ubl block and compare it to the working > copy.
You can also read/write NAND flash through JTAG. This is very useful when you have bricked your NAND. I have used a Ronetix PEEDI flash programmer a lot, it has a telnet interface and can read/write/erase things with or without OOB. I am now just setting up to use OpenOCD which now has Davinci NAND support. Also good for debugging bootloaders, etc. And dirt cheap interface hardware is available. -- Jon Povey [email protected] 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 [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
