From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] CFI driver and P33 64M flash
Date: Thu, 25 Sep 2008 19:08:19 +0300 [thread overview]
Message-ID: <48DBB773.9040301@embedded-sol.com> (raw)
In-Reply-To: <200809251653.30832.sr@denx.de>
Hi, Stefan
Stefan Roese wrote:
> On Thursday 25 September 2008, Felix Radensky wrote:
>
>> I'm running U-Boot 1.3.4 on custom 460EX based board,
>> equipped with 64M P33 flash (similar to Intel P30). See
>> http://www.numonyx.com/Documents/Datasheets/314749_P33_Discrete_DS.pdf
>>
>> This flash is comprised internally of two 32M flashes.
>>
>
> Then you have to define 2 physical chips in your U-Boot configuration.
>
>
>> I have the following declarations in configuration file:
>>
>> #define CFG_FLASH_CFI /* The flash is CFI compatible */
>> #define CFG_FLASH_CFI_DRIVER /* Use common CFI driver */
>>
>> #define CFG_FLASH_BANKS_LIST {CFG_FLASH_BASE}
>> #define CFG_MAX_FLASH_BANKS 1 /* max number of memory banks */
>>
>
> This will not work. Take a look at the lwmon5 configuration. It has a similar
> Intel FLASH which has two chips inside:
>
> #define CFG_FLASH0 0xFC000000
> #define CFG_FLASH1 0xF8000000
> #define CFG_FLASH_BANKS_LIST { CFG_FLASH1, CFG_FLASH0 }
>
> #define CFG_MAX_FLASH_BANKS 2
>
> ...
>
> You need to change the addresses for your 32MB version though.
>
Using 2 flash banks works fine. Thanks a lot for a prompt reply.
Felix.
next prev parent reply other threads:[~2008-09-25 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 13:50 [U-Boot] CFI driver and P33 64M flash Felix Radensky
2008-09-25 14:53 ` Stefan Roese
2008-09-25 15:52 ` Wolfgang Denk
2008-09-25 16:08 ` Felix Radensky [this message]
2009-08-04 20:48 ` psdof
-- strict thread matches above, loose matches on Subject: below --
2008-09-26 7:00 yusuf khan
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=48DBB773.9040301@embedded-sol.com \
--to=felix@embedded-sol.com \
--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