<?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: MPC5566 Interrupts in Other NXP Products</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/MPC5566-Interrupts/m-p/146125#M342</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi Sas,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As far as I have understand this subject (I am transitionning from the MPC555 to the MPC5554 :smileywink: the software vector mode is a king of MPC5XX compatibility mode, wether the hardware mode offers better performance by handling in hardware some of the work that used to be done by software...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 04 Feb 2009 18:35:29 GMT</pubDate>
    <dc:creator>JChMathae</dc:creator>
    <dc:date>2009-02-04T18:35:29Z</dc:date>
    <item>
      <title>MPC5566 Interrupts</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/MPC5566-Interrupts/m-p/146124#M341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;DIV&gt;I'm moving from the MPC563 to the MPC5566 and am looking for guidance on some choices...&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Are there any benchmarks or guidelines to help determine the tradeoffs between the hardware and software vector modes?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;INTC has many vectors for FlexCAN, one for&amp;nbsp;each of the first 16 mailboxes.&amp;nbsp; Should each be sent to its own ISR?&amp;nbsp; Or is one ISR looping through the interrupt flags, like TouCAN, still a good choice?&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Jan 2009 01:47:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/MPC5566-Interrupts/m-p/146124#M341</guid>
      <dc:creator>sas</dc:creator>
      <dc:date>2009-01-24T01:47:48Z</dc:date>
    </item>
    <item>
      <title>Re: MPC5566 Interrupts</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/MPC5566-Interrupts/m-p/146125#M342</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Hi Sas,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;As far as I have understand this subject (I am transitionning from the MPC555 to the MPC5554 :smileywink: the software vector mode is a king of MPC5XX compatibility mode, wether the hardware mode offers better performance by handling in hardware some of the work that used to be done by software...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Feb 2009 18:35:29 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/MPC5566-Interrupts/m-p/146125#M342</guid>
      <dc:creator>JChMathae</dc:creator>
      <dc:date>2009-02-04T18:35:29Z</dc:date>
    </item>
    <item>
      <title>Re: MPC5566 Interrupts</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/MPC5566-Interrupts/m-p/146126#M343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;Performance is near the same, yet in hardware mode, you need more lines of code and rom due to the fact that each ISR has its own push and pop of the stack, its duplicated for every channel.&amp;nbsp; The advantage is that you can have custom code run on specific channels, to do your save context&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Dec 2009 09:55:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/MPC5566-Interrupts/m-p/146126#M343</guid>
      <dc:creator>hpdwally</dc:creator>
      <dc:date>2009-12-17T09:55:52Z</dc:date>
    </item>
  </channel>
</rss>

