<?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>topic Re: MQX 4.2 SCHEDULING CONFIGURATION in MQX Software Solutions</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-SCHEDULING-CONFIGURATION/m-p/926903#M18273</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anand.S&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;K66 is supported in MQX v5, please see below link for more details&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/pages/design/software/embedded-software/mqx-software-solutions/mqx-v5-software-solutions:MQX-V5?&amp;amp;tid=vanmqxv5" title="https://www.nxp.com/pages/design/software/embedded-software/mqx-software-solutions/mqx-v5-software-solutions:MQX-V5?&amp;amp;tid=vanmqxv5"&gt;MQX™ v5 Software Solutions | NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FIFO is the default scheduling policy for both MQX 4.0 &amp;amp; 4.2.&lt;/P&gt;&lt;P&gt;If you need to use Round Robin scheduling, you need to set the MQX_TIME_SLICE_TASK attribute in the task template. The task's time slice is determined by the value of the template's DEFAULT_TIME_SLICE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TASK_TEMPLATE_STRUCT MQX_template_list[] =&lt;BR /&gt;{&lt;BR /&gt;{ MAIN_TASK, world_task, 0x2000, 5, "world_task", MQX_AUTO_START_TASK, 0L, 0},&lt;BR /&gt;{ HELLO, hello_task, 0x2000, 5, "hello_task", MQX_TIME_SLICE_TASK, 0L, 100},&lt;BR /&gt;{ FLOAT, float_task, 0x2000, 5, "Float_task", MQX_AUTO_START_TASK |MQX_FLOATING_POINT_TASK, 0L, 0},&lt;BR /&gt;{ 0, 0, 0, 0, 0, 0, 0L, 0 }&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The hello_task task is a time slice task with a time slice of 100, in milliseconds. If the default compile-time configurations are used.&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>Thu, 01 Aug 2019 08:16:57 GMT</pubDate>
    <dc:creator>danielchen</dc:creator>
    <dc:date>2019-08-01T08:16:57Z</dc:date>
    <item>
      <title>MQX 4.2 SCHEDULING CONFIGURATION</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-SCHEDULING-CONFIGURATION/m-p/926902#M18272</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have doubts in mqx 4.2 scheduling. in our project we are using mqx4.0(for k60) due to code memory size issue we are moving project to K66. so switched mqx 4.0 to 4.2 as there is no support for K66 in mqx 4.0. Now we are facing issue in scheduling scheme. In mqx4.0 we are not using time slicing&amp;nbsp;MQX_HAS_TIME_SLICE to 0 if we do the same in mqx4.2 program controller resetting. in mqx4.0 we are using priority based event driven scheduling scheme .&lt;/P&gt;&lt;P&gt;is it possible to configure the same in mqx 4.2?&lt;/P&gt;&lt;P&gt;if it is possible please let me know how to configure?&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anand.S&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jul 2019 13:53:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-SCHEDULING-CONFIGURATION/m-p/926902#M18272</guid>
      <dc:creator>anand_s</dc:creator>
      <dc:date>2019-07-30T13:53:50Z</dc:date>
    </item>
    <item>
      <title>Re: MQX 4.2 SCHEDULING CONFIGURATION</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-SCHEDULING-CONFIGURATION/m-p/926903#M18273</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Anand.S&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;K66 is supported in MQX v5, please see below link for more details&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://www.nxp.com/pages/design/software/embedded-software/mqx-software-solutions/mqx-v5-software-solutions:MQX-V5?&amp;amp;tid=vanmqxv5" title="https://www.nxp.com/pages/design/software/embedded-software/mqx-software-solutions/mqx-v5-software-solutions:MQX-V5?&amp;amp;tid=vanmqxv5"&gt;MQX™ v5 Software Solutions | NXP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FIFO is the default scheduling policy for both MQX 4.0 &amp;amp; 4.2.&lt;/P&gt;&lt;P&gt;If you need to use Round Robin scheduling, you need to set the MQX_TIME_SLICE_TASK attribute in the task template. The task's time slice is determined by the value of the template's DEFAULT_TIME_SLICE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TASK_TEMPLATE_STRUCT MQX_template_list[] =&lt;BR /&gt;{&lt;BR /&gt;{ MAIN_TASK, world_task, 0x2000, 5, "world_task", MQX_AUTO_START_TASK, 0L, 0},&lt;BR /&gt;{ HELLO, hello_task, 0x2000, 5, "hello_task", MQX_TIME_SLICE_TASK, 0L, 100},&lt;BR /&gt;{ FLOAT, float_task, 0x2000, 5, "Float_task", MQX_AUTO_START_TASK |MQX_FLOATING_POINT_TASK, 0L, 0},&lt;BR /&gt;{ 0, 0, 0, 0, 0, 0, 0L, 0 }&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The hello_task task is a time slice task with a time slice of 100, in milliseconds. If the default compile-time configurations are used.&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>Thu, 01 Aug 2019 08:16:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/MQX-4-2-SCHEDULING-CONFIGURATION/m-p/926903#M18273</guid>
      <dc:creator>danielchen</dc:creator>
      <dc:date>2019-08-01T08:16:57Z</dc:date>
    </item>
  </channel>
</rss>

