<?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: EEEPROM ECC in S32K</title>
    <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042089#M6763</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;hello，&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;as the following picture description, which interrupt source supported by EEPROM used?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;and when does the&amp;nbsp; read collision Error generate?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;wish your help!&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/112957iBD933D9E7A6D498A/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 16 Jun 2020 10:03:41 GMT</pubDate>
    <dc:creator>814420552</dc:creator>
    <dc:date>2020-06-16T10:03:41Z</dc:date>
    <item>
      <title>EEEPROM ECC</title>
      <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042087#M6761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;1&amp;gt;when S32K146 data flash partitioned to EEPROM and ECC check EEPROM single-bit&amp;nbsp; error and double-bit error ,&lt;/P&gt;&lt;P&gt;all the error will&amp;nbsp; have&amp;nbsp; an interrupt if enabled?&amp;nbsp; whether can i get the error address for ECC error when ECC working on EEPROM?&lt;/P&gt;&lt;P&gt;Even if we can get these ECC error addresses, it seems that our users can't do anything to fix the errors. In this way, it feels that this ECC detects 2 bit errors. It does not seem to be useful except for automatically fixing 1 bit errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;2&amp;gt; &lt;STRONG&gt;How do you understand the following paragraph with red lines?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/112730iFF1A78A0CA76FEB4/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;wish&amp;nbsp; your help&lt;/P&gt;&lt;P&gt;&amp;nbsp;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 13 Jun 2020 08:05:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042087#M6761</guid>
      <dc:creator>814420552</dc:creator>
      <dc:date>2020-06-13T08:05:35Z</dc:date>
    </item>
    <item>
      <title>Re: EEEPROM ECC</title>
      <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042088#M6762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello &lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/814420552@qq.com"&gt;814420552@qq.com&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&lt;/P&gt;&lt;P&gt;The EEPROM backup flash is managed by the EEPROM state machine, the user does not have access to it.&lt;/P&gt;&lt;P&gt;When ECC errors are detected in the backup flash, no interrupt is generated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.&lt;/P&gt;&lt;P&gt;However,&amp;nbsp;&lt;/P&gt;&lt;P&gt;any single-bit ECC errors are automatically corrected when the data are loaded from the backup flash to FlexRAM (EEPROM).&lt;/P&gt;&lt;P&gt;Data that cannot be automatically corrected (uncorrectable double-bit ECC errors) are left as all 1s in FlexRAM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2020 08:49:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042088#M6762</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2020-06-16T08:49:51Z</dc:date>
    </item>
    <item>
      <title>Re: EEEPROM ECC</title>
      <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042089#M6763</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;hello，&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;as the following picture description, which interrupt source supported by EEPROM used?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;and when does the&amp;nbsp; read collision Error generate?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;wish your help!&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/112957iBD933D9E7A6D498A/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Jun 2020 10:03:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042089#M6763</guid>
      <dc:creator>814420552</dc:creator>
      <dc:date>2020-06-16T10:03:41Z</dc:date>
    </item>
    <item>
      <title>Re: EEEPROM ECC</title>
      <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042090#M6764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/814420552@qq.com"&gt;814420552@qq.com&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;The DFDIF flag is not available for the EEPROM, but the other two are available.&lt;/P&gt;&lt;P&gt;The FTFC module detects a read collision, when&amp;nbsp;the MCU attempts to read from an FTFC resource (block) that is&lt;BR /&gt;being manipulated by an FTFC command (CCIF=0).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Daniel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2020 12:25:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042090#M6764</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2020-06-17T12:25:12Z</dc:date>
    </item>
    <item>
      <title>Re: EEEPROM ECC</title>
      <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042091#M6765</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello Daniel,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;firstly thanks for you answer quickly! wish you good luck!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;and I have anther question is as the follow&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;how to understand the following Red frame description and&amp;nbsp; when and where will&amp;nbsp; we use this function ？&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;in fact&amp;nbsp; i&amp;nbsp; am confused with this sentence！&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/113169i683B9F82502DFE15/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2020 12:01:04 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042091#M6765</guid>
      <dc:creator>814420552</dc:creator>
      <dc:date>2020-06-18T12:01:04Z</dc:date>
    </item>
    <item>
      <title>Re: EEEPROM ECC</title>
      <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042092#M6766</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&amp;nbsp;&lt;A class="jx-jive-macro-user" href="https://community.nxp.com/people/814420552@qq.com"&gt;814420552@qq.com&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The FDFD allows emulating uncorrectable double-bit ECC error detection on the flash.&lt;/P&gt;&lt;P&gt;When FDFD = 1, any read from the flash will set the DFDIF flag as if there was a double bit ECC error.&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;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2020 12:18:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042092#M6766</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2020-06-18T12:18:12Z</dc:date>
    </item>
    <item>
      <title>Re: EEEPROM ECC</title>
      <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042093#M6767</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello，&lt;/P&gt;&lt;P&gt;in S32K-SafetyMannual, as the following description, EEPROM has ECC interupt source?&amp;nbsp;&lt;/P&gt;&lt;P&gt;this is inconsistent with what you said before that there is no ECC interruption.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="pastedImage_1.png"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/116392i6772AE4181E5EF75/image-size/large?v=v2&amp;amp;px=999" role="button" title="pastedImage_1.png" alt="pastedImage_1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 21 Jul 2020 03:58:25 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1042093#M6767</guid>
      <dc:creator>814420552</dc:creator>
      <dc:date>2020-07-21T03:58:25Z</dc:date>
    </item>
    <item>
      <title>Re: EEEPROM ECC</title>
      <link>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1173835#M8590</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I'm sorry for the delay.&lt;/P&gt;
&lt;P&gt;The safety manual will be corrected in the next revision.&lt;/P&gt;
&lt;P&gt;This applies only to PFlash and DFlash on S32K1xx with the FTFC module.&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>Tue, 27 Oct 2020 12:11:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32K/EEEPROM-ECC/m-p/1173835#M8590</guid>
      <dc:creator>danielmartynek</dc:creator>
      <dc:date>2020-10-27T12:11:56Z</dc:date>
    </item>
  </channel>
</rss>

