<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>MQX Software Solutionsのトピックlwevent functionality in a task</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/lwevent-functionality-in-a-task/m-p/606326#M16753</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!!!!&lt;/P&gt;&lt;P&gt;I have som problems with _lewent_wait. I have a task that do two&amp;nbsp;things, First, configure some buttons (Enable, Disable in SW, in a uint8 variable) for request of other task (control task),; second, detect an event (pressed or released) and report it to control task. My problem is that if I use _lewent wait_ticks, the code blocks in only waiting an event, and doesn't read the messages of control task. Is there other way with the library of lwevent?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Norberto Jiménez&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Sep 2016 15:59:31 GMT</pubDate>
    <dc:creator>norbertoj</dc:creator>
    <dc:date>2016-09-09T15:59:31Z</dc:date>
    <item>
      <title>lwevent functionality in a task</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/lwevent-functionality-in-a-task/m-p/606326#M16753</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!!!!&lt;/P&gt;&lt;P&gt;I have som problems with _lewent_wait. I have a task that do two&amp;nbsp;things, First, configure some buttons (Enable, Disable in SW, in a uint8 variable) for request of other task (control task),; second, detect an event (pressed or released) and report it to control task. My problem is that if I use _lewent wait_ticks, the code blocks in only waiting an event, and doesn't read the messages of control task. Is there other way with the library of lwevent?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sincerely,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Norberto Jiménez&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Sep 2016 15:59:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/lwevent-functionality-in-a-task/m-p/606326#M16753</guid>
      <dc:creator>norbertoj</dc:creator>
      <dc:date>2016-09-09T15:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: lwevent functionality in a task</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/lwevent-functionality-in-a-task/m-p/606327#M16754</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Norberto:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes, waiting on event bit is a blocking call.&amp;nbsp; Any task can set or clear bits event field,&amp;nbsp; or interrupt service routine can also set or clear bits. once the condition specified to unblock&amp;nbsp; is being met, the task state will change from blocked to ready, and the scheduler will be called to see whether a context switch should be done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please refer to the following demo for lwevent usage.&lt;/P&gt;&lt;P&gt;C:\Freescale\Freescale_MQX_4_2\mqx\examples\lwevent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Sep 2016 06:28:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/lwevent-functionality-in-a-task/m-p/606327#M16754</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2016-09-12T06:28:12Z</dc:date>
    </item>
    <item>
      <title>Re: lwevent functionality in a task</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/lwevent-functionality-in-a-task/m-p/606328#M16755</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Daniel.&lt;/P&gt;&lt;P&gt;I have my task waiting for an event bit(&lt;STRONG&gt;_lwevent_wait_ticks()&amp;nbsp;&lt;/STRONG&gt;) from a function that check if a button is&amp;nbsp;pressed. I have another task that send a message (Create from &lt;STRONG&gt;_lwmsgq_init()&lt;/STRONG&gt; ) in order to configure some characteristics of the button. I don't know if there is a way to unlock the task without use&lt;STRONG&gt; _lwevent_set()&lt;/STRONG&gt;, like &lt;STRONG&gt;_task_ready()&lt;/STRONG&gt;. Or , Is better assigned another event bit, and get the mask event bits?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Norberto.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Sep 2016 22:52:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/lwevent-functionality-in-a-task/m-p/606328#M16755</guid>
      <dc:creator>norbertoj</dc:creator>
      <dc:date>2016-09-12T22:52:59Z</dc:date>
    </item>
  </channel>
</rss>

