public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] Question about time interrupt
@ 2000-11-24 18:23 ness
  2000-11-25  9:37 ` Jonathan Larmour
  0 siblings, 1 reply; 2+ messages in thread
From: ness @ 2000-11-24 18:23 UTC (permalink / raw)
  To: ecos-discuss

Hi all.
 We are working on plateform of vr4300-vrc4373. How does cpu handle
the interrupt in the sourcecode. And how to decide address of function
which is processing the interrupts. 
Many thanks!
 
pyxue  

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ECOS] Question about time interrupt
  2000-11-24 18:23 [ECOS] Question about time interrupt ness
@ 2000-11-25  9:37 ` Jonathan Larmour
  0 siblings, 0 replies; 2+ messages in thread
From: Jonathan Larmour @ 2000-11-25  9:37 UTC (permalink / raw)
  To: ness; +Cc: ecos-discuss

ness wrote:
> 
> Hi all.
>  We are working on plateform of vr4300-vrc4373. How does cpu handle
> the interrupt in the sourcecode. And how to decide address of function
> which is processing the interrupts.

When the eCos kernel is enabled, the timer interrupt is hooked using an
eCos interrupt object in kernel/VERSION/src/common/clock.cxx in the
Cyg_RealTimeClock class constructor. The vector used is
CYGNUM_HAL_INTERRUPT_RTC which is defined in
hal/mips/vrc4373/VERSION/include/plf_intr.h to be interrupt 5:

// The vector used by the Real time clock. The default here is to use
// interrupt 5, which is connected to the counter/comparator registers
// in many MIPS variants.

#ifndef CYGNUM_HAL_INTERRUPT_RTC
#define CYGNUM_HAL_INTERRUPT_RTC            CYGNUM_HAL_INTERRUPT_COMPARE
#endif

Note if you were writing an application, you would use the equivalent
kernel C API functions to enable the interrupt handler, and not the
"native" C++ interface used within the kernel in clock.cxx.

If you want to take over this particular interrupt yourself, then you will
not be able to use timeslicing or timer functions in the eCos kernel. If
you want to share the interrupt with the eCos kernel, simply use the eCos
kernel timer functions, alarms, etc. as described in the documentation.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-11-25  9:37 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-11-24 18:23 [ECOS] Question about time interrupt ness
2000-11-25  9:37 ` Jonathan Larmour

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).