dangerous NAND_BBT_SCANBYTE1AND6

[Matthieu CASTET]

Hi,

Brian Norris a écrit :
> Hi
> 
> On 4/21/2011 8:52 AM, Matthieu CASTET wrote:
>>
>> [1]
>> The devices are supplied with all the locations inside valid blocks erased
>> (FFh). The Bad
>> Block Information is written prior to shipping. Any block, where the 1st and 6th
>> Bytes, or 1st
>> Word, in the spare area of the 1st page, does not contain FFh, is a Bad Block.
> 
> I've tried my best to verify that any modifications I have made to bad 
> block scanning comply with the data sheets, but I very well could have 
> made mistakes (especially since there are so many different types of 
> scanning patterns, and very few manufacturers are actually being 
> consistent with these things).
Did you ask some clarification to manufacturers ?

> 
> That being said, I believe that the data sheet you quoted has some answer:
> "Any block, where the 1st and 6th Bytes, or 1st Word, in the spare area 
> of the 1st page, does not contain FFh, is a Bad Block."
> AFAICT, this description means that x8 buswidth devices must scan bytes 
> 1 and 6 while x16 devices only need to scan the first word. 
Did you see real case where 6 was not 0xff but 1 was 0xff ?


> So I bet 
> your device is actually an x8 device and so the 1st/6th byte pattern is 
> correct. I think the fact that this conflicts with your ECC patterns is 
> something you must deal with.
I don't agree, that's a big mtd regression. If you update your kernel on such
flash, you brick it.


Matthieu