UART in RTEMS

[João Rasta]

Hmm catching interrupts with RTEMS for the UART2 was tricky since it uses
the trap value instead of the interrupt value so i had to do

rtems_interrupt_catch( UART_isr, (rtems_vector_number) 0x12,&old_handle );
LEON_Unmask_interrupt(2);

in order to get the interrupt working. However, once the handler runs, the
application seems to hang. the UART1, used for stdio, does not "printf"
anymore after the handler is called. Any clues why?


Best,
JM



On Mon, Aug 16, 2010 at 5:23 PM, João Rasta <freakforever at gmail.com> wrote:

> Hi,
>
> I re-compiled RTEMS with CONSOLE_USE_INTERRUPTS=1 but now i don't receive
> any UART messages. Can it be that LEON3 does not support interrupt mode?
>
>
> Best,
> JM
>
>
> On Thu, Aug 12, 2010 at 5:57 PM, João Rasta <freakforever at gmail.com>wrote:
>
>> No problem, any help is allways very much appreciated.
>>
>>
>> On Thu, Aug 12, 2010 at 5:45 PM, Joris van Rantwijk <jorisvr at sron.nl>wrote:
>>
>>> On Thursday 12 August 2010 18:24:16 João Rasta wrote:
>>> > Including leonuart.h results in a compilation error:
>>> >
>>> > ../src/comms/packet_lib/leonuart.h:57: warning: type defaults to 'int'
>>> in
>>> > declaration of 'amba_apb_device'
>>> > ../src/comms/packet_lib/leonuart.h:57: error: expected ';', ',' or ')'
>>> > before '*' token
>>>
>>> Right, sorry.
>>> I just looked at the gaisler.com version of RTEMS, and it appears that
>>> the interface to the AMBA bus has been redesigned. The leonuart driver
>>> will not work on your version of RTEMS.
>>>
>>> > Calling apbuart_register() also results an error: apbuart_register not
>>> > found. I have included apbuart.h.
>>>
>>> There seems to be a function called apbuart_register_drv() but I'm not
>>> sure how it works. It turns out that you are running a version of RTEMS
>>> that I have no experience with. Sorry for the confusion.
>>>
>>> Regards, Joris.
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20100817/a83adfcc/attachment-0001.html>