<?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 Re: Not enough information about Supported BIST configurations for S32K396 in SafeAssure Community (Archived)</title>
    <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1560415#M998</link>
    <description>&lt;P&gt;Which memory index is connected to the MBIST0? Is it the ones with 0 or are there different ones that are connected to MBIST0?&lt;/P&gt;</description>
    <pubDate>Mon, 28 Nov 2022 07:57:39 GMT</pubDate>
    <dc:creator>Berk123</dc:creator>
    <dc:date>2022-11-28T07:57:39Z</dc:date>
    <item>
      <title>Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1554919#M989</link>
      <description>&lt;P&gt;Hello, so I was wondering on what the differences between BIST_SAFETYBOOT_CFG and BIST_DIAGNOSTIC_CFG is, also if you can provide me with "every single BIST available on the platform" according to the BIST SPD user manual. Thank you!&lt;/P&gt;</description>
      <pubDate>Wed, 16 Nov 2022 12:46:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1554919#M989</guid>
      <dc:creator>Berk123</dc:creator>
      <dc:date>2022-11-16T12:46:11Z</dc:date>
    </item>
    <item>
      <title>Re: Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1557809#M994</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;the Bist Manager software supports the following selftest configurations on S32K396:&lt;/P&gt;
&lt;P&gt;BIST_DIAGNOSTIC_CFG - contains all the M/LBISTs available on the device, i.e. MBIST0 up to 11 and LBIST0&lt;BR /&gt;BIST_SAFETYBOOT_CFG – contains MBIST1 up to 11 and LBIST0 (i.e. the same as diagnostic config except that it does not contain MBIST0)&lt;/P&gt;
&lt;P&gt;The MBIST and LBIST are documented in HW reference manual, section “49.1.3 STCU2 LBIST/MBIST mapping”.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;BR /&gt;Frantisek&lt;/P&gt;</description>
      <pubDate>Tue, 22 Nov 2022 12:25:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1557809#M994</guid>
      <dc:creator>frantisekdobes</dc:creator>
      <dc:date>2022-11-22T12:25:02Z</dc:date>
    </item>
    <item>
      <title>Re: Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1560415#M998</link>
      <description>&lt;P&gt;Which memory index is connected to the MBIST0? Is it the ones with 0 or are there different ones that are connected to MBIST0?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Nov 2022 07:57:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1560415#M998</guid>
      <dc:creator>Berk123</dc:creator>
      <dc:date>2022-11-28T07:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1561379#M1002</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;the MBIST0 corresponds to "BIST Index"=0 and "BIST Name"=HSE_ROMS. I have checked the HW reference manual and the MBIST0 is not described there so I will provide more details after confirmation from HW team.&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Frantisek&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 14:24:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1561379#M1002</guid>
      <dc:creator>frantisekdobes</dc:creator>
      <dc:date>2022-11-29T14:24:41Z</dc:date>
    </item>
    <item>
      <title>Re: Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1561380#M1003</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;I really appreciate your time and effort, that would be very helpful&lt;BR /&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 29 Nov 2022 14:25:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1561380#M1003</guid>
      <dc:creator>Berk123</dc:creator>
      <dc:date>2022-11-29T14:25:39Z</dc:date>
    </item>
    <item>
      <title>Re: Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1562655#M1005</link>
      <description>Hi,&lt;BR /&gt;Any updates from the HW team?&lt;BR /&gt;Regards!</description>
      <pubDate>Thu, 01 Dec 2022 08:29:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1562655#M1005</guid>
      <dc:creator>Berk123</dc:creator>
      <dc:date>2022-12-01T08:29:32Z</dc:date>
    </item>
    <item>
      <title>Re: Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1562737#M1006</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;the HW team confirmed that MBIST0 is the HSE_ROMS MBIST.&amp;nbsp;There are memory reliability and retention tests for this ROM and these are part only of BIST_DIAGNOSTIC_CFG. Normally customers run&amp;nbsp;&lt;SPAN&gt;BIST_SAFETYBOOT_CFG which does not contain this MBIST0.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Best Regards,&lt;/P&gt;
&lt;P&gt;Frantisek&lt;/P&gt;</description>
      <pubDate>Thu, 01 Dec 2022 09:49:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1562737#M1006</guid>
      <dc:creator>frantisekdobes</dc:creator>
      <dc:date>2022-12-01T09:49:39Z</dc:date>
    </item>
    <item>
      <title>Re: Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1562842#M1007</link>
      <description>Hi,&lt;BR /&gt;I understand what you guys mean but when using the diagnostic in my code the ECU goes into a power down state instead of a sleeping state, which im trying to figure out why but if it is only memory reliability and retention tests why would it act differently?&lt;BR /&gt;Berk</description>
      <pubDate>Thu, 01 Dec 2022 13:15:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1562842#M1007</guid>
      <dc:creator>Berk123</dc:creator>
      <dc:date>2022-12-01T13:15:04Z</dc:date>
    </item>
    <item>
      <title>Re: Not enough information about Supported BIST configurations for S32K396</title>
      <link>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1571328#M1015</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/207465"&gt;@Berk123&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;to summarize results of investigations we did together:&amp;nbsp;we have seen the same issue in our tests (i.e. selftest failed with STCU WDTOSW bit set which is watchdog timeout). This was caused by not enabled EMAC clock by MC_CGM.MUX_9_DC_0 which is mandatory to run the selftest on EMAC TSN memory (MBIST11) as per this note from HW reference manual:&lt;/P&gt;
&lt;P&gt;======================================================&lt;BR /&gt;While running MBIST on EMAC timestamp memory, MC_CGM.MUX_9_DC_0[DIV] should be appropriately configured to ensure EMAC_CLK_TS should be at least 1.5 times the AIPS_SLOW_CLK frequency.&lt;BR /&gt;======================================================&lt;/P&gt;
&lt;P&gt;After enabling the EMAC clock the selftest (both safetyboot and diagnostic) is done correctly without any errors.&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;Frantisek&lt;/P&gt;</description>
      <pubDate>Fri, 16 Dec 2022 17:16:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/SafeAssure-Community-Archived/Not-enough-information-about-Supported-BIST-configurations-for/m-p/1571328#M1015</guid>
      <dc:creator>frantisekdobes</dc:creator>
      <dc:date>2022-12-16T17:16:45Z</dc:date>
    </item>
  </channel>
</rss>

