<?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のトピックRe: FS26 Safety Outputs release</title>
    <link>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1390185#M1725</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hello Yazhou,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;It is necessary to write a 1 in order to clear the error flags bits. This is typically denoted in the FS26xx datasheet as “Clear on write to 1.”&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Tomas&lt;/P&gt;</description>
    <pubDate>Tue, 21 Dec 2021 13:34:49 GMT</pubDate>
    <dc:creator>TomasVaverka</dc:creator>
    <dc:date>2021-12-21T13:34:49Z</dc:date>
    <item>
      <title>FS26 Safety Outputs release</title>
      <link>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1371093#M1683</link>
      <description>&lt;P&gt;Hello, I want to ask whether the fail-safe output release function Sbc_fs26_FsxbRelease of the FS26 chip needs to be called in a loop&lt;/P&gt;</description>
      <pubDate>Mon, 15 Nov 2021 07:06:46 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1371093#M1683</guid>
      <dc:creator>dingyazhou</dc:creator>
      <dc:date>2021-11-15T07:06:46Z</dc:date>
    </item>
    <item>
      <title>Re: FS26 Safety Outputs release</title>
      <link>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1371323#M1686</link>
      <description>&lt;P&gt;Hello Yazhou,&lt;/P&gt;
&lt;P&gt;There is no need to call this function in a loop to release FSxB.&lt;/P&gt;
&lt;P&gt;The below diagram provides high level flow chart to enter Normal mode in the application.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Figure 16.JPG" style="width: 573px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/162157i2079CA9F83279DF4/image-size/large?v=v2&amp;amp;px=999" role="button" title="Figure 16.JPG" alt="Figure 16.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Tomas&lt;/P&gt;</description>
      <pubDate>Mon, 15 Nov 2021 12:08:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1371323#M1686</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2021-11-15T12:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: FS26 Safety Outputs release</title>
      <link>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1389515#M1724</link>
      <description>&lt;P&gt;Hello, I have another question, is our error flag register, such as FS_OVUV_REG_STATUS register is cleared after error clearance, or do you need to manually write "1" software?&lt;/P&gt;</description>
      <pubDate>Mon, 20 Dec 2021 11:33:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1389515#M1724</guid>
      <dc:creator>dingyazhou1</dc:creator>
      <dc:date>2021-12-20T11:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: FS26 Safety Outputs release</title>
      <link>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1390185#M1725</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hello Yazhou,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;It is necessary to write a 1 in order to clear the error flags bits. This is typically denoted in the FS26xx datasheet as “Clear on write to 1.”&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;Tomas&lt;/P&gt;</description>
      <pubDate>Tue, 21 Dec 2021 13:34:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/FS26-Safety-Outputs-release/m-p/1390185#M1725</guid>
      <dc:creator>TomasVaverka</dc:creator>
      <dc:date>2021-12-21T13:34:49Z</dc:date>
    </item>
  </channel>
</rss>

