From: ecalvo@2se.es <ecalvo@2se.es>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] tick timer doubt
Date: Fri, 22 Nov 2019 14:41:25 +0100 [thread overview]
Message-ID: <00a201d5a13a$89b42f80$9d1c8e80$@2se.es> (raw)
Hi!!
I have some doubts about the tick timer. Could someone help me? I explain
them below
* I don't understand really well the example of or1k timer control
that is in that file: For example, how is ticks variable updated?
* If it was updated, I understand that if frequency is 100Hz, a new
tick takes place each 0.01 seg and with 100 ticks, a second has elapsed.
However, If I compile and run this code and, and I open with gtkwave the
generated vcd, I don't understand why the value of TTMR register is 1000000.
Is The value of TTMR register fixed by software using or1k_timer_set_period
function? Is it measured in Hz?
Thanks in advance
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20191122/85f0c147/attachment.html>
next reply other threads:[~2019-11-22 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 13:41 ecalvo [this message]
2019-11-24 0:04 ` [OpenRISC] tick timer doubt Stafford Horne
2019-11-25 8:20 ` ecalvo
2019-11-25 9:22 ` Stafford Horne
2019-11-25 10:09 ` ecalvo
2019-11-25 13:03 ` Stafford Horne
2019-11-25 13:24 ` ecalvo
2019-11-25 23:12 ` Stafford Horne
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='00a201d5a13a$89b42f80$9d1c8e80$@2se.es' \
--to=ecalvo@2se.es \
--cc=openrisc@lists.librecores.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.