intConnect(INUM_TO_IVEC (?),...)

[co...@ro.com]

Hello everyone,

First the HW:

MVME2307 (PPC604)
VXI chassis

I am trying to connect an isr to the appropriate vector number to allow our
board to receive vme interrupts and then launch the isr provided to the
vxworks call to intConnect(...)

I was hoping that someone has done the same thing on identical architecture or
a similar board. I have tried every vector number I can imagine, but when I
generate an interrupt using VICtext, I am always confronted with "bad vme
interrupt error message". I have yet to decide if the problem is with the
status/ID supplied from VICtext or something else. It is my understanding
that the vector number is not calculated by the interrupt handler until the
the IACK* signal is activated. As far as I can tell, this is not occurring,
(the bad vme interrupt will print indefinately until the interrupt is manually
deasserted). If anyone has any help to offer, it would be appreciated.

Chris Otto

further note: I HAVE initiated interrupts with sysIntEnable()

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/ Now offering spam-free web-based newsreading

[Erik Tijssen]

co...@ro.com wrote:

> Hello everyone,
>
> First the HW:
>
> MVME2307 (PPC604)
> VXI chassis
>
> I am trying to connect an isr to the appropriate vector number to allow our
> board to receive vme interrupts and then launch the isr provided to the
> vxworks call to intConnect(...)
>
> I was hoping that someone has done the same thing on identical architecture or
> a similar board. I have tried every vector number I can imagine, but when I
> generate an interrupt using VICtext, I am always confronted with "bad vme
> interrupt error message". I have yet to decide if the problem is with the
> status/ID supplied from VICtext or something else. It is my understanding
> that the vector number is not calculated by the interrupt handler until the
> the IACK* signal is activated. As far as I can tell, this is not occurring,
> (the bad vme interrupt will print indefinately until the interrupt is manually
> deasserted). If anyone has any help to offer, it would be appreciated.
>
> Chris Otto
>

Hey Chris,

Problem might be an offset of your IRQ0. I use a 486 bases board and use
interrupts. With my BSP, a variable COM1_INT_VEC was supplied to install an ISR
for the interrupt of COM1 (IRQ4). I've found out that in my case the offset is 20
hex.

I install the driver as follows: intConnect(INUM_TO_IVEC(COM1_INT_VEC, <ISR
name>,0)

That's all. I don't enable ints. This is done automatically by intConnect.

Good luck,

Erik Tijssen