From: Nick Garnett <nickg@ecoscentric.com>
To: Marcel Ovidiu Achim <marcel.achim@ovidius-ib.de>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] AT91 on EB55 DSR is started only once
Date: Thu, 19 May 2005 04:25:00 -0000 [thread overview]
Message-ID: <m364xgfpns.fsf@xl5.calivar.com> (raw)
In-Reply-To: <428AD5CA.4080900@ovidius-ib.de>
Marcel Ovidiu Achim <marcel.achim@ovidius-ib.de> writes:
> Dear all,
>
> I am experiencing some weird behaviour when trying to setup a timer
> interrupt on an EB55 board.
> I attached the relevant code below.
> What happens is that the DSR is started only once after init from main,
> and then never again, although the
> timer interrupt is shown to occur (on an ascilloscope).
> By accident I discovered that this can be fixed if I insert the
> following line in the DSR:
>
> HAL_READ_UINT32( AT91_TC1 + AT91_TC_SR, i );
>
> Although the read seems to have no impact of the content of the SR
> register,
> it seems to magically have the DSR activated again.
The timers need the SR register to be read to clear the interrupt,
although this does not seem to be documented. Take a look at the code
in eCos that sets up timer0 to generate clock interrupts.
> I could live fine with that, but then other external interrupts seem to
> considerably bring down overall system performance.
> What am I overseeing here? Can anyone please help?
I'm afraid I cannot help with these other interrupts, but I doubt that
they have anything to do with your timer. Try turning on assertions
and find out where they are coming from.
--
Nick Garnett eCos Kernel Architect
http://www.ecoscentric.com The eCos and RedBoot experts
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-05-18 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1DXzpq-0007Bq-00@mrelay.alturo.net>
2005-05-18 9:49 ` Marcel Ovidiu Achim
2005-05-18 10:11 ` Marcel Ovidiu Achim
2005-05-19 4:25 ` Nick Garnett [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=m364xgfpns.fsf@xl5.calivar.com \
--to=nickg@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=marcel.achim@ovidius-ib.de \
/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).