From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?QW5kcmVhcyBCaWXDn21hbm4=?= Date: Fri, 05 Apr 2013 11:15:36 +0200 Subject: [U-Boot] [PATCH v3 5/6] omap_gpmc: add support for hw assisted BCH8 In-Reply-To: <515E879C.5020906@gmail.com> References: <1365000650-1348-1-git-send-email-andreas.devel@googlemail.com> <1365000650-1348-2-git-send-email-andreas.devel@googlemail.com> <515E879C.5020906@gmail.com> Message-ID: <515E9638.3090300@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Thomas Weber, On 04/05/2013 10:13 AM, Thomas Weber wrote: > Hello Andreas, > > I have the following problem when switching from nandecc hw hamming to > nandecc hw bch8. > > Thomas > > -------8<---------- > U-Boot 2013.04-rc2-00006-g9abd2ec (Apr 05 2013 - 09:58:48) > > OMAP3530-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz > OMAP3 DevKit8000 + LPDDR/NAND > I2C: ready > DRAM: 128 MiB > NAND: 128 MiB > MMC: OMAP SD/MMC: 0 > *** Warning - bad CRC, using default environment > > In: serial > Out: serial > Err: serial > ethaddr not set, using Die ID > Die ID #1d82000400000000040365f90100b017 > Net: dm9000 > Hit any key to stop autoboot: 0 > OMAP3 DevKit8000 # nandecc hw bch8 > Unsupported HW ECC algorithm > OMAP3 DevKit8000 # nandecc hw bch8 > Unsupported HW ECC algorithm > OMAP3 DevKit8000 # nandecc hw hamming > 1-bit hamming HW ECC selected > OMAP3 DevKit8000 # nandecc sw > SW ECC selected > OMAP3 DevKit8000 # nandecc hw bch8 > Unsupported HW ECC algorithm > OMAP3 DevKit8000 # nandecc hw hamming > 1-bit hamming HW ECC selected > OMAP3 DevKit8000 # nandecc hw bch8 > Unsupported HW ECC algorithm > No ECC functions supplied; Hardware ECC not possible > BUG: failure at nand_base.c:3014/nand_scan_tail()! > BUG! You are right. I'v never tested the nandecc changes without the new CONFIG_NAND_OMAP_BCH8 config parameter, many thanks to you! I've a fix for that and will repost v4 ASAP. Best regards Andreas Bie?mann