• Locked Locked
  • Replies 4 replies
  • Subscribers 119 subscribers
  • Views 3739 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is RTSM A9 uart interrupt ok?

liang hua
Note: This was originally posted on 15th August 2011 at http://forums.arm.com

I run sample code 'SW012-SW-00000-r1p0-00rel0.zip' on RTSM CortexMPCore, uart interrupt does not generate after inputs a command.
The sample code has a uart console. Uart input is processed in interrupt. First command input is ok, but after that, input is hung up.
If not using uart interrput, input and output is ok.
Parents
  • Arm Employee Badge
    Note: This was originally posted on 19th August 2011 at http://forums.arm.com

    Been tied up all week, and only just got a chance to look over my notes.

    So, what I remember is that there is a difference in the way the modelled UART and the real board.  The model sends an additional end of line character, which the ukernel doesn't seem to expect.  This lead to an overflow error in the UART.  With the vanilla code this meant that after the first UART based input you couldn't receive any more.  I fixed this by modifying the serial_init() function in ./arch/drivers/serial/serial.c so that the FIFO was enabled.  This prevented the overflow in the UART.
Reply
  • Arm Employee Badge
    Note: This was originally posted on 19th August 2011 at http://forums.arm.com

    Been tied up all week, and only just got a chance to look over my notes.

    So, what I remember is that there is a difference in the way the modelled UART and the real board.  The model sends an additional end of line character, which the ukernel doesn't seem to expect.  This lead to an overflow error in the UART.  With the vanilla code this meant that after the first UART based input you couldn't receive any more.  I fixed this by modifying the serial_init() function in ./arch/drivers/serial/serial.c so that the FIFO was enabled.  This prevented the overflow in the UART.
Children
No data