From: Wolfgang Denk Date: Sun, 11 Jan 2009 14:28:43 +0100 Subject: [U-Boot] NAND bad environment block handling In-Reply-To: <1231672254.3130.29.camel@mobil.alm.archives.at> References: <247698.83293.qm@web33606.mail.mud.yahoo.com> <1231672254.3130.29.camel@mobil.alm.archives.at> Message-ID: <20090111132843.86CE0832E425@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Manfred, In message <1231672254.3130.29.camel@mobil.alm.archives.at> you wrote: > > 1. For our systems we assume, that the env-block never gets bad in > productive use, because the env-block is never written again. So we > reduced the problem to number of initial/factory bad blocks. That's a pretty risky setup because it is based on an incorrect assumption - on NAND, block become not only bad when being erased or written to, but also after a certain number of read operations is exceeded. Yes, there is a maximum number of reads per block on NAND! People like to ignore that... See for example the Micron Technical Note "Design and Use Considerations for NAND Flash Memory", http://download.micron.com/pdf/technotes/nand/tn2917.pdf Time to look into UBI, me thinks. 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: wd at denx.de No question is too silly to ask. Of course, some questions are too silly to to answer... - L. Wall & R. L. Schwartz, _Programming Perl_