Problem with mxc_nand driver
Jernej Turnsek
jernej.turnsek at gmail.com
Mon Sep 28 05:41:39 EDT 2009
Hi,
after writing root fs image into nand partition, running the image and
then checking the first empty block I've got following OOB data which
is suspicious to me:
OOB:
ff ff 85 19 03 20 ff ff
ff 65 02 08 00 00 00 ff
ff ff ff ff ff ff ff ff
ff ff 03 ff ff ff ff ff
ff ff ff ff ff ff ff ff
ff ff 03 ff ff ff ff ff
ff ff ff ff ff ff ff ff
ff ff 03 ff ff ff ff ff
One can see that bytes on offset 2 to 5 are not empty and when using
the smallpage_memorybased badblock_pattern byte 6 is not FF like it
should be.
Anyone knows what is going on here?
PS: for the not empty pages all first 6 bytes are FF.
BR,
Jernej
On Mon, Sep 28, 2009 at 11:20 AM, Eric Bénard <eric at eukrea.com> wrote:
> Hi,
>
> Jernej Turnsek a écrit :
>>
>> are you using HW ECC on your chip? I suspect that HW ECC is writting
>> something into space provided for the clean markers. I will
>> investigate to.
>>
> yes, I'm using HW ECC.
> static struct mxc_nand_platform_data eukrea_cpuimx27_nand_board_info = {
> .width = 1,
> .hw_ecc = 1,
> };
>
> In fact, maybe the change to the NAND driver should test hw_ecc as it
> shouldn't be necessary for software ecc.
>
> Eric
>
More information about the linux-arm-kernel
mailing list