Fw: corrupt my NAND flash device
Eugeny Mints
eugeny.mints at auriga.ru
Mon Aug 18 07:36:56 EDT 2003
Alex, all,
>Alex Samoutin samoutin at hotbox.ru
>Wed Jul 2 11:43:11 BST 2003
>Previous message: 2nd try: [PATCH] jffs2 on DOC
>Next message: Fw: corrupt my NAND flash device
>Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>Hi Thomas,
>Sorry for big delay with answer - I had no hardware to test. Now I got
my
>CerfCube 405ep back and can play with it.
>So I had two problems
> 1.. Write verify sometimes fail
> 2.. Write operation during erase sometimes cause data corruption
Could you please describe you test which detects the first problem? I
have the same, but it arises very seldom and unstable. I'd like to be
able to reproduce the bug predictably.
>Hardware details :
>- NAND chip Toshiba TC58256AFT
>- ALE/CLE and CE connected to GPIO
>- R/B pin connected to GPIO and I use ready function which reads it
pin.
>- I played with different timings - even slowest setting gets me the
same
>result
>1-st problem was solved by applying new MTD snapshot (Jun 26). It's
look
>like nand_deselect(); nand_select() fixes the problem.
It is interesting - this fix doesn't help me:( (I have MIPS Au1100 and
Toshiba TC58256AFTI )
More over, I discovered that fix proposed by David in the latests
(august) snapshots (reset before write command) hangs my system during
eraseall:(
>However after applying new MTD release the 2-nd problem still
remained.
>Then I comment out erase abort in nand_get_chip (as you suggested) and
it
>fixes my second problem!
>Could you remove this erase abort from MTD source? I think it will not
>affect much on efficiency.
My second problem is that system hangs if the device is filled once and
an attempt to re-use previously used sectors is made. Comment out erase
abort in nand_get_chip fixes my second problem too.
Regards,
Eugeny
More information about the linux-mtd
mailing list