public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: wpa at fastmail.fm <wpa@fastmail.fm>
To: u-boot@lists.denx.de
Subject: [U-Boot] problem detecting CFI
Date: Thu, 01 Oct 2009 16:47:30 -0500	[thread overview]
Message-ID: <1254433650.30149.1337631127@webmail.messagingengine.com> (raw)

I have a working u-boot 2008.10 on a mips 32 board and am trying to port
it over to u-boot 2009.06.
So I used buildroot 2009.08 to build the tool chain for my mips32 board
as well as u-boot2009.06. I also copied the previous u-boot
initialization code to
initialize timer, serial port, ram and etc from u-boot 2008.10 to
2009.06.

Right now the problem is the new u-boot 2009.06 does not detect cfi of
the flash. I am pretty sure u-boot is running from SDRAM when the
problem happens because the address is in the range of SDRAM. Please let
me know if you have any suggestion - I am running out of ideas. I am
attaching the printout from both the working u-boot 2008.10 and u-boot
2009.06 below.

Thanks a lot.

U-Boot 2009.06 (Sep 30 2009 - 18:41:26)

Reset Cause: Hardware Reset
DRAM:  64 MB
Top of RAM usable for U-Boot at: 98000000
Reserving 139k for U-Boot at: 97fdc000
Reserving 4352k for malloc() at: 97b9c000
Reserving 36 Bytes for Board Info at: 97b9bfdc
Reserving 36 Bytes for Global Data at: 97b9bfb8
Reserving 128k for boot params() at: 97b7bfb8
Stack Pointer at: 97b7bf98
Now running in RAM - U-Boot at: 97fdc000
flash detect cfi
not found
flash detect cfi
not found


U-Boot 2008.10 (Sep 30 2009 - 11:37:03)

Reset Cause: Hardware Reset
DRAM:  64 MB
Top of RAM usable for U-Boot at: 98000000
Reserving 736k for U-Boot at: 97f44000
Reserving 4352k for malloc() at: 97b04000
Reserving 44 Bytes for Board Info at: 97b03fd4
Reserving 36 Bytes for Global Data at: 97b03fb0
Reserving 128k for boot params() at: 97ae3fb0
Stack Pointer at: 97ae3f98
Now running in RAM - U-Boot at: 97f44000
flash detect cfi
fwc addr b0000000 cmd f0 f0 8bit x 8 bit
fwc addr b0000000 cmd ff ff 8bit x 8 bit
fwc addr b0000055 cmd 98 98 8bit x 8 bit
is= cmd 51(Q) addr b0000010 is= 4f 51
fwc addr b0000555 cmd 98 98 8bit x 8 bit
is= cmd 51(Q) addr b0000010 is= 4f 51
fwc addr b0000000 cmd f0 f0f0 16bit x 8 bit
fwc addr b0000000 cmd ff ffff 16bit x 8 bit
fwc addr b00000aa cmd 98 9898 16bit x 8 bit
is= cmd 51(Q) addr b0000020 is= 5151 5151
is= cmd 52(R) addr b0000022 is= 5252 5252
is= cmd 59(Y) addr b0000024 is= 5959 5959
device interface is 2
found port 2 chip 1 port 16 bits chip 8 bits

             reply	other threads:[~2009-10-01 21:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-01 21:47 wpa at fastmail.fm [this message]
2009-10-01 23:25 ` [U-Boot] problem detecting CFI wpa at fastmail.fm
2009-10-02 21:42   ` wpa at fastmail.fm
2009-10-09 16:21 ` [U-Boot] MIPS cpu has " myuboot at fastmail.fm
     [not found]   ` <c166aa9f0910091016x6fe7bc77tc16222b6fb7c3c5d@mail.gmail.com>
     [not found]     ` <1255195660.1993.1339394551@webmail.messagingengine.com>
2009-10-10 20:47       ` Andrew Dyer
2009-10-12 15:10         ` myuboot at fastmail.fm
2009-10-12 22:11           ` Andrew Dyer
2009-10-12 22:28             ` Andrew Dyer

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=1254433650.30149.1337631127@webmail.messagingengine.com \
    --to=wpa@fastmail.fm \
    --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