All of lore.kernel.org
 help / color / mirror / Atom feed
From: Craig A. Vanderborgh <craigv@voxware.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Intel StrataFlash 28F128J3 vs. 28F256K3
Date: Tue, 21 Dec 2004 01:50:52 -0500	[thread overview]
Message-ID: <41C7C7CC.2040801@voxware.com> (raw)

Hello,

I am bringing up u-boot on a new revision of our board and I am having a 
problem with flash.  Both boards have share *exactly* the same 
schematic, with just one difference.  The newer board has 2 Intel 
28F256K3 flash chips in a single bank versus 2 Intel 28F128J3 flash 
chips in a single bank on the older board.

I am inexperienced with this flash stuff, so bear with me.  What I am 
seeing is very strange.  The board comes up, and everything works except 
flash.  u-boot comes up, serial works fine, DRAM works fine.  Flash does 
not work right.  Here is what I am seeing.

1. Using JTAG, I can program the 1st sector of flash successfully.  This 
works and I am using this mechanism to boot the board.
2. Using JTAG or u-boot flash commands, erasing appears to work for all 
sectors > sector 0.  Programming does NOT work.  The low-order bits (for 
bytes 1&2) are programmed correctly.  The high-order bits (for bytes 
3&4) are LOST, and thus every 32-bit word contains "ff" as the 
high-order bytes after programming.

I have made ABSOLUTELY CERTAIN that all my PXA register settings are 
correct.  The same flash code (within u-boot) works correctly on the 
older board (with the J3's).  I am very stuck - and I would appreciate 
some help.  I have spent a vast amount of time on this problem and I 
would dearly love any bone that might be tossed from the U-Boot gurus.

Thansk in advance,
craig vanderborgh
voxware incorporated

             reply	other threads:[~2004-12-21  6:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-21  6:50 Craig A. Vanderborgh [this message]
2004-12-21  8:02 ` [U-Boot-Users] Intel StrataFlash 28F128J3 vs. 28F256K3 Wolfgang Denk
2004-12-21 15:00 ` Robert Whaley

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=41C7C7CC.2040801@voxware.com \
    --to=craigv@voxware.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 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.