public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Andreas Bürgel <ab@genologic.de>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] timeout in flash_am29xxxxx.inl and SA1110
Date: Thu, 16 Aug 2001 06:56:00 -0000	[thread overview]
Message-ID: <3B7BD113.B11F5EFA@redhat.com> (raw)
In-Reply-To: <3B7B8250.E9933B1F@genologic.de>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]

Andreas Bürgel wrote:
> 
> Hi folks,
> 
> I'm using a custom SA1110 (206 MHz) board with four 29LV800B flash-chips
> - two parallel, two serial - and eCos-CVS version from yesterday (you
> know Jonathan ;). When starting the command "fis init -f" in redboot,
> the flash-driver made it to erase the first two blocks and then hanged.
> I found out that the timeout-value in "flash_erase()" at the following
> location is to small.
> 
> ...
> // Then wait for erase completion.
> if (FLASH_ERR_OK == res) {
>   timeout = 5000000;
>   while (true) {
>     state = *b_v;
>     if (FLASH_BlankValue == state) {
>       break;
>   }
> ...
> 
> I changed it to 10000000 and got all blocks erased (at least those of
> the first two flash-chips, but that's another problem).

Yes, we really need a "bogomip" calibration loop in eCos that can be used
for simple timeouts like this. In the meantime, I'll double it like you
suggest, although it'll go wrong when 400Mhz CPUs use it :-|.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

      reply	other threads:[~2001-08-16  6:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16  1:20 Andreas Bürgel
2001-08-16  6:56 ` Jonathan Larmour [this message]

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=3B7BD113.B11F5EFA@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ab@genologic.de \
    --cc=ecos-discuss@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).