Comments

Hi John/Stephanie,
> The patch sets a few registers that Sascha's patches forgot. It also> correctly notices if there were ECC errors. Without the patch, most ECC> errors will go unnoticed.
I am having a issue with using nandwrite mtd util and it so happens
that the nandwrite gets stuck at a particular block and the sonsole
hangs there forever.
We are using the mx27(mxc) with a large size page NAND(4k). The annd
write suceeds for the kernel MTD parition. I am suspecting my NAND
driver is somehow obsolete. How do i find out as to what could be the
root cause of the problem?
What could be the pest debugging path?
Cheers,
Alfred.

Hi Alfred,
alfred steele a écrit :
> I am having a issue with using nandwrite mtd util and it so happens> that the nandwrite gets stuck at a particular block and the sonsole> hangs there forever.> We are using the mx27(mxc) with a large size page NAND(4k). The annd> write suceeds for the kernel MTD parition. I am suspecting my NAND> driver is somehow obsolete. How do i find out as to what could be the> root cause of the problem?
are you sure the i.MX27's NAND controler supports 4k NAND ?
From the Reference Manual is only support 512 & 2k :
The NFC interfaces standard NAND Flash devices to the IC and hides the
complexities of accessing the NAND Flash. It provides a glueless
interface to both 8-bit and 16-bit NAND Flash parts with page sizes
of 512 bytes or 2 Kbytes, and densities up to 64 Gbits per 2-Kbyte page
size NAND Flash, and 8 Gbits per 512 byte page size NAND Flash.
There is no mention of 4k NAND and the NFC's RAM buffer is only 2k + 64
which may be not enough for 4k NAND (the v2 NFC has 4k + 512 and support
4k).
Eric

Hi Alfred,
On 2009-12-13, alfred steele <alfred.jaquez@gmail.com> wrote:
> I am having a issue with using nandwrite mtd util and it so happens> that the nandwrite gets stuck at a particular block and the sonsole> hangs there forever.>> We are using the mx27(mxc) with a large size page NAND(4k). The annd> write suceeds for the kernel MTD parition. I am suspecting my NAND> driver is somehow obsolete. How do i find out as to what could be the> root cause of the problem?>> What could be the pest debugging path?
You may want to consider setting the kernel option MTD_DEBUG and setting
MTD_DEBUG_VERBOSE to 3 (noisy). It will generate a _lot_ of output on
the console, but may help you to identify where it is hanging.
John Ogness