<?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>topic When FS26 is in Normal Mode, can FS0B_DIAG / FS1B_DIAG detected short to high? in Power Management</title>
    <link>https://community.nxp.com/t5/Power-Management/When-FS26-is-in-Normal-Mode-can-FS0B-DIAG-FS1B-DIAG-detected/m-p/2204118#M4794</link>
    <description>&lt;P&gt;I found that if I'm in Debug Mode and haven't executed EXIT_DBG_MODE, FS0B_SNS and FS1B_SNS will be 0 / SENSED LOW. In this case, if I connect TP88 to 5V, I can get a SHORT TO HIGH DETECTED to set FS0B_DIAG = 1, and if I connect TP11 to 5V, I can get a SHORT TO HIGH DETECTED to set FS1B_DIAG = 1. However, if I'm in NORMAL Mode and have released FS0B and FS1B, because FS0B_SNS and FS1B_SNS will be 1 / SENSED HIGH, I cannot perform a check on FS0B_DIAG and FS1B_DIAG. This is because FS0B_DIAG and FS1B_DIAG are initially 1 / SHORT TO HIGH DETECTED, even though I haven't Input 5V to TP88 and TP11.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ASK_NXP_11.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/365419i20ACEE436F82C7A9/image-size/large?v=v2&amp;amp;px=999" role="button" title="ASK_NXP_11.png" alt="ASK_NXP_11.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ASK_NXP_10.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/365420iAD23C58E027AB96D/image-size/large?v=v2&amp;amp;px=999" role="button" title="ASK_NXP_10.png" alt="ASK_NXP_10.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When FS_STATES = 10 / Safety Outputs not released, connecting TP88 to 5V triggers a short to high detected and gives FS0B_DIAG = 1. Connecting TP11 to 5V triggers a short to high detected and gives FS1B_DIAG = 1.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ASK_NXP_9.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/365421iBF03FB9C8FD9AA3E/image-size/large?v=v2&amp;amp;px=999" role="button" title="ASK_NXP_9.png" alt="ASK_NXP_9.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When FS_STATES = 11 / Normal, I connected TP88 / TP11 to 5V, but FS0B_DIAG / FS1B_DIAG is always 0 / NO FAILURE.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ASK_NXP_12.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/365422i00DD96352D22C6D7/image-size/large?v=v2&amp;amp;px=999" role="button" title="ASK_NXP_12.png" alt="ASK_NXP_12.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This means that FS0B_DIAG / FS1B_DIAG detection is not possible when FS_STATES = 11.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Nov 2025 04:55:38 GMT</pubDate>
    <dc:creator>Allen_863</dc:creator>
    <dc:date>2025-11-13T04:55:38Z</dc:date>
    <item>
      <title>When FS26 is in Normal Mode, can FS0B_DIAG / FS1B_DIAG detected short to high?</title>
      <link>https://community.nxp.com/t5/Power-Management/When-FS26-is-in-Normal-Mode-can-FS0B-DIAG-FS1B-DIAG-detected/m-p/2204118#M4794</link>
      <description>&lt;P&gt;I found that if I'm in Debug Mode and haven't executed EXIT_DBG_MODE, FS0B_SNS and FS1B_SNS will be 0 / SENSED LOW. In this case, if I connect TP88 to 5V, I can get a SHORT TO HIGH DETECTED to set FS0B_DIAG = 1, and if I connect TP11 to 5V, I can get a SHORT TO HIGH DETECTED to set FS1B_DIAG = 1. However, if I'm in NORMAL Mode and have released FS0B and FS1B, because FS0B_SNS and FS1B_SNS will be 1 / SENSED HIGH, I cannot perform a check on FS0B_DIAG and FS1B_DIAG. This is because FS0B_DIAG and FS1B_DIAG are initially 1 / SHORT TO HIGH DETECTED, even though I haven't Input 5V to TP88 and TP11.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ASK_NXP_11.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/365419i20ACEE436F82C7A9/image-size/large?v=v2&amp;amp;px=999" role="button" title="ASK_NXP_11.png" alt="ASK_NXP_11.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ASK_NXP_10.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/365420iAD23C58E027AB96D/image-size/large?v=v2&amp;amp;px=999" role="button" title="ASK_NXP_10.png" alt="ASK_NXP_10.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When FS_STATES = 10 / Safety Outputs not released, connecting TP88 to 5V triggers a short to high detected and gives FS0B_DIAG = 1. Connecting TP11 to 5V triggers a short to high detected and gives FS1B_DIAG = 1.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ASK_NXP_9.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/365421iBF03FB9C8FD9AA3E/image-size/large?v=v2&amp;amp;px=999" role="button" title="ASK_NXP_9.png" alt="ASK_NXP_9.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When FS_STATES = 11 / Normal, I connected TP88 / TP11 to 5V, but FS0B_DIAG / FS1B_DIAG is always 0 / NO FAILURE.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ASK_NXP_12.png" style="width: 999px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/365422i00DD96352D22C6D7/image-size/large?v=v2&amp;amp;px=999" role="button" title="ASK_NXP_12.png" alt="ASK_NXP_12.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;This means that FS0B_DIAG / FS1B_DIAG detection is not possible when FS_STATES = 11.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Nov 2025 04:55:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/When-FS26-is-in-Normal-Mode-can-FS0B-DIAG-FS1B-DIAG-detected/m-p/2204118#M4794</guid>
      <dc:creator>Allen_863</dc:creator>
      <dc:date>2025-11-13T04:55:38Z</dc:date>
    </item>
    <item>
      <title>Re: When FS26 is in Normal Mode, can FS0B_DIAG / FS1B_DIAG detected short to high?</title>
      <link>https://community.nxp.com/t5/Power-Management/When-FS26-is-in-Normal-Mode-can-FS0B-DIAG-FS1B-DIAG-detected/m-p/2204180#M4796</link>
      <description>&lt;P&gt;Dear Allen,&lt;/P&gt;
&lt;P&gt;this is expected behavior. In DEBUG mode, the&amp;nbsp;FS0B is forced low and cannot be released by design; the watchdog is effectively opened, and the deep failsafe is deactivated. That means the device &lt;EM&gt;expects&lt;/EM&gt; FS0B to be low, so if you drive the pin externally to 5 V (short‑to‑high), the fail‑safe IO diagnostics see a contradiction and flag the short‑to‑high. Same applies for FS1B.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In Normal mode (FS_STATES=11), once released, FS0B/FS1B are high (pulled up). The device now expects HIGH, so tying the pin to 5 V does not contradict the expected state — therefore no short‑to‑high is detected and FSxB_DIAG stays 0. That’s why your “connect to 5 V” check appears to “do nothing” in Normal mode. Short‑to‑high diagnostics only make sense when the device is driving the pin low (or expects it to be low).&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With Best Regards,&lt;/P&gt;
&lt;P&gt;Jozef&lt;/P&gt;</description>
      <pubDate>Thu, 13 Nov 2025 06:28:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Power-Management/When-FS26-is-in-Normal-Mode-can-FS0B-DIAG-FS1B-DIAG-detected/m-p/2204180#M4796</guid>
      <dc:creator>JozefKozon</dc:creator>
      <dc:date>2025-11-13T06:28:00Z</dc:date>
    </item>
  </channel>
</rss>

