https://community.nxp.com/t5/SafeAssure-Community/S32K-BIST-process-problem/m-p/1979945#M317 <P>Hi Li,</P> <P>the complete safety concept requires an external PMIC or at least a WDT as pure minimum. The WDT will detect endless loops and reset the part a number of times until it completely disables the MCU. NXP PMICs support this, the number of POR resets can be configured and read after boot. Please consult the RM/SM of the used PMIC.</P> <P>If permanent HW failures occur causing an endless loop there is a severe problem so completely disable the MCU is appropriate as you can assume a recovery is not possible anymore. Customers need to handle this situation themselves as this is application dependent.</P> <P>Regards,</P> <P>Bas</P> Wed, 23 Oct 2024 07:23:01 GMT BasW 2024-10-23T07:23:01Z https://community.nxp.com/t5/SafeAssure-Community/S32K-BIST-process-problem/m-p/1975024#M316 <P>Hi NXP,</P><P><SPAN>As shown in the figure: if the return value of Bist_GetExecStatus is always BIST_INTEGRITY_FAIL, the loop will keep going. Is there a problem with designing the BIST process this way?</SPAN></P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="li3_0-1729069451782.png" style="width: 400px;"><img src="https://community.nxp.com/t5/image/serverpage/image-id/304972i0DF55F2F62A6131D/image-size/medium?v=v2&amp;px=400" role="button" title="li3_0-1729069451782.png" alt="li3_0-1729069451782.png" /></span></P><P><SPAN>Best regards,</SPAN></P><P><SPAN>Li 3</SPAN></P><P>&nbsp;</P> Wed, 16 Oct 2024 09:07:32 GMT https://community.nxp.com/t5/SafeAssure-Community/S32K-BIST-process-problem/m-p/1975024#M316 li3 2024-10-16T09:07:32Z https://community.nxp.com/t5/SafeAssure-Community/S32K-BIST-process-problem/m-p/1979945#M317 <P>Hi Li,</P> <P>the complete safety concept requires an external PMIC or at least a WDT as pure minimum. The WDT will detect endless loops and reset the part a number of times until it completely disables the MCU. NXP PMICs support this, the number of POR resets can be configured and read after boot. Please consult the RM/SM of the used PMIC.</P> <P>If permanent HW failures occur causing an endless loop there is a severe problem so completely disable the MCU is appropriate as you can assume a recovery is not possible anymore. Customers need to handle this situation themselves as this is application dependent.</P> <P>Regards,</P> <P>Bas</P> Wed, 23 Oct 2024 07:23:01 GMT https://community.nxp.com/t5/SafeAssure-Community/S32K-BIST-process-problem/m-p/1979945#M317 BasW 2024-10-23T07:23:01Z