From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Tue, 13 Sep 2011 17:53:09 -0500 Subject: [U-Boot] [PATCH 5/5] NAND: Add scrub.quiet command option In-Reply-To: <201109140041.30150.marek.vasut@gmail.com> References: <1315800250-19761-1-git-send-email-marek.vasut@gmail.com> <201109130302.16991.marek.vasut@gmail.com> <4E6FD793.4010906@freescale.com> <201109140041.30150.marek.vasut@gmail.com> Message-ID: <4E6FDED5.5080204@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 09/13/2011 05:41 PM, Marek Vasut wrote: >> Any chance you could blow the NAND_MEMBLOCK_MARKER_RESERVE fuse? :-) > > No, they are one-time programable. Delivering a "damaged" chip isn't a good > practice. I'd call it "fixed" rather than "damaged" -- they did throw in that fuse in case of "any defective ROM code in handling bad block marker byte swapping", and the entire concept is defective. But I agree that if you're delivering them to other developers, rather than as part of a final product, they might want to make that choice themselves. And who knows, blowing the fuse might expose other defects. >> Otherwise, I guess you do need to scrub. Have you complained to >> Freescale sales/support? > > In fact no. The BootROM is "broken" and I doubt they will be willing to do > anything about it. Probably not, but they should still hear about it, if only for the chance they'll do it right next time. -Scott