[Bug 1000109] How to handle hardware interrupts?

[bugzilla at ecoscentric dot com]

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1000109





------- Additional Comments From jifl@ecoscentric.com  2004-05-08 00:02 -------
I don't see any obvious problem with the code you've sent, assuming it does get
as far as attaching the interrupt. Does jj ever get incremented or is it just
the DSR that doesn't get called?

The RTC interrupt is also just an IRQ (IRQ0). Can you check that that works,
e.g. by doing a cyg_thread_delay. That will show that there is no intrinsic
problem witht the interrupt system in general.

Another thing to try is to _not_ start the eCos scheduler, but instead attach to
IRQ0 yourself to check if the problem is in your code instead. If the eCos
kernel scheduler can use the clock interrupt okay, but you can't, then that
would mean the problem is in your code.

BTW, you'll need to do:
    HAL_CLOCK_RESET( CYGNUM_HAL_INTERRUPT_RTC, CYGNUM_KERNEL_COUNTERS_RTC_PERIOD );
    Cyg_Interrupt::acknowledge_interrupt(CYGNUM_HAL_INTERRUPT_RTC);

first.




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.