<?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: Tick Period &amp; not disabling a interrupt in MQX Software Solutions</title>
    <link>https://community.nxp.com/t5/MQX-Software-Solutions/Tick-Period-not-disabling-a-interrupt/m-p/188230#M3477</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Srikar,&lt;/P&gt;&lt;P&gt;Just thinking out loud without much thought into the subject.&lt;/P&gt;&lt;P&gt;You could raise the PIT1 interrupt level to be the highest in the system.&amp;nbsp; And use it as the incrementer for the RTOS TICK.&lt;/P&gt;&lt;P&gt;Ex: Every 10 PIT1 interrupts, increment the TICK and let its code run.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I haven't tried chaning the tick period but you should be able to do that.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 04 Mar 2011 06:30:21 GMT</pubDate>
    <dc:creator>DavidS</dc:creator>
    <dc:date>2011-03-04T06:30:21Z</dc:date>
    <item>
      <title>Tick Period &amp; not disabling a interrupt</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Tick-Period-not-disabling-a-interrupt/m-p/188229#M3476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can the value of 1 tick = 5msec, changed, i.e. increase or decrease its value?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also is there a way in MQX, where no one can disable a particular interrupt, because I have a periodic PIT1 interrupt at 500usec, which always needs to happen, it should never be missed,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After some analysis, I realized that I miss PIT1 interrupt, every 5 msec, which is the tick period.&lt;/P&gt;&lt;P&gt;I would assume that the scheduler runs every tick, and it will disable all interrupts to see if it has to scheudle or run a task.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have any inputs on this issue?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 03 Mar 2011 23:46:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Tick-Period-not-disabling-a-interrupt/m-p/188229#M3476</guid>
      <dc:creator>srikar</dc:creator>
      <dc:date>2011-03-03T23:46:06Z</dc:date>
    </item>
    <item>
      <title>Re: Tick Period &amp; not disabling a interrupt</title>
      <link>https://community.nxp.com/t5/MQX-Software-Solutions/Tick-Period-not-disabling-a-interrupt/m-p/188230#M3477</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Srikar,&lt;/P&gt;&lt;P&gt;Just thinking out loud without much thought into the subject.&lt;/P&gt;&lt;P&gt;You could raise the PIT1 interrupt level to be the highest in the system.&amp;nbsp; And use it as the incrementer for the RTOS TICK.&lt;/P&gt;&lt;P&gt;Ex: Every 10 PIT1 interrupts, increment the TICK and let its code run.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I haven't tried chaning the tick period but you should be able to do that.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Mar 2011 06:30:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MQX-Software-Solutions/Tick-Period-not-disabling-a-interrupt/m-p/188230#M3477</guid>
      <dc:creator>DavidS</dc:creator>
      <dc:date>2011-03-04T06:30:21Z</dc:date>
    </item>
  </channel>
</rss>

