From: Shiju <shiju.mathew@amd.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Spansion flash not detected by CFI driver
Date: Thu, 19 Apr 2007 12:51:36 -0400 [thread overview]
Message-ID: <1177001496.23147.23.camel@localhost> (raw)
In-Reply-To: <1176997602.23147.13.camel@localhost>
On Thu, 2007-19-04 at 11:46 -0400, Shiju wrote:
> > > #define CFG_MAX_FLASH_BANKS 1
> > > #define CFG_MAX_FLASH_SECT 128
> > This is not correct for your chip. You should have this set not less
> > than the total number of ease units (blocks) on your chip.
> >
> > For what I could find on the net this chip seems to have the following
> > interesting geometry:
> >
> > 4 x 32kB
> > 254 x 128kB
> > 4 x 32kB
> >
> > So, the total should be at least 4 + 254 + 4 = 262
> >
> > Please fix this and provide the logs again...
> Thanks Tolunay,
> I could fix the flash detection after changing the total no: of sector
> to 262. But the flash unprotect sector always times out.The first 4
> sectors are protected when uboot comes up. I am not able to update uboot
> from within uboot since unprotect sectors always fails on these(all)
> sector. Should I need to change any timeout values.The log is as below.
>
> ### main_loop: bootcmd="run bootcmd_net"
> Hit any key to stop autoboot: 0
> uboot>
> uboot> protect off a0000000 +100000
> Flash unprotect timeout at address a0000000 data c68686c6
> .Flash unprotect timeout at address a0008000 data c68686c6
> .Flash unprotect timeout at address a0010000 data c68686c6
> .Flash unprotect timeout at address a0018000 data c68686c6
> .Flash unprotect timeout at address a0020000 data c68686c6
> .Flash unprotect timeout at address a0040000 data c68686c6
> .Flash unprotect timeout at address a0060000 data c68686c6
> .Flash unprotect timeout at address a0080000 data c68686c6
> .Flash unprotect timeout at address a00a0000 data c68686c6
> .Flash unprotect timeout at address a00c0000 data c68686c6
> .Flash unprotect timeout at address a00e0000 data c68686c6
> . done
> Un-Protected 11 sectors
> uboot>
I have another update. THe protect/unprotect failure was happening only
when I was using h/w protect enable. I disabled h/w protect to see
whether everything else goes well. But timeout happens on write as well.
Below is the log message.
uboot> cp.b 0x80000000 0xa0000000 $(filesize)
Copy to Flash... Flash buffer write timeout at address a0000000 data
c68686c6
Timeout writing to Flash
uboot>
Thanks,
Shiju
next prev parent reply other threads:[~2007-04-19 16:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 1:42 [U-Boot-Users] Spansion flash not detected by CFI driver Shiju Mathew
2007-04-19 2:06 ` Tolunay Orkun
2007-04-19 15:46 ` Shiju
2007-04-19 16:51 ` Shiju [this message]
2007-04-19 21:13 ` Shiju
2007-04-19 22:13 ` Tolunay Orkun
2007-04-19 22:25 ` Shiju
2007-04-19 23:52 ` Tolunay Orkun
-- strict thread matches above, loose matches on Subject: below --
2007-04-18 14:48 Shiju
2007-04-18 15:24 ` Wolfgang Denk
2007-04-18 15:59 ` Shiju
2007-04-17 23:15 Shiju Mathew
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=1177001496.23147.23.camel@localhost \
--to=shiju.mathew@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox