"Bad eraseblock" and "Failed ECC read"

Pramod P K pra.engr at gmail.com
Sun Jan 8 06:19:00 EST 2006


Thanks Josh.

> 1) This shows u-boot failing, not MTD/JFFS2.  This has been sent to
> the wrong list.

Sorry .. for less info...

Actually it fails at ECC of U-Boot.. Exactly at bad-block-table
creation step. Isnt it related to MTD?
Bt code is by someone from   linutronix.de

> 2)...
> what version of the kernel, what version of MTD, what board you are
> even using.

Linux- 2.6.10
Actually I dont know the version of the MTD.. sorry.. No body, even
who gave it knows !!!

Plz find attached log file

Thanks,
pramod


On 1/6/06, Josh Boyer <jwboyer at gmail.com> wrote:
> On 1/6/06, Pramod P K <pra.engr at gmail.com> wrote:
> > This is the MTD NAND with JFFS2 and after I flash I get:
> >
> >
> > My U-Boot v0.1
> >
> > .......
> >
> >
> > NAND device: Manufacturer ID: 0xec, Chip ID: 0xa1 (Samsung NAND 128MiB
> > 1,8V 8-bit)
> > Scanning device for bad blocks
> > ....
> > ....
> >
> > check_short_pattern: p[td->offs + i]: ff td->pattern[i]: ff
> >
> > ...
> >
> > check_short_pattern: p[td->offs + i]: 84 td->pattern[i]: ff
> > Bad eraseblock 96 at 0x00c00000
> >
> > td->len:2
> > check_short_pattern: p[td->offs + i]: 23 td->pattern[i]: ff
> > Bad eraseblock 97 at 0x00c20000
> >
> > .....
> >
> > NAND flash probing at 0x20020000 Finished
> > In:    console
> > Out:   console
> > Err:   console
> > Hit any key to stop autoboot:  2  1  0
> >
> > Loading from device 0: NAND 128MiB 1,8V 8-bit at 0x200b8000 (offset 0xd00000)
> >
> > .....
> >
> > : do_nandboot(): ecc_status=-1
> > nand_read_ecc: Failed ECC read, page 0x00001a00
> >
> > .....
> >
> > : do_nandboot(): ecc_status=-1
> > nand_read_ecc: Failed ECC read, page 0x00001a00
> >
> > ...
> >
> > ** Read error on 0
> > Boot reached stage -1
> >
> >
> >
> > Please come with the possibilities.
>
> 1) This shows u-boot failing, not MTD/JFFS2.  This has been sent to
> the wrong list.
>
> 2) The amount of information is so small that nobody would even know
> where to begin to look if it were a MTD/JFFS2 problem.  You don't say
> what version of the kernel, what version of MTD, what board you are
> even using.
>
> I seriously doubt anybody will even think of coming up with
> possiblities for you unless you give way more detailed information
> that is relevant to MTD/JFFS2.
>
> josh
>


--
----------------------------------------------------------------
  PRAMOD P. K.,
  pra.engr at gmail.com
  pra_engr at yahoo.co.in

  CDMA: 91- 9242195490.
----------------------------------------------------------------
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Jan5-630.txt
Url: http://lists.infradead.org/pipermail/linux-mtd/attachments/20060108/7630c390/attachment.txt 


More information about the linux-mtd mailing list