<?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>Power ManagementのトピックFS26   Perform RSTB path check</title>
    <link>https://community.nxp.com/t5/Power-Management/FS26-Perform-RSTB-path-check/m-p/1637930#M2552</link>
    <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;RSTB assertion can be requested by SPI with the bit RSTB_REQ in FS_SAFE_IOS_1，then the&amp;nbsp;&amp;nbsp;software reads the RSTB _ DIAG flag for judgment.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;But after the MCU reset, how does the software identify the reset reason is power reset or RSTB_REQ?&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Please help me give me a way to implement step4, thank you!&lt;/FONT&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Close&lt;/STRONG&gt; the initialization phase by sending the first good WD refresh.&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Clear&lt;/STRONG&gt; all the flags by writing in FS_DIAG_SAFETY1,FS_DIAG_SAFETY2,FS_OVUVREG_STATUS.&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;OL&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Clear&lt;/STRONG&gt; the fault error counter to “0” with consecutive good WD refresh.&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif" color="#FF0000"&gt;&lt;STRONG&gt;Perform&lt;/STRONG&gt; RSTB path check (steps 1 to 4 must be redone after RSTB is released).&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Release&lt;/STRONG&gt; FS0B pin.&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Perform&lt;/STRONG&gt; FS0B safety path check.&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;</description>
    <pubDate>Fri, 21 Apr 2023 09:18:03 GMT</pubDate>
    <dc:creator>liyongfeng</dc:creator>
    <dc:date>2023-04-21T09:18:03Z</dc:date>
    <item>
      <title>FS26   Perform RSTB path check</title>
      <link>https://community.nxp.com/t5/Power-Management/FS26-Perform-RSTB-path-check/m-p/1637930#M2552</link>
      <description>&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;RSTB assertion can be requested by SPI with the bit RSTB_REQ in FS_SAFE_IOS_1，then the&amp;nbsp;&amp;nbsp;software reads the RSTB _ DIAG flag for judgment.&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;But after the MCU reset, how does the software identify the reset reason is power reset or RSTB_REQ?&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;Please help me give me a way to implement step4, thank you!&lt;/FONT&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Close&lt;/STRONG&gt; the initialization phase by sending the first good WD refresh.&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Clear&lt;/STRONG&gt; all the flags by writing in FS_DIAG_SAFETY1,FS_DIAG_SAFETY2,FS_OVUVREG_STATUS.&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;OL&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Clear&lt;/STRONG&gt; the fault error counter to “0” with consecutive good WD refresh.&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif" color="#FF0000"&gt;&lt;STRONG&gt;Perform&lt;/STRONG&gt; RSTB path check (steps 1 to 4 must be redone after RSTB is released).&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Release&lt;/STRONG&gt; FS0B pin.&lt;/FONT&gt;&lt;/LI&gt;&lt;LI&gt;&lt;FONT face="arial,helvetica,sans-serif"&gt;&lt;STRONG&gt;Perform&lt;/STRONG&gt; FS0B safety path check.&lt;/FONT&gt;&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Fri, 21 Apr 2023 09:18:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/FS26-Perform-RSTB-path-check/m-p/1637930#M2552</guid>
      <dc:creator>liyongfeng</dc:creator>
      <dc:date>2023-04-21T09:18:03Z</dc:date>
    </item>
    <item>
      <title>Re: FS26   Perform RSTB path check</title>
      <link>https://community.nxp.com/t5/Power-Management/FS26-Perform-RSTB-path-check/m-p/1638593#M2553</link>
      <description>&lt;P&gt;Dear 李 永锋,&lt;/P&gt;
&lt;P&gt;please refer to the section 21.3.7 in the FS26 datasheet. If the INTB pin generates a pulse to the MCU, then the source of the RSTB asserted, is a fault. Not a requested by the MCU through the SPI interface. The Table 136. and Table 137. shows list of INTB sources.&lt;/P&gt;
&lt;P&gt;With Best Regards,&lt;/P&gt;
&lt;P&gt;Jozef&lt;/P&gt;</description>
      <pubDate>Mon, 24 Apr 2023 05:19:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/FS26-Perform-RSTB-path-check/m-p/1638593#M2553</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2023-04-24T05:19:41Z</dc:date>
    </item>
  </channel>
</rss>

