From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Spansion flash not detected by CFI driver
Date: Thu, 19 Apr 2007 18:52:43 -0500 [thread overview]
Message-ID: <462800CB.9010501@orkun.us> (raw)
In-Reply-To: <1177021509.23147.38.camel@localhost>
Shiju wrote:
> On Thu, 2007-19-04 at 17:13 -0500, Tolunay Orkun wrote:
>> Shiju wrote:
>>>> 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>
>>> After disabling the buffered writes, write timeout doesn't happen. ALso
>>> protect/unprotect works well when h/w protect is enabled. Is there a
>>> way to use buffered writes on this flash device.
>> Try disabling debug outputs in CFI driver. I've seen writes do fail when
>> debug output is enabled.
>>
> I tested disabling the debug outputs. Still writes and protect/unprotect
> fails if CFG_FLASH_USE_BUFFER_WRITE is defined.
Is this chip capable of buffer writes? It is a new chip. It is described
as Stacked Multo-chip Cellular RAM flash. I do not know. You will have
to debug a bit to find out why. If your debugging indicates something
that should be addressed in the driver please submit a patch...
Tolunay
next prev parent reply other threads:[~2007-04-19 23:52 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
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 [this message]
-- 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=462800CB.9010501@orkun.us \
--to=listmember@orkun.us \
--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