From: Robert Schwebel <r.schwebel@pengutronix.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Flash write problem on CSB226
Date: Wed, 28 Jan 2004 20:00:24 +0100 [thread overview]
Message-ID: <20040128190023.GV23652@pengutronix.de> (raw)
In-Reply-To: <40179180.7070608@imms.de>
On Wed, Jan 28, 2004 at 11:40:00AM +0100, Rolf Peukert wrote:
> we have installed U-boot on a CSB226 board with a PXA255 CPU and a
> bank of 2 Intel 28F128J3 flash chips (8M x 16bit each). There appeared
> to be a problem with the flash write function. It would stop after a
> few words, claiming "flash not erased". Closer inspection revealed,
> only one of the flashes was in read mode, the other was still in
> status mode.
Hmm, I havn't tested the CSB stuff for some time and I have only used it
with the old board containing the PXA250. As there was no real customer
project behind the board and I used it mainly for testing the network
chip I didn't investigate the flash stuff too deeply.
> There's one more thing I'm unsure about: Which is the right place to
> set the CPU clock? In boards/csb226/memsetup.S it is set to a default
> value. In cpu/pxa/start.S it is set to the configured CFG_CPUSPEED
> value, but memsetup is called after this.
Having just a short look into it it looks like a bug which didn't turn
up because I didn't have a faster processor at that time.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hornemannstra?e 12, 31137 Hildesheim, Germany
Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4
next prev parent reply other threads:[~2004-01-28 19:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 10:40 [U-Boot-Users] Flash write problem on CSB226 Rolf Peukert
2004-01-28 19:00 ` Robert Schwebel [this message]
2004-02-09 20:42 ` Wolfgang Denk
2004-02-10 6:23 ` Robert Schwebel
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=20040128190023.GV23652@pengutronix.de \
--to=r.schwebel@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.