All of lore.kernel.org
 help / color / mirror / Atom feed
* [U-Boot-Users] BDI/flash question
@ 2004-01-15  2:44 Ed Okerson
  2004-01-15  3:40 ` George G. Davis
  0 siblings, 1 reply; 4+ messages in thread
From: Ed Okerson @ 2004-01-15  2:44 UTC (permalink / raw)
  To: u-boot

After spending the time (and money) on getting the BDI2000 and u-boot
working on the DBAU1500 board, our hardware guys finally delivered me a
couple of our own design boards with Au1500 processors on them.  I
connected the BDI2000 to one of our boards, and when it wouldn't erase the
flash and after a call to the HW engineer, found out that it has a
different flash.  OK, changed the flash type to the correct one, and also
the bus width was changed to 16 as opposed to the 32 on the DBAU1500.  The
BDI will now erase and program the flash, but u-boot won't come up.  After
a bit of digging I found that after an erase the flash looks like this:

BDI>md 0xbfc00000
bfc00000 : 0000ffff 0000ffff 0000ffff 0000ffff  ................
bfc00010 : 0000ffff 0000ffff 0000ffff 0000ffff  ................
bfc00020 : 0000ffff 0000ffff 0000ffff 0000ffff  ................
bfc00030 : 0000ffff 0000ffff 0000ffff 0000ffff  ................

and on, and on.....

Does anyone have any idea what could cause this?  Our HW guy is pouring
over the schematics trying to find something, but I want to make sure it
isn't something stupid I did on the BDI2000 config.

Ed Okerson

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2004-01-15 16:54 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-01-15  2:44 [U-Boot-Users] BDI/flash question Ed Okerson
2004-01-15  3:40 ` George G. Davis
2004-01-15  5:03   ` Ed Okerson
2004-01-15 16:54     ` George G. Davis

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.