From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Configuring Spansion flash
Date: Fri, 14 Sep 2007 11:35:04 -0400 [thread overview]
Message-ID: <46EAAA28.7050608@smiths-aerospace.com> (raw)
In-Reply-To: <CE54F2377C0FB8439A290BF5A88BF13D0656791D@CHN-HCLT-EVS01.HCLT.CORP.HCL.IN>
Yasothabalan Ramaswamy-TLS,Chennai wrote:
> So how shall I proceed next Ben.
> Where and in which file this configuration is done?
>
> Whenever I trace out which flash is detected, it always gets detects as
> FLASH_UNKNOWN.
It would appear you have something misconfigured in your hardware or
u-boot software. We know basically zero about either, so you will have
to work the problem with only generic hints from the list.
Start by verifying the chip select to your flash part is being driven
properly.
Once you are sure your hardware is driving the flash OK, use u-boot
memory read and write commands to send the CFI manufacturer ID commands.
When you figure out how to do CFI commands manually so that the flash
responds, your misconfiguration of hardware/software should be very obvious.
The following message thread goes into more details, simply substitute
u-boot memory read/write commands for BDI configuration read/write commands.
<http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/31501/focus=31730>
Good luck,
gvb
next prev parent reply other threads:[~2007-09-14 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 14:21 [U-Boot-Users] Configuring Spansion flash Yasothabalan
2007-09-14 14:23 ` Ben Warren
2007-09-14 14:47 ` Yasothabalan
2007-09-14 15:00 ` Ben Warren
2007-09-14 15:12 ` Yasothabalan
2007-09-14 15:22 ` Ben Warren
2007-09-14 15:35 ` Jerry Van Baren [this message]
2007-09-17 6:52 ` Yasothabalan
2007-09-18 15:15 ` Ben Warren
2007-09-18 15:20 ` Yasothabalan
2007-09-18 15:30 ` Ben Warren
2007-09-18 19:17 ` Wolfgang Denk
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=46EAAA28.7050608@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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