Can ID the NAND chip, but every erase block is bad?

[Bill Gatliff]

David Woodhouse wrote:
> Take a closer look at how bad blocks were detected under 2.6.20.
>   

Found the problem.

I hacked the code to show me the bytes as they were being read from the
flash, and they were significantly different with my 2.6.32 kernel---
all zeros, in fact.  That led me to a bug in my cmd_ctrl code: I was
bailing out if the command was CMD_NONE, before writing anything to the
flash.  That causes some important bytes to get dropped, apparently.  :)


Thanks!


b.g.

-- 
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat at billgatliff.com