public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Michael Anburaj" <embeddedeng@hotmail.com>
To: satish@bvt.sc.sanyo.co.jp, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] isr routine does not invoke for RTC interrupt
Date: Wed, 17 Sep 2003 16:13:00 -0000	[thread overview]
Message-ID: <Law15-F50BGLiHtRleY0001ab19@hotmail.com> (raw)

Hi,

Interrupt controller Registers:
1. The corresponding Interrupt Mask bit could be set <or enable bit not set>
2. If there is a global interrupt Mask bit; could be set <or Global enable 
bit not set>
ARM core register:
3. I bit in CPSR set <ARM specific – IRQs disabled>.

-Mike.

>From: Satish Kumar <satish@bvt.sc.sanyo.co.jp>
>To: Satish Kumar 
><satish@bvt.sc.sanyo.co.jp>,ecos-discuss@sources.redhat.com
>Subject: Re: [ECOS] isr routine does not invoke for RTC interrupt
>Date: Wed, 17 Sep 2003 19:17:26 +0900
>
>Ok,
>      i have used the system timer and not the RTC..the interrupts are
>gettin generated , but the isr routines are not being called..what could
>be the reason..?
>
>thanks
>satish
>
>
>
>
>On Wed, 17 Sep 2003 12:14:16 +0200
>Andrew Lunn <andrew@lunn.ch> wrote:
>
> > On Wed, Sep 17, 2003 at 06:50:04PM +0900, Satish Kumar wrote:
> > >
> > > Hi,
> > >    i m testing this clocktruth.cxx in the kernel/tests/ directory
> > > to test my on-board timer. well i see that though the corresponding
> > > timer interrupt gets generated, the isr routine is not called..i don`t
> > > understand how to solve this problem.
> > >
> > >    also my RTC time period is set to 1, since it generates 1 sec
> > > timer interval for 1 Hz clock input. i m not sure were i have gone 
>wrong.
> > >
> > > plz feel free to ask details to answer my queries..
> >
> > RTC means real time clock. It gives you the time of day, 11.07 BST,
> > 17/09/2003.
> >
> > eCos does not use this sort of clock. eCos uses a plain timer. These
> > are generally a count down register clocked by a high speed
> > clock. When it reaches zero, it interrupts and reloads the
> > counter. eCos normally sets this up to generate 100 interrupts per
> > second.
> >
> > So you need to change you HAL so that i uses a timer and not the RTC.
> >
> >    Andrew
> >
> >
>
>--
>Satish Kumar <satish@bvt.sc.sanyo.co.jp>
>
>
>--
>Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
>and search the list archive: http://sources.redhat.com/ml/ecos-discuss
>

_________________________________________________________________
Fast, faster, fastest: Upgrade to Cable or DSL today!   
https://broadband.msn.com


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

             reply	other threads:[~2003-09-17 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 16:13 Michael Anburaj [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-18  7:32 Satish Kumar
2003-09-17  9:50 Satish Kumar
2003-09-17 10:14 ` Andrew Lunn
2003-09-17 10:17   ` Satish Kumar
2003-09-17 10:25     ` Andrew Lunn

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=Law15-F50BGLiHtRleY0001ab19@hotmail.com \
    --to=embeddedeng@hotmail.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=satish@bvt.sc.sanyo.co.jp \
    /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).