From: Rolf Peukert <rolf.peukert@imms.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Flash write problem on CSB226
Date: Wed, 28 Jan 2004 11:40:00 +0100 [thread overview]
Message-ID: <40179180.7070608@imms.de> (raw)
Hi,
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.
So I suspected the write_buff function in boards/csb226/flash.c (which
wrote the two chips sequentially as two 16-bit words) and modified it to
access both chips in parallel as 32 bit (the flash_erase function
already works this way).
The flash write problem seems to be gone now. Did anyone else experience
such problems, or is just our board equipped with particularly unequal
or pernickety flash chips?
In the attached patch, the old functions are just #ifdef'd out and could
be easily reactivated.
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.
Regards,
Rolf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: csb226-flash32.patch.gz
Type: application/x-gunzip
Size: 1930 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040128/6286b7b1/attachment.bin
next reply other threads:[~2004-01-28 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 10:40 Rolf Peukert [this message]
2004-01-28 19:00 ` [U-Boot-Users] Flash write problem on CSB226 Robert Schwebel
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=40179180.7070608@imms.de \
--to=rolf.peukert@imms.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