From: Jonathan Larmour <jlarmour@redhat.com>
To: Michaó Oleñczuk <olenczuk@rts.com.pl>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] clock resolution
Date: Mon, 23 Apr 2001 11:10:00 -0000 [thread overview]
Message-ID: <3AE4700F.19E70AC4@redhat.com> (raw)
In-Reply-To: <014701c0cbfa$f80f7900$1e00a8c0@OLENCZUK>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Micha³ Oleñczuk wrote:
>
> Hi,
> I am beginner in eCos programming and I have some problems:
>
> I want to set real time clock resolution to 1000 ticks/sec (or higher). Is
> it available to set it from software using cyg_clock_set_resolution() ?
> Setting dividend and divisor in cyg_resolution_t structure gives no effect
> (cyg_clock_get_resolution() gives the same before-setting resolution value
> =100).
> I changed it in eCos ConfigTool, and after calling
> cyg_clock_get_resolution() I got my setted resolution resolution, but some
> function like cyg_thread_delay() or alarm functions work the same as with
> default resolution value.
>
> How to get 1000 or more ticks for a second ????
Setting the resolution like that will just change the resolution that the
system *thinks* it is using, but it won't actually use it!
What you probably want to do is change the CYGNUM_HAL_RTC_PERIOD option in
the CDL of the HAL for your target. This value is used to program the timer
on your board (or the on-chip timer if appropriate), and therefore you'll
have to choose the correct value according to the documentation of your
processor/board.
You then change one or both of CYGNUM_HAL_RTC_NUMERATOR and
CYGNUM_HAL_RTC_DENOMINATOR to _reflect_ the change you just made.
For example to increase the frequency by a factor of ten, you may have to
(for example) reduce the ..._PERIOD option by a factor of 10, and then
increase the ..._DENOMINATOR option by a factor of 10.
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
prev parent reply other threads:[~2001-04-23 11:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 5:40 Micha&lstrok
2001-04-23 5:50 ` Gary Thomas
2001-04-23 11:10 ` 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=3AE4700F.19E70AC4@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=olenczuk@rts.com.pl \
/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).