<?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>Kinetis MicrocontrollersのトピックKE18F512VLH16 ECC RAM Single Bit Correction</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE18F512VLH16-ECC-RAM-Single-Bit-Correction/m-p/2404369#M68466</link>
    <description>&lt;P&gt;I have a follow up question related to&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/90401"&gt;@sean_dvorscak&lt;/a&gt;'s post the other day (&lt;A href="https://community.nxp.com/t5/Kinetis-Microcontrollers/KE1-ECC-RAM-Single-Bit-Corrrection/m-p/2399360#M68449" target="_blank"&gt;KE1 ECC RAM Single Bit Corrrection&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/237877"&gt;@Celeste_Liu&lt;/a&gt;&amp;nbsp;replied,&lt;BR /&gt;&lt;SPAN&gt;-&amp;gt;&amp;gt;&amp;nbsp;If implementing an optional scrub, please align the access according to the actual access size or scrub granularity, not blindly to the raw MCM_LMFAR value. Also don't use a fixed 4-byte access unless you first align the address appropriately and confirm the access size is valid.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can&amp;nbsp;MCM_LMFATR[PEFSIZE] be used to determine the access size? If so, can this be used in tandem with&amp;nbsp;MCM_LMFAR to implement a&amp;nbsp;read-correct-writeback operation? For example, if&amp;nbsp;MCM_LMFATR[PEFSIZE] is 3'b000 indicating an 8-bit access, can I perform an 8-bit read from the address indicated by&amp;nbsp;MCM_LMFAR then perform an 8-bit write to the same address to correct the error. Similarly, if&amp;nbsp;MCM_LMFATR[PEFSIZE] is 3'b010 indicating a 32-bit access, can I perform a 32-bit write to the address indicated by MCM_LMFAR without worrying about alignment?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 13 Aug 2026 00:20:22 GMT</pubDate>
    <dc:creator>rseigle77</dc:creator>
    <dc:date>2026-08-13T00:20:22Z</dc:date>
    <item>
      <title>KE18F512VLH16 ECC RAM Single Bit Correction</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE18F512VLH16-ECC-RAM-Single-Bit-Correction/m-p/2404369#M68466</link>
      <description>&lt;P&gt;I have a follow up question related to&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/90401"&gt;@sean_dvorscak&lt;/a&gt;'s post the other day (&lt;A href="https://community.nxp.com/t5/Kinetis-Microcontrollers/KE1-ECC-RAM-Single-Bit-Corrrection/m-p/2399360#M68449" target="_blank"&gt;KE1 ECC RAM Single Bit Corrrection&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/237877"&gt;@Celeste_Liu&lt;/a&gt;&amp;nbsp;replied,&lt;BR /&gt;&lt;SPAN&gt;-&amp;gt;&amp;gt;&amp;nbsp;If implementing an optional scrub, please align the access according to the actual access size or scrub granularity, not blindly to the raw MCM_LMFAR value. Also don't use a fixed 4-byte access unless you first align the address appropriately and confirm the access size is valid.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can&amp;nbsp;MCM_LMFATR[PEFSIZE] be used to determine the access size? If so, can this be used in tandem with&amp;nbsp;MCM_LMFAR to implement a&amp;nbsp;read-correct-writeback operation? For example, if&amp;nbsp;MCM_LMFATR[PEFSIZE] is 3'b000 indicating an 8-bit access, can I perform an 8-bit read from the address indicated by&amp;nbsp;MCM_LMFAR then perform an 8-bit write to the same address to correct the error. Similarly, if&amp;nbsp;MCM_LMFATR[PEFSIZE] is 3'b010 indicating a 32-bit access, can I perform a 32-bit write to the address indicated by MCM_LMFAR without worrying about alignment?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Aug 2026 00:20:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/KE18F512VLH16-ECC-RAM-Single-Bit-Correction/m-p/2404369#M68466</guid>
      <dc:creator>rseigle77</dc:creator>
      <dc:date>2026-08-13T00:20:22Z</dc:date>
    </item>
  </channel>
</rss>

