From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Multiple chip support in ndfc driver
Date: Mon, 6 Dec 2010 11:09:36 +0100 [thread overview]
Message-ID: <201012061109.36445.sr@denx.de> (raw)
In-Reply-To: <4CFBA136.9030808@embedded-sol.com>
Hi Felix,
On Sunday 05 December 2010 15:27:02 Felix Radensky wrote:
> On a custom 460EX board I have a 2Gbyte NAND device, 1Gbyte per chip
> select. I'm trying to enable support for the second NAND CS, so far
> without success.
>
> U-Boot properly detects both devices, (manufacturer, size, bus width).
> First device
> works as expected, on second device bad blocks are reported correctly,
> but attempt
> to erase the device results in I/O errors on every block. The bank
> settings are identical
> for both chips.
>
> What am I missing ?
Perhaps a misconfiguration in your board config header? How did you configure
the NAND driver? Take a look at DU440.h or bamboo.h for example. Those boards
use multiple NAND devices.
> BTW, I was wandering why NAND TLB window size on Canyonlands is 16Mbytes.
Yes. This TLB could be smaller. 1KiB should be enough. Patch welcome. ;)
> Also, why NAND start address for TLB mapping is calculated as
> CONFIG_SYS_NAND_ADDR + CONFIG_SYS_NAND_CS
This is because of the NAND booting config option. NOR booting Canyonlands has
NAND conntected to chip-select 3 and NAND booting has it connected to chip-
select 0. And the lower 2 bits (value 0...3) of CONFIG_SYS_NAND_BASE are used
to configure the chip-select the NAND device is connected to (see ndfc.c for
more details).
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2010-12-06 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 14:27 [U-Boot] Multiple chip support in ndfc driver Felix Radensky
2010-12-06 10:09 ` Stefan Roese [this message]
2010-12-07 10:50 ` Felix Radensky
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=201012061109.36445.sr@denx.de \
--to=sr@denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.