<?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>i.MX ProcessorsのトピックemWin and FreeRTOS</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/emWin-and-FreeRTOS/m-p/1212373#M167823</link>
    <description>&lt;P&gt;I am using&amp;nbsp;&lt;SPAN&gt;i.MX&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;RT1064.&lt;/EM&gt; I have taken emWin from what has been included in&amp;nbsp;SDK_2.x_EVK-MIMXRT1064 version 2.8.0. When I am using FreeRTOS with multiple tasks (one taking care of touch, one emwin, one other sensors) with this environment, after calling GUIExec() (which returns just fine), it seems that another task does not get runtime anymore (it is waiting in xTaskNotifyWait). Otherwise I can see in the screen what I am supposed to, and changing emWin views works fine.&lt;/P&gt;&lt;P&gt;One thing I was wondering, is that the&amp;nbsp;GUI_X_ExecIdle is never called, although according to emwin specification GUI_X_ExecIdle&amp;nbsp; is "Called when there are no longer any messages which require processing. In this case the GUI is up to date."&lt;/P&gt;&lt;P&gt;Does anyone have ideas on this issue? Should FreeRTOS and emWin work together in&amp;nbsp;&lt;SPAN&gt;i.MX&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;RT1064?&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Jan 2021 12:02:46 GMT</pubDate>
    <dc:creator>Gamka</dc:creator>
    <dc:date>2021-01-15T12:02:46Z</dc:date>
    <item>
      <title>emWin and FreeRTOS</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/emWin-and-FreeRTOS/m-p/1212373#M167823</link>
      <description>&lt;P&gt;I am using&amp;nbsp;&lt;SPAN&gt;i.MX&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;RT1064.&lt;/EM&gt; I have taken emWin from what has been included in&amp;nbsp;SDK_2.x_EVK-MIMXRT1064 version 2.8.0. When I am using FreeRTOS with multiple tasks (one taking care of touch, one emwin, one other sensors) with this environment, after calling GUIExec() (which returns just fine), it seems that another task does not get runtime anymore (it is waiting in xTaskNotifyWait). Otherwise I can see in the screen what I am supposed to, and changing emWin views works fine.&lt;/P&gt;&lt;P&gt;One thing I was wondering, is that the&amp;nbsp;GUI_X_ExecIdle is never called, although according to emwin specification GUI_X_ExecIdle&amp;nbsp; is "Called when there are no longer any messages which require processing. In this case the GUI is up to date."&lt;/P&gt;&lt;P&gt;Does anyone have ideas on this issue? Should FreeRTOS and emWin work together in&amp;nbsp;&lt;SPAN&gt;i.MX&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;RT1064?&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2021 12:02:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/emWin-and-FreeRTOS/m-p/1212373#M167823</guid>
      <dc:creator>Gamka</dc:creator>
      <dc:date>2021-01-15T12:02:46Z</dc:date>
    </item>
    <item>
      <title>Re: emWin and FreeRTOS</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/emWin-and-FreeRTOS/m-p/1261107#M172503</link>
      <description>&lt;P&gt;Hi Gamka:&lt;/P&gt;
&lt;P&gt;Normally in a multiple tasks environment, the real time critical tasks will have the highest priorities. and the tasks which used for the user interface calling emWin functions, these tasks typically have low priorities in the system.&lt;/P&gt;
&lt;P&gt;I would suggest you adjust the priorities of your system first.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 08:27:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/emWin-and-FreeRTOS/m-p/1261107#M172503</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2021-04-13T08:27:30Z</dc:date>
    </item>
    <item>
      <title>Re: emWin and FreeRTOS</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/emWin-and-FreeRTOS/m-p/1261288#M172523</link>
      <description>&lt;P&gt;Hi!&lt;BR /&gt;&amp;nbsp;I was able to solve this issue, it was due to too small stack size.&lt;/P&gt;&lt;P&gt;Br, Gamka&lt;/P&gt;</description>
      <pubDate>Tue, 13 Apr 2021 12:40:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/emWin-and-FreeRTOS/m-p/1261288#M172523</guid>
      <dc:creator>Gamka</dc:creator>
      <dc:date>2021-04-13T12:40:27Z</dc:date>
    </item>
  </channel>
</rss>

