This is the mail archive of the
mailing list for the SID project.
RE: [ECOS] generating interrupts in ARM-PID (SID simulator)
- From: Partha Palit <chessrook2001 at yahoo dot com>
- To: Robert Cragie <rcc at jennic dot com>, Andrew Lunn <andrew dot lunn at ascom dot ch>
- Cc: ECOS <ecos-discuss at sources dot redhat dot com>, SID <sid at sources dot redhat dot com>
- Date: Tue, 1 Jul 2003 13:50:14 -0700 (PDT)
- Subject: RE: [ECOS] generating interrupts in ARM-PID (SID simulator)
I am back again with questions on generating
As recommened by Robert, I tried using the interrupt
11.It seemed to work, but it showed up as spurious
interrupt which is not handled by the ARM Hal. I guess
this is becuase ARM recognizes level triggered
interrupts as pointed out by Robert.
-->Q: Could anyone kindly tell how to generate pulses
of definite time period using sid-sched? I guess a
timer can be used, but in the SID configuration file I
see that the timers have inputs from the cpu itself.
Is there anything simpler?
Also I had to manually generate the interrupt in the
SID tksm GUI. Otherwise it was not working.
-->Q: What am I doing wrong ? Can the duration of the
pulse be controlled in the GUI? Presently, I am just
changing the value in the sched-event field..and I get
a spurious interrupt.
Thanks a lot.
--- Robert Cragie <email@example.com> wrote:
> > > I am trying to generate external interrupts and
> > > it on a ARM-PID configuration. I am using SID as
> > > simulator for ARM PID.Ofcourse, eCos is my RTOS.
> > >
> > > >From the SID configuration file, I understand
> > > there is a interrupt controller which can be
> > > associated with 32 interrupts.One of the output
> > > of the interrupt controler is connected to the
> > > pin of the processor.
> > > I use one the the interrutpt sources numbered
> "16" to
> > > associate with an event whose occurance I want
> > > count.
> Only interrupts up to 15 can be handled by the
> interrupt controller (well,
> according to the PID manual anyway). Try connecting
> to interrupt number 11.
> This corresponds to the ASB0 interrupt, which seems
> to be unconnected in
> So in configrun-sid:
> connect-pin sensor-sched 1-event -> intrctrl
> However, note that the inputs to the ARM interrupt
> controller are level
> interrupts. If the scheduler generates a pulse, it
> could either get missed
> (short pulse) or cause continuous interruption
> problems (long pulse). So
> ideally in either case you'd want to latch the
> rising edge of the scheduler
> output and have some mechanism to clear the it in
> the DSR somehow. I'm not
> sure how you'd do this is SID, though.
> > > Now, the problem is that I am unable to catch
> > > interrupt and process it using an ISR.
> Specifically, I
> > > register my own ISR at the the vector 16.
> However, it
> > > seems that I am unable to catch the interrupt.
> > >
> > > Could anyone kindly advise where I am making the
> > > mistake? Also, I m unable to figure out that if
> > > how eCos can be configured to use the 32
> > > Afterall, there is only one nirq line. How are
> the 32
> > > interrupts mapped? When, I check the hal_intr.h
> > > I find that at max there can be 8 interrupts.
> Try something like the following to add a handler
> for interrupt number 11
> #include <cyg/kernel/kapi.h>
> #include <cyg/hal/hal_intr.h>
> /* IRQ handler object */
> typedef struct tagIRQ_s
> CYG_WORD tNum;
> cyg_interrupt sIRQrsrc;
> cyg_handle_t hIRQ;
> } IRQ_s;
> static IRQ_s s_sMyIRQ;
> /* snip */
> cyg_uint32 myISR(cyg_vector_t tVector,
> cyg_addrword_t tData)
> /* Nothing to do in ISR apart from the mandatory
> procedures */
> /* Stop any further interrupts until handled */
> /* Acknowledge to system (this MUST be done) */
> /* Cause DSR to be run */
> return CYG_ISR_CALL_DSR;
> cyg_uint32 myDSR(cyg_vector_t tVector, cyg_ucount32
> u32Count, cyg_addrword_t
> /* DO YOUR INTERRUPT PROCESSING HERE */
> /* Finally reenable interrupts */
> /* snip - somewhere in your initialisation .... */
> s_sMyIRQ.tNum = CYGNUM_HAL_INTERRUPT_ASB0; /* 11
> /* First, create and attach the Interrupt
> handlers */
> /* Interrupt number
> /* Priority - what
> goes here? */
> /* Data item passed
> to interrupt handler - whatever you want */
> /* ISR */
> /* DSR */
> /* (ptr. to)
> Handle - filled in */
> /* (ptr. to)
> Resource reqd. by interrupt */
> /* Finally, enable the interrupt */
> Hope this helps
> Robert Cragie, Design Engineer
> Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK
> http://www.jennic.com Tel: +44 (0) 114 281 2655
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!