<?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>MPC5xxxのトピックRe: Can not clear ECSM.ESR.R1BC</title>
    <link>https://community.nxp.com/t5/MPC5xxx/Can-not-clear-ECSM-ESR-R1BC/m-p/633779#M5984</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ECC mechanism corrects 1-bit errors internally, NOT in RAM.&amp;nbsp;The correct data is passed to the core, but the RAM remains corrupted.&amp;nbsp;Because of this, the original address with the error needs to be written with a good data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 Sep 2016 13:04:36 GMT</pubDate>
    <dc:creator>buzduganandrei</dc:creator>
    <dc:date>2016-09-20T13:04:36Z</dc:date>
    <item>
      <title>Can not clear ECSM.ESR.R1BC</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Can-not-clear-ECSM-ESR-R1BC/m-p/633778#M5983</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello NXP Community,&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;I am developing some code to help verify the ECC's HW for RAM. For this I need to use the error injection mechanism and inspect the ESR.R1BC. While I do see that ECC has captured correctly the address and data of the error, (though the symptom bits are way off) and the R1BC is asserted, I can not clear the R1BC.&lt;/P&gt;&lt;P&gt;&amp;nbsp;I have the following algorithm :&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;//Load &lt;SPAN&gt;ECSM.EEGR.ERRBIT&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;//Set &lt;SPAN&gt;ECSM.EEGR.FR11BI&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;//Generate&amp;nbsp;SEC&lt;BR /&gt;array[0]&amp;nbsp;= 0xFFFFFFFF - u8Idx;&lt;BR /&gt;readBackData=&amp;nbsp;array[0];&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;//Clear&amp;nbsp;&lt;SPAN&gt;ECSM.EEGR.FR11BI&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;if (ECSM.ESR.R1BC == 0x1)&lt;BR /&gt; {&lt;BR /&gt; ECSM.ESR.R1BC = 0x1;&lt;/P&gt;&lt;P&gt;}&lt;BR /&gt;else&lt;BR /&gt;{&lt;BR /&gt;/*Nothing to do.*/&lt;BR /&gt;}&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;To be more specifically, I can see the R1BC clear to 0, but after half a second it is put back to 1.I can clear it, if I deactivate the ECC 1-bit RAM reporting. But, later if I re-activate it, the R1BC automically sets (restores more like it) itself. I've looked through the errata, but I didn't find anything similar. This is for SPC5605B. Did anybody else run into this scenario ? if so, is there a way-around ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Sep 2016 09:52:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Can-not-clear-ECSM-ESR-R1BC/m-p/633778#M5983</guid>
      <dc:creator>buzduganandrei</dc:creator>
      <dc:date>2016-09-20T09:52:30Z</dc:date>
    </item>
    <item>
      <title>Re: Can not clear ECSM.ESR.R1BC</title>
      <link>https://community.nxp.com/t5/MPC5xxx/Can-not-clear-ECSM-ESR-R1BC/m-p/633779#M5984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ECC mechanism corrects 1-bit errors internally, NOT in RAM.&amp;nbsp;The correct data is passed to the core, but the RAM remains corrupted.&amp;nbsp;Because of this, the original address with the error needs to be written with a good data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 Sep 2016 13:04:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MPC5xxx/Can-not-clear-ECSM-ESR-R1BC/m-p/633779#M5984</guid>
      <dc:creator>buzduganandrei</dc:creator>
      <dc:date>2016-09-20T13:04:36Z</dc:date>
    </item>
  </channel>
</rss>

