From: Peter Barada <peter.barada@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Re: nanddump shows all bad blocks
Date: Thu, 05 Apr 2012 15:16:10 -0400 [thread overview]
Message-ID: <4F7DEF7A.1090100@gmail.com> (raw)
In-Reply-To: <5D308BD40154E4439D82454FE483A50206619995@EVS4.nam.ci.root>
> When I do this:
> root:/> nanddump -l 0x20000 -s 0x60000 --bb=padbad -f testfile
> /dev/mtd0
>
> It shows that the ECC has failed, but I know there is good data in there
> as that I can read the data in uboot.
> 0x60000-0x7ffff holds my uboot environment.
>
> ECC failed: 429
> ECC corrected: 0
> Number of bad blocks: 4
> Number of bbt blocks: 0
> Block size 131072, page size 2048, OOB size 64
> Dumping data starting at 0x00060000 and ending at 0x00080000...
>
> My 'testfile' is full of 0xFFs as the option specifies (padbad: dump
> flash data, substituting 0xFF for any bad blocks).
>
> I know mtd0 is mapped to that partition:
> ...
> Creating 4 MTD partitions on "MT29F2G08ABAEAWP":
> 0x000000000000-0x000000080000 : "bootloader(nand)"
> 0x000000080000-0x000000880000 : "linux kernel(nand)"
> 0x000000880000-0x000006c80000 : "file system(nand)"
> 0x000006c80000-0x000010000000 : "file system(ubifs)"
> ...
>
> Any idea how I can make this work?
>
Sounds as if the kernel is using a different ECC method to read the data
than what u-boot used to write it...
--
Peter Barada
peter.barada@gmail.com
next prev parent reply other threads:[~2012-04-05 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 17:04 nanddump shows all bad blocks Bishop, Mark
2012-04-05 19:16 ` Peter Barada [this message]
2012-04-05 19:38 ` Bishop, Mark
2012-04-05 20:18 ` Bishop, Mark
2012-04-05 20:22 ` Bishop, Mark
2012-04-05 21:00 ` Mike Frysinger
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=4F7DEF7A.1090100@gmail.com \
--to=peter.barada@gmail.com \
--cc=linux-mtd@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