Re: [ECOS] Spurious interrupt

[Andrew Lunn <andrew at lunn dot ch>]

On Wed, Oct 08, 2003 at 02:09:56PM +0530, Mahesh wrote:
>  Hi,
>        
>  
>    I am using eCos for Arm pid target.I am using sid for printf's 
>  .I am working on PC only not on board.In my code i have 5 threads being 
>  created in cyg_user_start function.Alarm's are being used by the threads
>  for some tasks.I am using real time clock for alarms.tick function is
>  called after the scheduler is started,but once the first alarm is
>  triggered,tick function is not called at all.So my second
>  alarm(different from first one) is not triggering and the program is
>  getting stuck.
>  
>  The program is going into spurious INTR code.
>  What is this spurious interrupt?

A spurious interrupt is an interrupt which eCos does not have a
handler for. It does not know what to do with this interrupt. You need
to find out what interrupt vector its on and then find out why sid is
generating this interrupt.

>  Is this the reason for tick function not to be called and second alarm
>  not to be triggerd ?

Could be. You will have to fix the spurious interrupt problem and see.

      Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss