<?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のトピックTrigger BIST Failure on S32K344 using S32DS</title>
    <link>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2121655#M50167</link>
    <description>&lt;P&gt;&lt;FONT size="2"&gt;I'm working with the S32K344 in S32DS and trying to test the BIST functionality. I want to simulate a failure to observe how the system reacts, but I’m not sure how to get BIST to actually fail.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;So far, I’ve tried changing the LBIST clock frequency in the clock configuration, but I still get&amp;nbsp; Bist_GetExecStatus as BIST_OK.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;Is there a recommended way to force a BIST failure for testing purposes?&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;I am using the example code from the demo for my testing:&lt;/FONT&gt;&lt;/P&gt;
&lt;LI-SPOILER&gt;&lt;LI-CODE lang="markup"&gt;if (MCU_POWER_ON_RESET == resetReason) {
		Bist_Run(BIST_SAFETYBOOT_CFG);
	} else if (MCU_ST_DONE_RESET == resetReason) {
		bistStatus = Bist_GetExecStatus(BIST_SAFETYBOOT_CFG);
		if (bistStatus != BIST_OK) {
                   ...&lt;/LI-CODE&gt;&lt;/LI-SPOILER&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Jun 2025 14:28:30 GMT</pubDate>
    <dc:creator>aayushisingh</dc:creator>
    <dc:date>2025-06-24T14:28:30Z</dc:date>
    <item>
      <title>Trigger BIST Failure on S32K344 using S32DS</title>
      <link>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2121655#M50167</link>
      <description>&lt;P&gt;&lt;FONT size="2"&gt;I'm working with the S32K344 in S32DS and trying to test the BIST functionality. I want to simulate a failure to observe how the system reacts, but I’m not sure how to get BIST to actually fail.&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;So far, I’ve tried changing the LBIST clock frequency in the clock configuration, but I still get&amp;nbsp; Bist_GetExecStatus as BIST_OK.&amp;nbsp;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;Is there a recommended way to force a BIST failure for testing purposes?&amp;nbsp;&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT size="2"&gt;I am using the example code from the demo for my testing:&lt;/FONT&gt;&lt;/P&gt;
&lt;LI-SPOILER&gt;&lt;LI-CODE lang="markup"&gt;if (MCU_POWER_ON_RESET == resetReason) {
		Bist_Run(BIST_SAFETYBOOT_CFG);
	} else if (MCU_ST_DONE_RESET == resetReason) {
		bistStatus = Bist_GetExecStatus(BIST_SAFETYBOOT_CFG);
		if (bistStatus != BIST_OK) {
                   ...&lt;/LI-CODE&gt;&lt;/LI-SPOILER&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Jun 2025 14:28:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2121655#M50167</guid>
      <dc:creator>aayushisingh</dc:creator>
      <dc:date>2025-06-24T14:28:30Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger BIST Failure on S32K344 using S32DS</title>
      <link>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2121921#M50181</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/251111"&gt;@aayushisingh&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;We cannot inject a fault into MBIST itself to make it report a failure.&lt;BR /&gt;MBIST is a hardware self-test mechanism built into the silicon. It runs a deterministic test pattern to detect structural faults.&lt;BR /&gt;&lt;BR /&gt;It was already discussed in this thread:&lt;BR /&gt;&lt;A href="https://community.nxp.com/t5/S32K/STCU2-BIST-question/m-p/1774475" target="_blank" rel="noopener"&gt;https://community.nxp.com/t5/S32K/STCU2-BIST-question/m-p/1774475&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The watchdog can be set incorrectly though:&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="danielmartynek_0-1750747208186.png" style="width: 584px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/344304iFE3BC737B1319467/image-dimensions/584x178?v=v2" width="584" height="178" role="button" title="danielmartynek_0-1750747208186.png" alt="danielmartynek_0-1750747208186.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Jun 2025 07:02:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2121921#M50181</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2025-06-26T07:02:12Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger BIST Failure on S32K344 using S32DS</title>
      <link>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2122293#M50201</link>
      <description>&lt;P&gt;&lt;FONT size="2"&gt;Thanks for the clarification &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/160001"&gt;@danielmartynek&lt;/a&gt;&amp;nbsp;!&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;Just to confirm, if I intentionally misconfigure the watchdog, and it triggers during BIST execution, does that mean BIST is considered&amp;nbsp;incomplete, or the system just resets before BIST can finish?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;Also, is the watchdog timer mentioned in the manual referring to&lt;FONT face="courier new,courier"&gt;&amp;nbsp;BIST_STCU_SAF_WDG_VAL&lt;/FONT&gt;? If that expires, would the reset reason be something other than&lt;FONT face="courier new,courier"&gt;&amp;nbsp;MCU_ST_DONE_RESET&lt;/FONT&gt;?&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2"&gt;As I mentioned earlier, I’m using the demo example provided with the SAF module. In that context, would you recommend modifying the reset check from just&amp;nbsp;&lt;FONT face="courier new,courier"&gt;MCU_ST_DONE_RESET&lt;/FONT&gt; to account for other reset types?&lt;/FONT&gt;&lt;/P&gt;
&lt;LI-SPOILER&gt;&lt;LI-CODE lang="c"&gt;    if (MCU_POWER_ON_RESET == resetReason)
    {
#if (BIST_MODULE_ENABLED == 1U)
        Bist_Run(BIST_SAFETYBOOT_CFG);
    }
    else if(MCU_ST_DONE_RESET == resetReason)
    {
        bistStatus = Bist_GetExecStatus(BIST_SAFETYBOOT_CFG);
        if( bistStatus != BIST_OK )
        {
            if(bistStatus == BIST_ERROR)
            { ...&lt;/LI-CODE&gt;&lt;/LI-SPOILER&gt;
&lt;DIV style="background-color: #ffffff; padding: 0px 0px 0px 2px;"&gt;
&lt;DIV style="color: #000000; background-color: #ffffff; font-family: 'Courier New'; font-size: 10pt; white-space: pre;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Jun 2025 18:39:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2122293#M50201</guid>
      <dc:creator>aayushisingh</dc:creator>
      <dc:date>2025-06-25T18:39:30Z</dc:date>
    </item>
    <item>
      <title>Re: Trigger BIST Failure on S32K344 using S32DS</title>
      <link>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2125410#M50380</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/251111"&gt;@aayushisingh&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;If BIST WDG expires you should be able to read that as internal error ERR_STTA register, bit WDTOSW.&lt;/P&gt;
&lt;PRE class="lia-code-sample  language-markup"&gt;&lt;CODE&gt;if(bistStatus == BIST_ERROR)
            {
                /* Reads STCU ERR_STAT register to identify what HW error occurred */
                stcuStatus = Bist_GetRawErrorStatus();
                (void) stcuStatus;
            }&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;For test purpose you can modify macro BIST_STCU_DIAG_WDG_VAL to some very low value to see the effect.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Daniel&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jun 2025 07:17:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/Trigger-BIST-Failure-on-S32K344-using-S32DS/m-p/2125410#M50380</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2025-06-30T07:17:04Z</dc:date>
    </item>
  </channel>
</rss>

