<?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>S32K中的主题 Re: FCCU FAULT state reaction</title>
    <link>https://community.nxp.com/t5/S32K/FCCU-FAULT-state-reaction/m-p/1781166#M30056</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;However, during my debugging process, I noticed that if I select all three options, my program automatically performs a functional reset&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Yes that is correct. Since your FCCU will immediately wire signal to RGM and then reset is performed sooner as the interrupt is executed.&lt;/P&gt;
&lt;P&gt;Basically, just select reset or interrupt and optionally EOUT to those 2.&lt;/P&gt;
&lt;P&gt;If the FCCU is not able to perform interrupt the FOSU will reset it anyway after timeout.&lt;/P&gt;
&lt;P&gt;So set reset on the faults you want immediate reset reaction to prevent device damage (motor burnout etc..) and interrupts on the faults you want to analyze before any actions are performed.&lt;/P&gt;
&lt;P&gt;If you select all, they will be executed in parallel and your device will take reset.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
    <pubDate>Fri, 29 Dec 2023 09:03:50 GMT</pubDate>
    <dc:creator>petervlna</dc:creator>
    <dc:date>2023-12-29T09:03:50Z</dc:date>
    <item>
      <title>FCCU FAULT state reaction</title>
      <link>https://community.nxp.com/t5/S32K/FCCU-FAULT-state-reaction/m-p/1781143#M30052</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;In the safety section of the reference manual, in the introduction of the FCCU (Fault Collection and Control Unit) module, there are three options mentioned regarding the error handling mechanism when FCCU enters the FAULT state.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pusoy_0-1703834758040.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/256214i992497C758283498/image-size/large?v=v2&amp;amp;px=999" role="button" title="Pusoy_0-1703834758040.png" alt="Pusoy_0-1703834758040.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;These three options can also be selected simultaneously in the configuration tool.&lt;/P&gt;&lt;P&gt;However, during my debugging process, I noticed that if I select all three options, my program automatically performs a functional reset before entering the NMI (Non-Maskable Interrupt) handler function.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Pusoy_0-1703835509684.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/256215i818085D8ED3D0B11/image-size/large?v=v2&amp;amp;px=999" role="button" title="Pusoy_0-1703835509684.png" alt="Pusoy_0-1703835509684.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;1. Can you please explain the execution order of these three reactions when all three options are selected?&lt;/P&gt;</description>
      <pubDate>Fri, 29 Dec 2023 07:42:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/FCCU-FAULT-state-reaction/m-p/1781143#M30052</guid>
      <dc:creator>Pusoy</dc:creator>
      <dc:date>2023-12-29T07:42:01Z</dc:date>
    </item>
    <item>
      <title>Re: FCCU FAULT state reaction</title>
      <link>https://community.nxp.com/t5/S32K/FCCU-FAULT-state-reaction/m-p/1781166#M30056</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;BLOCKQUOTE&gt;
&lt;P&gt;However, during my debugging process, I noticed that if I select all three options, my program automatically performs a functional reset&lt;/P&gt;
&lt;/BLOCKQUOTE&gt;
&lt;P&gt;Yes that is correct. Since your FCCU will immediately wire signal to RGM and then reset is performed sooner as the interrupt is executed.&lt;/P&gt;
&lt;P&gt;Basically, just select reset or interrupt and optionally EOUT to those 2.&lt;/P&gt;
&lt;P&gt;If the FCCU is not able to perform interrupt the FOSU will reset it anyway after timeout.&lt;/P&gt;
&lt;P&gt;So set reset on the faults you want immediate reset reaction to prevent device damage (motor burnout etc..) and interrupts on the faults you want to analyze before any actions are performed.&lt;/P&gt;
&lt;P&gt;If you select all, they will be executed in parallel and your device will take reset.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Peter&lt;/P&gt;</description>
      <pubDate>Fri, 29 Dec 2023 09:03:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/FCCU-FAULT-state-reaction/m-p/1781166#M30056</guid>
      <dc:creator>petervlna</dc:creator>
      <dc:date>2023-12-29T09:03:50Z</dc:date>
    </item>
  </channel>
</rss>

