From: Peter Asemann <peter.asemann@web.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Not primarily u-boot related problem with Flash-RAM
Date: Fri, 13 May 2005 17:48:51 +0200 [thread overview]
Message-ID: <4284CC63.8080405@web.de> (raw)
Hi there!
I've a problem that is not really u-boot specific; in fact it rather
stands in my way to be able to use the U-Boot at all. I'm sorry for the
off-topic post, but as this list's topic is the one most close to
"bringing up boards" I hope you can help me a bit though:
I have a prototype board which has an MPC875 with 4 AM29LV320DB flash
chips on the bus (there also are 2 SDRAMs and an FPGA on the bus).
The board had a design flaw which made some buffers/level converters
which should convert the bus signal level to the signal level of a
PCMCIA adapter kind of burn out or at least disturb bus operations on
the data- as well as address-bus.
We've therefore removed the buffers/level converters, and now the busses
work, as we can see with a test program running on the FPGA (which
monitors the busses and draws block graphics of the last non-identical
32 bus states on a VGA display). That means, the MPC and the FPGA seem
to have survived what ever was wrong with the busses.
But though the busses seem to be okay now, the flash doesn't react to
the ident command sequence as it should, though I tried very defensive
clocking and stuff.
So the question is if you know typical mistakes which can cause
accessing flash to fail, or if you know that flash chips are well known
to go into pieces if there is something wrong with the busses connected
to them. Any hint will be appreciated.
Thanks for reading,
Peter Asemann
next reply other threads:[~2005-05-13 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 15:48 Peter Asemann [this message]
2005-05-13 16:05 ` [U-Boot-Users] Not primarily u-boot related problem with Flash-RAM richard at uclinux.net
2005-05-13 16:14 ` Wolfgang Denk
2005-05-13 19:13 ` Andrew Dyer
2005-05-17 16:27 ` Peter Asemann
2005-05-17 16:43 ` Wolfgang Denk
2005-05-17 19:58 ` Mark Rakes
2005-05-18 21:51 ` Peter Asemann
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=4284CC63.8080405@web.de \
--to=peter.asemann@web.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