<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>isr_evt_set inside a uart interrupt not working</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/38464/isr_evt_set-inside-a-uart-interrupt-not-working</link><description> 
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</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: isr_evt_set inside a uart interrupt not working</title><link>https://community.arm.com/thread/101887?ContentTypeID=1</link><pubDate>Wed, 29 Jul 2009 18:51:19 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:7022ba6b-d9c1-47f6-a637-10b9c041bee0</guid><dc:creator>Hui J</dc:creator><description>&lt;p&gt;&lt;p&gt;
Hi all,&lt;/p&gt;

&lt;p&gt;
Thank you for your replys!&lt;/p&gt;

&lt;p&gt;
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.&lt;/p&gt;

&lt;p&gt;
Xiao&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: isr_evt_set inside a uart interrupt not working</title><link>https://community.arm.com/thread/89889?ContentTypeID=1</link><pubDate>Tue, 28 Jul 2009 13:58:27 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:763d4ec5-8957-405a-a335-94117afdd967</guid><dc:creator>ImPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
The waiting task will get one (1) signal to wake up. When it wakes
up, it should consume all data it can.&lt;/p&gt;

&lt;p&gt;
If you get another interrupt before the task has woken, it doesn&amp;#39;t
matter that only one event gets sent. The new character should be
queued, and when the task waits, it will process all characters
available.&lt;/p&gt;

&lt;p&gt;
If you get another interrupt after the task has woken and
processed all data, the task will return to the wait and immediately
get the event to process the new character.&lt;/p&gt;

&lt;p&gt;
If you get another interrupt after the task has woken but before
it has left the read loop, it will read this new character and on the
next wait call will be immediately woken but not find any data to
eat. No big problem.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: isr_evt_set inside a uart interrupt not working</title><link>https://community.arm.com/thread/56524?ContentTypeID=1</link><pubDate>Tue, 28 Jul 2009 12:58:23 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:239a684c-9f75-47c6-99c8-a3101becc880</guid><dc:creator>Jenny Turner</dc:creator><description>&lt;p&gt;&lt;p&gt;
Don&amp;#39;t think isr_evt_set buffers up multiple calls.&lt;/p&gt;

&lt;p&gt;
So you get a signal to say one or more signals have happened.&lt;/p&gt;

&lt;p&gt;
Don&amp;#39;t you?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>