Re: Interrupt on MV2302

[Marty Kraimer <mrk@aps.anl.gov>]

Weixing Cheng wrote:
> 
> hello, There has something with my system when using interrupt.
> The system is like this :
> Mv2302 CPU board + Avme9321 12 bit I/O card.
> I tried to use External Trigger of Avme9321 and wrote a simple pure vxWorks program:

...

> void isr()
> {
>  unsigned char * pointer;
>  pointer=Base_Addr+0x81;
>  *pointer=0x03;  /*int disable*/
>  sysIntDisable(4);
>  logMsg("The isr is running...\n");
>  *pointer=0x0B;  /*int enable*/
>  sysIntEnable(4);
>  return OK;
> }
> 
> make and ld it. run test() routine. and then I give a external trigger to Avme9321. the
> message is like this:
> 
> Interrupt: The isr is running
> Interrupt: The isr is running
> Interrupt: T
>                                          /* it seems the isr is runing, but only
>                                          last for several times and get a overflow message,
>                                           and reboot the system*/
> 
> WorkQPanic: Kernel work queue overflow        /* what does this mean? */



In this case the Kernel work queue overflow is most likely because the interrupt
is always pending.
Look at the documentation for the Avme9321. You probably have to access some
register in order to acknowledge the interrupt. Until you acknowledge the
interrupt it will continue being asserted even though your interrupt routine was
executed. For many devices just reading a data register is enough. Sometimes you
have to write to an interrupt acknowledge register.

For example the interrupt routine for the avme9444 is

STATIC void avme9440_isr(struct ioCard *pc)
{
   volatile struct avme9440                *p = pc->card;
   volatile unsigned char         intStatusLocal = p->intStatus;
   unsigned int                   chanNum;
   volatile unsigned char         intStatWrite = 0;

   for (chanNum=0; chanNum <= 7; chanNum++)
   {
      if(intStatusLocal & (1 << chanNum))
      {
         scanIoRequest(pc -> ioscanpvt[chanNum]);
         intStatWrite |= (1 << chanNum);
      }
   }

   p->intStatus = intStatWrite;
}

I will guess that the last instruction is what constitutes the interrupt
acknowledge.

Marty Kraimer