<?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: Does anyone use MPC5746C?</title>
    <link>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916078#M13706</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And did you perform the reading of FCCU faults or just simple look at registers?&lt;/P&gt;&lt;P&gt;because without changing OP state to read (0xA) FCCU status registers they will only return 0.&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/82808i5D6A2A841794AE37/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;regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 26 Sep 2019 10:00:19 GMT</pubDate>
    <dc:creator>petervlna</dc:creator>
    <dc:date>2019-09-26T10:00:19Z</dc:date>
    <item>
      <title>Does anyone use MPC5746C?</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916075#M13703</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;MPC5746C error, jump to IVOR1_Handler interrupt, a dozen processors are like this, using the official demo, has anyone encountered a similar problem?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2019 06:49:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916075#M13703</guid>
      <dc:creator>my_souls</dc:creator>
      <dc:date>2019-09-26T06:49:54Z</dc:date>
    </item>
    <item>
      <title>Re: Does anyone use MPC5746C?</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916076#M13704</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Ok, can you tell me what is the root cause for your IVOR1? There must be latched fault in FCCU.&lt;/P&gt;&lt;P&gt;What is the content of FCCU_NCFSx registers?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;BR /&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2019 08:57:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916076#M13704</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2019-09-26T08:57:34Z</dc:date>
    </item>
    <item>
      <title>Re: Does anyone use MPC5746C?</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916077#M13705</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, it is not clear what the reason is, the content of the FCCU_NCFSx register is 0.&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/81456iA9E5A780F94BCF39/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;DIV style="position: absolute; left: -11px; top: 418px;"&gt;&lt;DIV class="gtx-trans-icon"&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2019 09:50:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916077#M13705</guid>
      <dc:creator>my_souls</dc:creator>
      <dc:date>2019-09-26T09:50:49Z</dc:date>
    </item>
    <item>
      <title>Re: Does anyone use MPC5746C?</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916078#M13706</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;And did you perform the reading of FCCU faults or just simple look at registers?&lt;/P&gt;&lt;P&gt;because without changing OP state to read (0xA) FCCU status registers they will only return 0.&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/82808i5D6A2A841794AE37/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;regards,&lt;/P&gt;&lt;P&gt;Peter&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Sep 2019 10:00:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916078#M13706</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2019-09-26T10:00:19Z</dc:date>
    </item>
    <item>
      <title>Re: Does anyone use MPC5746C?</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916079#M13707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you very much for your answer. I seem to have found the problem. Currently, there is no OSC32K external pin in the MCU of the MPC5746C 100MAPBGA, and MC_ME.DRUN_MC.SXOSCON is enabled in the Demo of the SDK, but it does not judge and wait for MC_ME.GS. The .B.S_MTRANS bit is set to 0, so the program jumps to the IVOR1_Handler interrupt when the PIT register is manipulated.&lt;BR /&gt;It seems that the officially provided Demo Code does not distinguish the 100MAPBGA of the MPC5746C from other Pin packages.&lt;/P&gt;&lt;DIV style="position: absolute; left: -41px; top: -16px;"&gt;&lt;DIV class="gtx-trans-icon"&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Oct 2019 07:12:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Does-anyone-use-MPC5746C/m-p/916079#M13707</guid>
      <dc:creator>my_souls</dc:creator>
      <dc:date>2019-10-08T07:12:13Z</dc:date>
    </item>
  </channel>
</rss>

