public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Joachim Jaeger <maillist@fsforth.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] skipping bad blocks when erasing nand
Date: Fri, 14 Jul 2006 11:58:18 +0200	[thread overview]
Message-ID: <44B76ABA.3000607@fsforth.de> (raw)
In-Reply-To: <200607141047.08126.sr@denx.de>

Hi Stefan,

Stefan Roese wrote:
> Perhaps somebody else can jump in here and test the current linux mtd driver 
> behavior on a device with bad blocks. Thanks.

I only can provide the output based on the 2.6.12.5 kernel:

NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB
3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 4861 at 0x25fa0000
Bad eraseblock 5098 at 0x27d40000
Bad eraseblock 5163 at 0x28560000
Bad eraseblock 6252 at 0x30d80000
Bad eraseblock 7952 at 0x3e200000
Creating 3 MTD partitions on "NAND 1GiB 3,3V 8-bit":
0x00000000-0x00040000 : "u-boot"
0x00040000-0x00300000 : "kernel"
0x00300000-0x40000000 : "rootfs"

/ # mtd_debug erase /dev/mtd/2 0x22f00000 0x3000000
nand_erase: attempt to erase a bad block at page 0x0004bf40
MEMERASE: Input/output error

I think, bad blocks should not prevent U-Boot from erasing a partition,
which is needed to write an OS there, which needs to be booted.


Best regards
Joachim

-- 
Joachim Jaeger

FS Forth-Systeme GmbH
A DIGI International Company
Kueferstrasse 8
79206 Breisach
Germany
Phone: +49-7667-908-0
Fax: +49-7667-908-200
mailto:joachim_jaeger at digi.com
web: www.fsforth.de, www.digi.com

  parent reply	other threads:[~2006-07-14  9:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 22:21 [U-Boot-Users] skipping bad blocks when erasing nand David Byron
2006-07-13 22:45 ` Wolfgang Denk
2006-07-13 23:13   ` Dave Hylands
2006-07-14  7:10     ` Joachim Jaeger
2006-07-14  7:14   ` Stefan Roese
2006-07-14  8:28     ` Wolfgang Denk
2006-07-14  8:47       ` Stefan Roese
2006-07-14  9:29         ` Wolfgang Denk
2006-07-14  9:58         ` Joachim Jaeger [this message]
2006-07-14 11:19           ` Wolfgang Denk
2006-08-22  9:44             ` Ladislav Michl
  -- strict thread matches above, loose matches on Subject: below --
2006-07-17 21:42 David Byron
2006-07-20 23:22 ` Tolunay Orkun
2006-07-21  4:27   ` Stefan Roese
2006-07-13 21:35 David Byron
2006-07-13 21:48 ` Wolfgang Denk

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=44B76ABA.3000607@fsforth.de \
    --to=maillist@fsforth.de \
    --cc=u-boot@lists.denx.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