Installing interrupts for a custom driver

[Alberto Parnaso]

Thanks Dwaine for answering.. 
I also thought this may be a problem even though I install the interrupt after BSP Initialization. So I decided to undefined RTEMS_DRVMNG_STARTUP and also CONFIGURE_APPLICATION_NEEDS_CONSOLE_DRIVER so "_IO_Initialize" from bootcard does not look for UARTs and therefore console driver is not installed.

Starting up this way I also may read and write through the UART port but interrupt is still missing. I have tried to install the interrupt in different vectors:

old_handler = setvector((rtems_isr_entry)UARTInterruptHandler, (rtems_vector_number)0, 1);
old_handler = setvector((rtems_isr_entry)UARTInterruptHandler, (rtems_vector_number)1, 1);
old_handler = setvector((rtems_isr_entry)UARTInterruptHandler, (rtems_vector_number)2, 1);
old_handler = setvector((rtems_isr_entry)UARTInterruptHandler, (rtems_vector_number)3, 1);

just to check if I was miss understanding the vector number, but this did not work either...

Alberto.
 

________________________________
 De: "Molock, Dwaine S. (GSFC-5820)" <dwaine.s.molock at nasa.gov>
Para: "pafbat00 at yahoo.es" <pafbat00 at yahoo.es> 
CC: "rtems-users at rtems.org" <rtems-users at rtems.org> 
Enviado: Lunes 7 de abril de 2014 20:43
Asunto: Re: Installing interrupts for a custom driver
  

Alberto,

Its possible that you're unable to install your interrupt handler because of the APBUART console driver.

The APBUART console driver will auto detect all APBUARTs then configure and install its own interrupt handler.

You should look to see if its possible to configure the APBUART console driver to only the first APBUART and then you could write you own driver to handle the second APBUART.

Dwaine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20140408/0eefb592/attachment.html>