public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Partha Palit <chessrook2001@yahoo.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: how to generate external interrupts
Date: Thu, 26 Jun 2003 22:47:00 -0000	[thread overview]
Message-ID: <20030626224659.41279.qmail@web12904.mail.yahoo.com> (raw)
In-Reply-To: <20030624191120.GC1520@redhat.com>

Hello,

Thank you Frank for showing the direction to
generating an external interrupt. 

Kindly advise if my approach is correct. I edited the
sid.conf as follows-

new sid-sched-sim sensor-sched

//then I set the num clients to 5...
//then connected the sched event to the intrctrl...

connect-pin sensor-sched 1-event -> intrctrl source-16

//then I appropriately set the 'regular' and 'time'
attributes.

The problem is that I am unable to catch the
interrupt.I am using eCos as the RTOS. In my program,
I register an ISR at "vector 16". Is this correct ? I
saw some memory mapping for the timers and UART in the
SID config file. Do I have to do somehing like that? 

Also, when I checked the eCos header file
(hal_intr.h), max interrupts were set to 8.If,possible
could you kindly comment on this?
P.S: my platform - ARM-PID.

Thanks for your time.

-Partha

--- "Frank Ch. Eigler" <fche@redhat.com> wrote:
> Hi -
> 
> > >How would you prefer to cause interrupts?
> > 
> > I want to simulate a periodic interrupt(
> specifically,
> > I want to be able to count the heart beats [...]
> 
> OK.
> 
> > Hence, I guess a script or a program would be
> > a suitable way to do it.
> 
> That's possible, but not necessary for this context.
> 
> Probably the easiest thing to do is to use one of
> the
> sid scheduler objects to supply the periodic
> interrupt.
> You would have to decide whether you would like
> these
> interrupts based on the progression of host (real)
> time,
> versus target (simulated) time.  Then, you'd pick a
> suitable time interval, in milliseconds or clock
> ticks
> respectively.  Then you'd arrange to get the chosen
> scheduler to send out a ping at the chosen interval
> to the appropriate interrupt input pin.  This latter
> bit is most easily done by emitting and editing the
> sid configuration file that otherwise models your
> desired system.
> 
> 
> > Presently,I am reading through the SID user
> manual. Is
> > there any other documentation, which can be
> helpful?
> 
> The other two families of documentation that you may
> find
> helpful consist of a guide on developing sid
> components and
> the set of individual component reference pages. 
> These may
> all be found on the sid project web page.
> 
> 
> - FChE
> 

> ATTACHMENT part 2 application/pgp-signature 



__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

  reply	other threads:[~2003-06-26 22:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20 21:17 error building SID Partha Palit
2003-06-20 21:31 ` Frank Ch. Eigler
     [not found]   ` <20030623211200.20420.qmail@web12903.mail.yahoo.com>
2003-06-24 16:18     ` how to generate external interrupts Frank Ch. Eigler
2003-06-24 19:01       ` Partha Palit
2003-06-24 20:26         ` Frank Ch. Eigler
2003-06-26 22:47           ` Partha Palit [this message]
2003-06-27  2:33             ` Frank Ch. Eigler

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=20030626224659.41279.qmail@web12904.mail.yahoo.com \
    --to=chessrook2001@yahoo.com \
    --cc=fche@redhat.com \
    --cc=sid@sources.redhat.com \
    /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).