From: Shawn <shawnxjin@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] ARM VersatilePB - Fixed flash support
Date: Thu, 14 Oct 2004 09:51:09 -0700 [thread overview]
Message-ID: <c3d0340b04101409512a20b628@mail.gmail.com> (raw)
In-Reply-To: <89A528FE6DB0FA44877BB2F05B846718013AE569@ZIPPY.Emea.Arm.com>
Philippe,
> > One issue I've encoutered is flash write timeout of a big
> > chunk of data (> 128KB). Write always times out no matter how
> > big the value of CFG_FLASH_WRITE_TOUT is. The issue hasn't
> > been solved yet. Any hints are appreciated.
>
> I have tried with removing the test for timeout in the write_data()
> routine, just looping on the status:
>
> while (((status = *addr) & (FPW) 0x00800080) != (FPW) 0x00800080) ;
>
> This worked fine for large amounts of data so the timeout value is
> probably too low. Let me know if this is the same with your setting.
Good try. I'm not sure if this is a decent fix. It's possible that
Flash write gets stuck in while loop if there is a real problem. It
may be other factor(s) that cause this problem. For example, timer is
not accurate?
Best regards,
-Shawn.
next prev parent reply other threads:[~2004-10-14 16:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 13:43 [U-Boot-Users] ARM VersatilePB - Fixed flash support Philippe Robin
2004-10-14 16:51 ` Shawn [this message]
2004-10-14 21:09 ` Wolfgang Denk
2004-10-15 23:01 ` [U-Boot-Users] CFG_HZ and get_timer() issue Shawn
2005-01-12 0:33 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2004-10-12 14:49 [U-Boot-Users] ARM VersatilePB - Fixed flash support Philippe Robin
2004-10-13 0:50 ` Shawn
2004-09-28 16:59 Philippe Robin
2004-10-11 22:47 ` Wolfgang Denk
2004-10-11 23:20 ` Shawn
2005-01-09 23:36 ` Wolfgang Denk
2005-01-10 17:56 ` Shawn Jin
2005-01-10 18:01 ` Shawn Jin
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=c3d0340b04101409512a20b628@mail.gmail.com \
--to=shawnxjin@gmail.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 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.