mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Kjell Ove Røte" <kjellove.rote@zenitel.com>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: FW: Handling boot on NAND Bad Blocks
Date: Thu, 23 Nov 2017 13:45:22 +0000	[thread overview]
Message-ID: <d8583e62109f4b9ebc7030799343b662@nooslMX1.zenitelcss.com> (raw)

Hi

We have a product on the Freescale imx28 booting from a NAND Flash.
Lately we have seen high numbers of boards failing, and find we have received batches with marked bad blocks in lower boot addresses of Flash.
Typically we see bad blocks in partition where Barebox are located. 

We do also use the barebox command "bcb" to create the Boot Control Block. 
I did just test that using two partitions for the bootstream, and adding these to BCB handles my problem with bad block in one bootstream partition.

I realize we will get into same problem for bareboxenv, kernel and devicetree partitions.
Is there any sort of built-in mechanism or best practice dealing with this? 
Or do I need to make redundant copy of all partition and verifications before load?

We are currently using a rather old Barebox 2013.01.0, which has been working perfectly fine for many years.

Example running an update command on a partition with one bad block below.

barebox@Stentofon Turbine:/ update -t bootstream -d nand -f sti_boot
host 10.5.2.152 is alive

erasing partition /dev/nand0.bootstream.bb

Skipping bad block at 0x00140000

flashing sti_boot to /dev/nand0.bootstream.bb

Regards, 
Kjell Ove

DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.

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

             reply	other threads:[~2017-11-23 13:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 13:45 Kjell Ove Røte [this message]
2017-11-23 17:12 ` Robert Schwebel
2017-11-24  8:49   ` Kjell Ove Røte
2017-11-30 21:43     ` Robert Schwebel
2017-12-04  8:49       ` Kjell Ove Røte

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=d8583e62109f4b9ebc7030799343b662@nooslMX1.zenitelcss.com \
    --to=kjellove.rote@zenitel.com \
    --cc=barebox@lists.infradead.org \
    /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