From: Andrew Lunn <andrew@lunn.ch>
To: David Vrabel <dvrabel@arcom.com>
Cc: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>,
ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] how to measure time from within flash_program_buf
Date: Tue, 23 May 2006 09:13:00 -0000 [thread overview]
Message-ID: <20060523091300.GA16080@lunn.ch> (raw)
In-Reply-To: <4472D055.8040201@arcom.com>
On Tue, May 23, 2006 at 10:05:25AM +0100, David Vrabel wrote:
> Neundorf, Alexander wrote:
> > Hi,
> >
> > in the Intel 28fxxx flash driver there is a timeout used, and this
> > timeout is specified as a simple loop which is executed 5000000
> > times. Now we have a fast processor and a slow flash, so for us this
> > timeout isn't big enough. We could simply increase the count, but
> > this still depends on flash and processor speed.
>
> I'd have suggested putting HAL_DELAY_US() macro calls in the loop. That
> would give you a lower bound on the timeout. However, I think it it has
> the same problem as HAL_CLOCK_READ() below.
>
> How about sticking a few more functions (like hal_delay_us) in .2ram ?
These functions are normally in the platform HAL, or varient HAL. So
you would have to change every target. A lot of work...
Also, i work on a target which has a reasonable amount of flash and
very little RAM. I don't want these functions in RAM because i don`t
have space for them and my flash driver does not require them.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2006-05-23 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 7:32 Neundorf, Alexander
2006-05-23 8:03 ` Andrew Lunn
2006-05-23 9:05 ` David Vrabel
2006-05-23 9:13 ` Andrew Lunn [this message]
2006-05-23 10:07 ` David Vrabel
2006-05-23 9:21 AW: " Neundorf, Alexander
2006-05-23 9:35 ` Andrew Lunn
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=20060523091300.GA16080@lunn.ch \
--to=andrew@lunn.ch \
--cc=Alexander.Neundorf@jenoptik.com \
--cc=dvrabel@arcom.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).