public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Privat <PicassoCT@gmx.de>
To: "Ilija Kocho [Илија Кочо]" <ilijak@siva.com.mk>,
	ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Real Time Clock
Date: Thu, 17 Dec 2015 11:17:00 -0000	[thread overview]
Message-ID: <567299BF.8010000@gmx.de> (raw)
In-Reply-To: <5672976A.9030806@siva.com.mk>

Its a MPC5668x ?

Am 17.12.2015 um 12:07 schrieb Ilija Kocho [Илија Кочо]:
> On 17.12.2015 11:31, 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.
> Is it a Kinetis?
>
>> 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.
>>
>> Strange as it sounds, the default works near perfect.
>> But reading the realtime clock resolution i got a dividend 1000000000
>> and a divisor of 1000 - which would be correct for a 100 Hz processor.
>>
>> Any help or advice is welcome. I would also like to know, how the system
>> is able to derive its own cyclerate.
>>
>> Regards Picasso
>>
>


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2015-12-17 11:17 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 [this message]
2016-01-01 18:00 ` Jonathan Larmour
  -- 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=567299BF.8010000@gmx.de \
    --to=picassoct@gmx.de \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=ilijak@siva.com.mk \
    /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).