From: "Frank Ch. Eigler" <fche@redhat.com>
To: Partha Palit <chessrook2001@yahoo.com>
Cc: sid@sources.redhat.com
Subject: Re: how to generate external interrupts
Date: Fri, 27 Jun 2003 02:33:00 -0000 [thread overview]
Message-ID: <20030627023311.GA7068@redhat.com> (raw)
In-Reply-To: <20030626224659.41279.qmail@web12904.mail.yahoo.com>
Hi -
> [...]
> Kindly advise if my approach is correct. I edited the
> sid.conf as follows-
> new sid-sched-sim sensor-sched
This part is not necessary. You could reuse the existing
sim-sched-sim instance - just use a new unused client number.
(If were to use a new scheduler instance, you would have to
connect its upstream "advance" pin to an appropriate source.)
> //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.
All correct, I'm impressed!
> The problem is that I am unable to catch the
> interrupt.I am using eCos as the RTOS. [...]
> 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?
I am sorry, but I'm not familiar with that low-level aspect
of eCos. I suspect choosing a lower interrupt number would
help, as might putting breakpoints into eCos functions for
setting interrupt masks and dispatching received interrupts.
If you suspect a sid (rather than eCos) problem, consider
monitoring the interrupt controller with tksm, and manually
sending interrupts from the pin view.
> P.S: my platform - ARM-PID.
This suggests that you should be using the an arm-cpu
configuration for sid that includes models for selected
peripherals of the pid board, like the sid/pregen/arm-pid.conf
file. Sending a diff between that file and your modified
version would help diagnose problems in the future.
- FChE
prev parent reply other threads:[~2003-06-27 2:33 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
2003-06-27 2:33 ` Frank Ch. Eigler [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=20030627023311.GA7068@redhat.com \
--to=fche@redhat.com \
--cc=chessrook2001@yahoo.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).