From: "Boulais, Marc-Andre" <maboulais@rheinmetall.ca>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: saveenv & erase with bad blocks present
Date: Mon, 9 Feb 2015 13:37:26 +0000 [thread overview]
Message-ID: <29A2697B0516A946B1023D5E798DFCF67BAB743C@mail-ying> (raw)
In-Reply-To: <20150209071849.GR12209@pengutronix.de>
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
....
And then the erase operation appeared to have succeeded. After doing a reset and reloading Barebox v15.02.0, if I modify the environment and then execute "saveenv", my changes do not appear to ve saved if I do another reset...I am starting to think there was indeed a bad block in the bareboxenv NAND partition...I am checking with Phytec now.
Marc-Andre
-----Original Message-----
From: Sascha Hauer [mailto:s.hauer@pengutronix.de]
Sent: February-09-15 2:19 AM
To: Boulais, Marc-Andre
Cc: barebox@lists.infradead.org
Subject: Re: saveenv & erase with bad blocks present
On Fri, Feb 06, 2015 at 05:03:59PM +0000, Boulais, Marc-Andre wrote:
> Ok, I did erase the nand0.bareboxenv partition and after a reset, partition size for the env looks good:
> barebox@Phytec phyCORE-OMAP4460:/ ls /dev/nand0.bareboxenv* -l
> crw------- 131072 /dev/nand0.bareboxenv.bb
> crw------- 131072 /dev/nand0.bareboxenv
> barebox@Phytec phyCORE-OMAP4460:/ loadenv -d -s loading environment
> from defaultenv barebox@Phytec phyCORE-OMAP4460:/ saveenv saving
> environment
>
> So I can now save the environment without errors. But if I edit the config file and then do "saveenv" and then I reset, my changes are not there anymore as if the saveenv didn't work.
>
> Furthermore, I have this message " wrong crc on env superblock" that appears in the boot output...
> What do you think ?
I'll try to reproduce that tomorrow.
Just to be sure: You applied the patches I posted to the list in the meantime. Is the barebox version flashed on your board the version with the patches applied or did you only start the fixed version second stage?
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
next prev parent reply other threads:[~2015-02-09 13:37 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 [this message]
2015-02-10 9:20 ` Sascha Hauer
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=29A2697B0516A946B1023D5E798DFCF67BAB743C@mail-ying \
--to=maboulais@rheinmetall.ca \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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