<?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: Interrupt priority in MPC 5602B in CodeWarrior for MCU</title>
    <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556474#M13142</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bengt,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you use CodeWarrior, there is macro in IntcInterrupts.c file called INTC_NESTED_INTERRUPT. If you want to preempt one interrupt by some other with higher priority, set this macro to 1.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/3339iEA2F1921B2AD865A/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you look at lines below in this file, you will find conditional compilation code. If INTC_NESTED_INTEERUPT is 1, part with prolog and epilog is used.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/3366iED55BA0A35412FDC/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About calling function in ISR, it depends on the implementation, but in general there is not any system problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have any other question, please feel free to write me back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Aug 2016 07:52:08 GMT</pubDate>
    <dc:creator>martin_kovar</dc:creator>
    <dc:date>2016-08-25T07:52:08Z</dc:date>
    <item>
      <title>Interrupt priority in MPC 5602B</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556473#M13141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have a problem where my timer interrupt (irq 30)&amp;nbsp;at priority 2 is not interrupted by an uart interrupt (irq 79)&amp;nbsp;with priority 6. Are there any special measures to be taken if this priority should work as expected. I'm calling another function from the timer ISR, is that OK?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2016 14:28:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556473#M13141</guid>
      <dc:creator>bengtandersson</dc:creator>
      <dc:date>2016-08-24T14:28:16Z</dc:date>
    </item>
    <item>
      <title>Re: Interrupt priority in MPC 5602B</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556474#M13142</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bengt,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you use CodeWarrior, there is macro in IntcInterrupts.c file called INTC_NESTED_INTERRUPT. If you want to preempt one interrupt by some other with higher priority, set this macro to 1.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/3339iEA2F1921B2AD865A/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you look at lines below in this file, you will find conditional compilation code. If INTC_NESTED_INTEERUPT is 1, part with prolog and epilog is used.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_2.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/3366iED55BA0A35412FDC/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_2.png" alt="pastedImage_2.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About calling function in ISR, it depends on the implementation, but in general there is not any system problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have any other question, please feel free to write me back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2016 07:52:08 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556474#M13142</guid>
      <dc:creator>martin_kovar</dc:creator>
      <dc:date>2016-08-25T07:52:08Z</dc:date>
    </item>
    <item>
      <title>Re: Interrupt priority in MPC 5602B</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556475#M13143</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Martin!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pretty obvious now that I know where to look :smileyhappy:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tested and works as expected!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards Bengt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Aug 2016 09:14:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556475#M13143</guid>
      <dc:creator>bengtandersson</dc:creator>
      <dc:date>2016-08-26T09:14:04Z</dc:date>
    </item>
    <item>
      <title>Re: Interrupt priority in MPC 5602B</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556476#M13144</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Martin!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have another question. Why&amp;nbsp;are nested interrupts not the default behavior&amp;nbsp;in CW? Is this feature not recommended?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards Bengt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Sep 2016 05:28:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556476#M13144</guid>
      <dc:creator>bengtandersson</dc:creator>
      <dc:date>2016-09-01T05:28:01Z</dc:date>
    </item>
    <item>
      <title>Re: Interrupt priority in MPC 5602B</title>
      <link>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556477#M13145</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Bengt,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not able to tell you, why nested interrupts are not default behavior, but there is no problem with this feature. From my point of view, you do not have to worry about it. Of course there should appear a problem if you incorrectly design the algorithm, but it is application dependent. I think you can definitely use nested interrupts, if it bring you some advantages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have any other questions, please feel free to write me back.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Martin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 01 Sep 2016 07:10:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/CodeWarrior-for-MCU/Interrupt-priority-in-MPC-5602B/m-p/556477#M13145</guid>
      <dc:creator>martin_kovar</dc:creator>
      <dc:date>2016-09-01T07:10:30Z</dc:date>
    </item>
  </channel>
</rss>

