mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Boulais, Marc-Andre" <maboulais@rheinmetall.ca>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: saveenv & erase with bad blocks present
Date: Tue, 10 Feb 2015 10:20:03 +0100	[thread overview]
Message-ID: <20150210092003.GW12209@pengutronix.de> (raw)
In-Reply-To: <29A2697B0516A946B1023D5E798DFCF67BAB743C@mail-ying>

Hi Marc-Andre,

I just sent an updated series for the nand issues. With this I tested
bootstrapping the board completly from SD card using the nand_bootstrap
script. I also tested 'saveenv' successfully.

On Mon, Feb 09, 2015 at 01:37:26PM +0000, Boulais, Marc-Andre wrote:
> Hi Sascha,
> I start the patched/fixed version in second stage. My PCM049 board is
> programmed with Phytec's BSP Barebox 2013.06.0. Upon entering its
> prompt, I start v 15.02.0 with your patches using tftp and bootm
> commands.
> 
> The "wrong crc on env superblock" message appears after I execute
> v15.02.0 with the bootm comand. It does not appear in the resident
> Barebox startup.
> 
> Note: The first time I tried your patches, I had this error message:
> nand_erase_nand: attempt to erase a bad block at page [...]
> 
> Since we were considering potential problems in the nand driver to
> cause a "false" bad block, I commented out the bad block check in
> function nand_erase_nand() (nand/nand_base.c):

>  	instr->state = MTD_ERASING;
> 
> 	while (len) {
> #if 0
> 		/* Check if we have a bad block, we do not erase bad blocks! */
> 		if (!mtd->allow_erasebad &&
> 				nand_block_checkbad(mtd, ((loff_t) page) <<
> 					chip->page_shift, 0, allowbbt)) {
> 			pr_warn("%s: attempt to erase a bad block at page 0x%08x\n",
> 				    __func__, page);
> 			instr->state = MTD_ERASE_FAILED;
> 			goto erase_exit;
> 		}
> #endif

The way to do this without sourcecode changes is to enable
CONFIG_NAND_ALLOW_ERASE_BAD and do a 'nand0.erasebad=1'

You should make sure to use a consistent barebox version state for both
the MLO and the full barebox later. Unfortunately the ECC layout
information and partition information of the NAND is stored in the
bootloader binaries and not on the device. This makes for a good source
of unpredictable errors.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-02-10  9:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 16:38 Boulais, Marc-Andre
2015-02-03 19:52 ` Uwe Kleine-König
2015-02-03 20:11 ` Sascha Hauer
2015-02-03 20:44   ` Boulais, Marc-Andre
2015-02-05 10:16     ` Sascha Hauer
2015-02-05 19:09       ` Boulais, Marc-Andre
2015-02-05 21:23         ` Sascha Hauer
2015-02-06 17:03           ` Boulais, Marc-Andre
2015-02-09  7:18             ` Sascha Hauer
2015-02-09 13:37               ` Boulais, Marc-Andre
2015-02-10  9:20                 ` Sascha Hauer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150210092003.GW12209@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=maboulais@rheinmetall.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox