From: "Lukas Riezler" <lukas.riezler@gmx.net>
To: ecos-discuss@sourceware.org
Subject: [ECOS] RTC doesn't work?
Date: Tue, 28 May 2013 19:41:00 -0000 [thread overview]
Message-ID: <trinity-78dc2a4e-5962-421a-9887-8c6990220a88-1369770093004@3capp-gmx-bs31> (raw)
Hi ecos-guys :)
I've a question depending on the real time clock in eCos (I try a port for FM3).
It seems it isn't working!
The returned value of cyg_current_time() is always 0!
It also seemy cyg_thread_delay(100) doesn't work...
I tried a "hard" read of the value of the systick register, and this isn't 0!
while(1)
{
HAL_READ_UINT32(CYGARC_REG_SYSTICK_BASE+CYGARC_REG_SYSTICK_VALUE, timerVal0);
timerVal2= cyg_current_time();
printf("%u\n", timerVal0); //it's okay...i counts down!
printf("%u\n", timerVal1); //always 0 :-(
}
Any ideas where my problems are?
With kind regards, Lukas
--
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 reply other threads:[~2013-05-28 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 19:41 Lukas Riezler [this message]
2013-05-29 15:09 ` [ECOS] " Felix R
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=trinity-78dc2a4e-5962-421a-9887-8c6990220a88-1369770093004@3capp-gmx-bs31 \
--to=lukas.riezler@gmx.net \
--cc=ecos-discuss@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).