From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Handling dual die and single die flash on same board
Date: Tue, 7 Sep 2010 19:26:04 +0200 [thread overview]
Message-ID: <201009071926.04557.sr@denx.de> (raw)
In-Reply-To: <4C8670EA.5010501@gmail.com>
Hi Chris,
On Tuesday 07 September 2010 19:05:46 Chris Packham wrote:
> I've run into a situation with a new design and I could use some pointers.
>
> Our hardware designers have built prototypes with different flash
> configurations. One possible configuration is a dual die 2x32MB the
> other is a single die 1x64MB.
>
> My u-boot config is currently setup for the 2x32MB case i.e.
> CONFIG_SYS_MAX_FLASH_BANKS = 2, CONFIG_SYS_FLASH_BANKS_LIST = {base,
> base+32MB}. The problem with this is that when flash_get_size is called
> on the 1x64 chip it discovers the same chip the 2nd time around and
> promptly walks off the end of the memory area I have allocated for it.
>
> Is there any existing way to make the cfi_flash driver handle this
> situation for me?
I just recently sent a patchset for the CFI driver that could help to handle
such a situation. Here the most interesting patch:
http://www.mail-archive.com/u-boot at lists.denx.de/msg37234.html
I would suggest to set CONFIG_SYS_MAX_FLASH_BANKS_DETECT to 2 and then add
some board specific code to determine the real bank count and set
cfi_flash_num_flash_banks accordingly.
Hope this helps.
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-09-07 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 17:05 [U-Boot] Handling dual die and single die flash on same board Chris Packham
2010-09-07 17:26 ` Stefan Roese [this message]
2010-09-07 22:05 ` Chris Packham
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=201009071926.04557.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox