Problem with u-boot and flash MT29F16G08DAA

[Maupin, Chase]

In my testing that was enough to support 4K nand pages.  The only other thing that needed to change was that in nand_ids.c the older NAND chips can share the same device id as the new one.  Thus the new NAND chip is detected incorrectly and the page size is wrong.  i.e. for Samsung the NAND id for the 512MB nand chip was 0xd5 and the id for the new chip was 0xD5.  Since these are hex values the new chip was mistakenly detected as a 512MB part.  You may need to comment out the old part.

Lastly, there is a limitation in the nand_base.c code of 2GB for the total size of the nand chip.  This is because they use a signed value for the offset which causes bit extension during calculation of the nand chip to use for the offset.  Assuming this was fixed there is then a 4GB limitation in the MTD subsystem.

Still, to at least get 2GB of NAND with 4K page sizes all I needed to do was update the nand_ids.c file and increase the NAND_MAX_OOBSIZE variable to 128.

Sincerely,
Chase Maupin
Software Applications
Catalog DSP Products
e-mail: chase.maupin at ti.com
phone: (281) 274-3285

> -----Original Message-----
> From: Felipe Balbi [mailto:me at felipebalbi.com]
> Sent: Monday, December 15, 2008 2:29 PM
> To: Maupin, Chase
> Cc: me at felipebalbi.com; dbrownell at users.sourceforge.net; davinci-linux-
> open-source at linux.davincidsp.com
> Subject: Re: Problem with u-boot and flash MT29F16G08DAA
> 
> On Mon, Dec 15, 2008 at 02:19:24PM -0600, Maupin, Chase wrote:
> > You will definitely need to change the NAND_MAX_OOBSIZE to 128 for 4K
> pages.  You may also need to change the FFCHARS definition to 4096 to be
> safe.
> 
> sure, that's an easy guess. But is that really enough in the end ? I
> hope so :-)
> 
> --
> balbi