<?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>MPC5xxxのトピックRe: Tracking the reason for IVOR2_3 handler</title>
    <link>https://community.nxp.com/t5/MPC5xxx/Tracking-the-reason-for-IVOR2-3-handler/m-p/1777797#M24653</link>
    <description>&lt;P&gt;Could you specify used MCU?&lt;/P&gt;</description>
    <pubDate>Wed, 20 Dec 2023 08:29:10 GMT</pubDate>
    <dc:creator>davidtosenovjan</dc:creator>
    <dc:date>2023-12-20T08:29:10Z</dc:date>
    <item>
      <title>Tracking the reason for IVOR2_3 handler</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Tracking-the-reason-for-IVOR2-3-handler/m-p/1777295#M24649</link>
      <description>&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;Sometimes I got into the IVOR2_3 handler, but I don't know how. Is there any way to track it except debug trace? Attached is my configuration for this handler. Normally the function "next_inst" should not be called.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Dec 2023 16:47:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Tracking-the-reason-for-IVOR2-3-handler/m-p/1777295#M24649</guid>
      <dc:creator>yixin</dc:creator>
      <dc:date>2023-12-19T16:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: Tracking the reason for IVOR2_3 handler</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Tracking-the-reason-for-IVOR2-3-handler/m-p/1777797#M24653</link>
      <description>&lt;P&gt;Could you specify used MCU?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Dec 2023 08:29:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Tracking-the-reason-for-IVOR2-3-handler/m-p/1777797#M24653</guid>
      <dc:creator>davidtosenovjan</dc:creator>
      <dc:date>2023-12-20T08:29:10Z</dc:date>
    </item>
  </channel>
</rss>

