public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] 16BIT SPANSION Flash writing problem with CFI Driver
Date: Mon, 20 Nov 2006 17:39:01 -0600	[thread overview]
Message-ID: <45623C95.30104@orkun.us> (raw)
In-Reply-To: <20061120104854.63524.qmail@web15915.mail.cnb.yahoo.com>

Sam Song wrote:
>> non-buffered writes I believe the write timeout of 0
>> may be the problem. Typically these values are set
>> to 0 if the feature is not supported but
>> the datasheet gives program sequence as well. Please
>> override the data read from CFI regarding write
>> timeout with a non zero value (say 1ms
>> timeout) and see what happens. Perhaps, they set the
>>     
>
> With this hacking way as suggested, it simply worked
> fine! I tried programming a 1.4MB files several times.
> No probelm.
>   

Glad to hear that the hack has worked.
> --- drivers/cfi_flash.c 17 Nov 2006 09:02:43 -0000    
>  1.2
> +++ drivers/cfi_flash.c 20 Nov 2006 03:41:43 -0000    
>  1.3
> @@ -1107,7 +1107,12 @@ ulong flash_get_size (ulong 
> +#ifndef CONFIG_S29GL064M
> info->write_tout = (tmp * (1 << flash_read_uchar
> (info, FLASH_OFFSET_WMAX_TOUT))) / 1000;
> +#else
> + info->write_tout = 1;   /* Suggested by Tolunay */
> +#endif /* CONFIG_S29GL064M  */
> +
>   
Instead of a chip specific solution we should try to find more
generalized solution. At minimum, we could always use 1 if the value
turns out to be 0 after calculation.

Or maybe we should examine the DQ7 toggle check to see if there is a
race condition. If there is a race condition there we should fix that
problem instead.

Best regards,
Tolunay

  reply	other threads:[~2006-11-20 23:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17  8:16 [U-Boot-Users] u-boot hanging Ram
2006-11-17 12:00 ` [U-Boot-Users] 16BIT SPANSION Flash writing problem with CFI Driver Sam Song
2006-11-17 16:40   ` Tolunay Orkun
2006-11-19 11:43     ` Sam Song
2006-11-19 19:27       ` Tolunay Orkun
2006-11-20 10:48         ` Sam Song
2006-11-20 23:39           ` Tolunay Orkun [this message]
2006-11-21  0:20             ` Andrew Dyer
2006-11-21  0:47               ` Andrew Dyer
2006-11-21  0:49               ` Tolunay Orkun
2006-11-21 13:25                 ` Sam Song
2006-11-21  0:52               ` Wolfgang Denk
2006-11-17 21:12 ` [U-Boot-Users] u-boot hanging Wolfgang Denk
2006-11-20  6:09   ` Ram
  -- strict thread matches above, loose matches on Subject: below --
2006-11-20 11:10 [U-Boot-Users] 16BIT SPANSION Flash writing problem with CFI Driver Bastos Fernandez Alexandre
2006-11-20 10:55 ` Sam Song

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=45623C95.30104@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