From: shafer <sh.workmail@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot CFI driver question
Date: Wed, 24 Oct 2007 12:58:28 -0700 (PDT) [thread overview]
Message-ID: <13393794.post@talk.nabble.com> (raw)
I am attempting to bring up a board with u-boot. I've so far been able to get
u-boot far enough along to get to the main prompt. I am having an issue
reading from and writing to the FLASH memory in my setup. For simplicity
sake my setup consists of an ARM920T processor, EEPROM (AM29040B) and 2
FLASH devices (S29GL256N...). U-boot resides in the EEPROM and I am able to
read/write to the EEPROM.
My non-EEPROM FLASH configuration consists of two devices. Both devices have
23 address pins and 16 data pins. I have routed the 23 address pins of the
ARM to both FLASH devices. However, I have routed the ARM?s lower 16 data
pins to one device and its upper 16 data pins to the second device. On paper
this should give me 8 Meg locations of 32 bits for a total of 32 Megs of
FLASH.
I have compiled u-boot to include the CFI driver. I am pretty certain that I
have setup the ARM through u-boot to use the proper chip select and
address/data bus. I believe this because when I issue an erase command from
the u-boot prompt I can see the correct chip select toggle and I see the
correct address and data pins wiggling.
My issue seems to be when I try to read/write to the FLAHS devices. For
example, when I issue the erase command u-boot spits back an error message.
Unfortunately, I am not able to tell you the exact error message at the
moment and I cannot remember the exact phrase.
Error message aside I suspect that I am have a problem because I have not
informed u-boot of this configuration. So my questions are:
1) Does u-boot inherently support a setup with a 32 bit data bus split
across two devices?
2) If so can someone point me to an example configuration file in u-boot to
get the cfi driver properly configured?
3) If not, has someone patched u-boot to handle this configuration?
Thanks for the help in advance.
--
View this message in context: http://www.nabble.com/u-boot-CFI-driver-question-tf4686656.html#a13393794
Sent from the Uboot - Users mailing list archive at Nabble.com.
next reply other threads:[~2007-10-24 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 19:58 shafer [this message]
2007-10-25 6:28 ` [U-Boot-Users] u-boot CFI driver question Martin Krause
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=13393794.post@talk.nabble.com \
--to=sh.workmail@gmail.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