• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 21 subscribers
  • Views 806 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

isr_evt_set inside a uart interrupt not working

Xiao B

Hi All,

I am working on project using At91sam7s128 and have isr_evt_set(0x0001,TaskIDUSPort0) inside my uart interrupt.

Question is what will happen if another new uart interrupt occurs while I am processing in TaskIDUSPort0.
isr_evt_set(0x0001,TaskIDUSPort0) will send same event again, right?

It looks like isr_evt_set stops working after multiple hits.

Any comments are welcome!

Xiao

Parents
  • 0 in reply to ImPer Westermark

    Hi all,

    Thank you for your replys!

    The event (isr_evt_set) should be sent after the UART gets a byte with parity error. Normally, it should be only one interrupt in one complete frame. If something wrong in the incoming frame, it could have serveral bytes with parity error one right after the other. Most time these bytes (Interrupts) will stop the isr_evt_set. I can see that isr_evt_set is called (set break point), but the UART task gets nothing.

    Xiao

Reply
  • 0 in reply to ImPer Westermark

    Hi all,

    Thank you for your replys!

    The event (isr_evt_set) should be sent after the UART gets a byte with parity error. Normally, it should be only one interrupt in one complete frame. If something wrong in the incoming frame, it could have serveral bytes with parity error one right after the other. Most time these bytes (Interrupts) will stop the isr_evt_set. I can see that isr_evt_set is called (set break point), but the UART task gets nothing.

    Xiao

Children
No data