From: Jonathan Larmour <jifl@eCosCentric.com>
To: Privat <PicassoCT@gmx.de>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Real Time Clock
Date: Fri, 01 Jan 2016 18:00:00 -0000 [thread overview]
Message-ID: <5686BEB9.5050606@eCosCentric.com> (raw)
In-Reply-To: <56728F18.1040409@gmx.de>
Privat wrote:
> Dear Ecos Developers and Maintainers,
>
> i have a question regarding the real time clock.
> I have a FreeSacle which runs at 116 Mhz, which means i have 1 000 000
> 000 ns / 116 000 000 or 8ns per cycle.
>
> I set the dividend to 1000, and the divisor to 116 which following the
> documentation (http://ecos.sourceware.org/docs-2.0/ref/kernel-clocks.html)
> - should always yield the ratio of ns between clock ticks.
> Unfortunatly that does not result in correct values.
The kernel real time clock doesn't run at 116 MHz though! The clock speed
for the processor is different from the clock you want the kernel to use
to measure time - the latter drives a clock interrupt that is used to
handle e.g. kernel alarms or timeslicing. You can't have a tick (and
therefore a clock interrupt) every CPU cycle :-).
You would need to set it to the number of nanoseconds per clock interrupt
you would get when the clock setting given by CYGNUM_HAL_RTC_PERIOD is
programmed into the PowerPC decrementer.
I don't know your HAL, but if it is derived from the MPC5554demo HAL,
which seems most likely, CYGNUM_HAL_RTC_PERIOD defaults to the expression
(CYGHWR_HAL_POWERPC_MPC55XX_FSYS/CYGNUM_HAL_RTC_DENOMINATOR) (with name
changed for you)
so that it becomes easy to make the denominator correspond to the kernel
clock frequency you want. In other words, if you want the standard 100Hz
kernel clock tick, you probably do indeed want to leave it as it is.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
--
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:[~2016-01-01 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 10:32 Privat
2015-12-17 11:15 ` Ilija Kocho [Илија Кочо]
2015-12-17 11:17 ` Privat
2016-01-01 18:00 ` Jonathan Larmour [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 11:42 James Yates
2003-10-23 12:03 ` Gary Thomas
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=5686BEB9.5050606@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=PicassoCT@gmx.de \
--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).