It would seem to me that for some reason the page write or erase failed, 
causing yaffs to then go mark the block bad.

Since bad block marking uses page writing, and the page is otherwise erased 
(0xff) I would hunch that for some reason, the erase actually worked, but 
yaffs thought that it failed and thus decided to mark the block bad.

The only times I've seen a large failure like this have been due to a 
hardware error (bad soldering etc) or due to a broken software interface to 
the NAND chips.

-- CHarles


On Tuesday 20 April 2004 00:18, Skumar wrote:
> hi,
> has someone faced the problem where yaffs has marked many blocks bad?
> for me yaffs has marked almost 70% blocks bad.
> below i am attaching the data of page 0 of a block which is marked bad
> this is the data in the all pages of blocks which are marked bad
> notice the last row ***
>
> help needed
>
> Regards
> sharath
>
>  0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  10h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  20h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  30h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  40h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  50h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  60h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  70h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  80h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  90h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  a0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  b0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  c0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  d0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  e0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>  f0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 100h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 110h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 120h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 130h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 140h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 150h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 160h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 170h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 180h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 190h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 1a0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 1b0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 1c0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 1d0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 1e0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 1f0h:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> 200h:ff ff ff ff 00 00 ff ff ff ff ff ff ff ff ff ff
>
>
>
>
>
>
> ---------------------------------------------------------------------------
>------------ This mailing list is hosted by Toby Churchill open software
> (www.toby-churchill.org). If mailing list membership is no longer wanted
> you can remove yourself from the list by sending an email to
> yaffs-request@toby-churchill.org with the text "unsubscribe" (without the
> quotes) as the subject.

---------------------------------------------------------------------------------------
This mailing list is hosted by Toby Churchill open software (www.toby-churchill.org).
If mailing list membership is no longer wanted you can remove yourself from the list by 
sending an email to yaffs-request@toby-churchill.org with the text "unsubscribe" 
(without the quotes) as the subject.