<?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: S32G2 DIAGNOSTICS_BIST failure in S32G</title>
    <link>https://community.nxp.com/t5/S32G/S32G2-DIAGNOSTICS-BIST-failure/m-p/1737983#M5743</link>
    <description>&lt;P&gt;Thanks for investigating. It looks like we have an instance on a non ES chip.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chip's marking are as follows:&lt;/P&gt;&lt;P&gt;S32G274ASBVUC&lt;/P&gt;&lt;P&gt;0P77B&lt;/P&gt;&lt;P&gt;SBBB2133B&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Oct 2023 22:41:54 GMT</pubDate>
    <dc:creator>lvaynberg</dc:creator>
    <dc:date>2023-10-11T22:41:54Z</dc:date>
    <item>
      <title>S32G2 DIAGNOSTICS_BIST failure</title>
      <link>https://community.nxp.com/t5/S32G/S32G2-DIAGNOSTICS-BIST-failure/m-p/1726570#M5741</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm running a BIST_DIAGNOSTIC_CFG on an S32G274A MCU on the RDB2 dev board. I'm observing a BIST_FAILED result, with the following MBIST status flags (corresponding to the MBSSW registers:&lt;/P&gt;&lt;P&gt;MBESW0,1,2,3 registers: FFFFFFFF FFFFFFFF 00003FFF 00000000&lt;BR /&gt;MBSSW0,1,2,3 registers: FFFFFFFF FFFFBFFF 00003FFF 00000000&lt;/P&gt;&lt;P&gt;I believe this is indicating that MBIST 46 is failing which corresponds to PCIE_CORE.&lt;/P&gt;&lt;P&gt;In our fleet of S32G274A devices, we've observed that some devices don't fail this test while others do, and some of them fail only sometimes. Is this a known issue with the S32G274A? Is there a particular clock configuration or any other configuration that can cause this MBIST to fail?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Sep 2023 23:28:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G2-DIAGNOSTICS-BIST-failure/m-p/1726570#M5741</guid>
      <dc:creator>lvaynberg</dc:creator>
      <dc:date>2023-09-20T23:28:52Z</dc:date>
    </item>
    <item>
      <title>Re: S32G2 DIAGNOSTICS_BIST failure</title>
      <link>https://community.nxp.com/t5/S32G/S32G2-DIAGNOSTICS-BIST-failure/m-p/1734225#M5742</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;we are still trying to investigate it, but we are not able to confirm any issue yet. Please, what silicon version do you use?&lt;/P&gt;</description>
      <pubDate>Thu, 05 Oct 2023 12:11:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G2-DIAGNOSTICS-BIST-failure/m-p/1734225#M5742</guid>
      <dc:creator>martinkaspar-r3</dc:creator>
      <dc:date>2023-10-05T12:11:15Z</dc:date>
    </item>
    <item>
      <title>Re: S32G2 DIAGNOSTICS_BIST failure</title>
      <link>https://community.nxp.com/t5/S32G/S32G2-DIAGNOSTICS-BIST-failure/m-p/1737983#M5743</link>
      <description>&lt;P&gt;Thanks for investigating. It looks like we have an instance on a non ES chip.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Chip's marking are as follows:&lt;/P&gt;&lt;P&gt;S32G274ASBVUC&lt;/P&gt;&lt;P&gt;0P77B&lt;/P&gt;&lt;P&gt;SBBB2133B&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Oct 2023 22:41:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/S32G2-DIAGNOSTICS-BIST-failure/m-p/1737983#M5743</guid>
      <dc:creator>lvaynberg</dc:creator>
      <dc:date>2023-10-11T22:41:54Z</dc:date>
    </item>
  </channel>
</rss>

