public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Matthias Weißer" <weisserm@arcor.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Add new NAND flash
Date: Fri, 01 Oct 2010 16:31:40 +0200	[thread overview]
Message-ID: <4CA5F0CC.3020901@arcor.de> (raw)

Hi

I would like to add a new NAND flash type to u-boot and have some 
problems with it. The type is

MT29F16G08CBABA
? Page size x8: 4320 bytes (4096 + 224 bytes)
? Block size: 256 pages (1024K + 56K bytes)
? Plane size: 2 planes x 1024 blocks per plane
? Device size: 16Gb: 2048 blocks

The NAND subsystem is configured as follows

#define CONFIG_NAND_MXC
#define CONFIG_NAND_MXC_V1_1
#define CONFIG_MXC_NAND_REGS_BASE	(0xBB000000)
#define CONFIG_SYS_MAX_NAND_DEVICE	1
#define CONFIG_SYS_NAND_BASE		(0xBB000000)
#define CONFIG_MXC_NAND_HWECC
#define CONFIG_SYS_NAND_LARGEPAGE

The NAND is connected (8 bit wide) to an iMX25 which is booting from 
NOR. So the NAND is only a mass storage device. I am able to read the ID 
of the chip.

2Ch 48h 04h 46h 85h

I then added the following entry to the nand_flash_ids[] table

{"NAND 2GiB 3,3V 8-bit",	0x48, 0, 2048, 0, LP_OPTIONS},

Before getting to the u-boot prompt I get the following message:

NAND:  NAND device: Manufacturer ID: 0x2c, Chip ID: 0x48 (Micron NAND 
2GiB 3,3V 8-bit)
NAND bus width 8 instead 16 bit

This is caused by bit 6 in id byte 4 which tells that the device is 16 
bit wide organized and the iMX specific part of the NAND system which 
tells the generic system that the device is connected via a 8 bit bus 
which is obviously correct as the flash chip only has 8 data lines.

Is there anything I am doing wrong here?

Thanks,
Matthias

             reply	other threads:[~2010-10-01 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01 14:31 Matthias Weißer [this message]
2010-10-01 19:52 ` [U-Boot] Add new NAND flash Scott Wood
2010-10-02 12:50   ` Matthias Weißer
2010-10-04 16:25     ` Scott Wood
2013-03-01  1:55       ` garyio
2013-03-05  1:04         ` Scott Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CA5F0CC.3020901@arcor.de \
    --to=weisserm@arcor.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox