<?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 FlexNV programming issue in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FlexNV-programming-issue/m-p/619677#M37044</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm seeing something strange when programming the FlexNV data section.&amp;nbsp; If I use it as data flash (not EEPROM), I can program it successfully, however, it does not read back the correct data even though the verify operation passes.&amp;nbsp; I see this with both the driver I wrote and with the KSDK driver for the KE18F512.&amp;nbsp; If I restart the debugger, I can then see what I've programmed.&amp;nbsp; Is there some secret to getting it to refresh and show correct data after programming?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Oct 2016 16:24:27 GMT</pubDate>
    <dc:creator>davidsherman</dc:creator>
    <dc:date>2016-10-10T16:24:27Z</dc:date>
    <item>
      <title>FlexNV programming issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FlexNV-programming-issue/m-p/619677#M37044</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm seeing something strange when programming the FlexNV data section.&amp;nbsp; If I use it as data flash (not EEPROM), I can program it successfully, however, it does not read back the correct data even though the verify operation passes.&amp;nbsp; I see this with both the driver I wrote and with the KSDK driver for the KE18F512.&amp;nbsp; If I restart the debugger, I can then see what I've programmed.&amp;nbsp; Is there some secret to getting it to refresh and show correct data after programming?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Oct 2016 16:24:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FlexNV-programming-issue/m-p/619677#M37044</guid>
      <dc:creator>davidsherman</dc:creator>
      <dc:date>2016-10-10T16:24:27Z</dc:date>
    </item>
    <item>
      <title>Re: FlexNV programming issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FlexNV-programming-issue/m-p/619678#M37045</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Flash access via FMC(Flash Memory Controller), which has the 128 (64 for bank1, Data Flash)-bit prefetch speculation buffer with controls for instruction/data access per master and bank.&lt;/P&gt;&lt;P&gt;In default, the speculation buffer is enabled for instruction and data.&lt;/P&gt;&lt;P&gt;Customer could use MSCM_OCMDR1 register (related to data Flash) [OCMC1] bit5 &amp;amp; bit4 to invalidate the speculation buffer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OCMDR1[4] or OCMDR1[5] bit controls whether prefetches (or speculative accesses) are initiated in&lt;BR /&gt;response to instruction fetches or data references, see section FMC speculative reads.&lt;BR /&gt;• OCMDR bit 4: Data Prefetch. Value 0 means enable and value 1 means disable.&lt;BR /&gt;• OCMDR bit 5: Flash Speculate. Value 0 means enable and value 1 means disable.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Wish it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have a great day,&lt;BR /&gt;Ma Hui&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Oct 2016 05:34:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FlexNV-programming-issue/m-p/619678#M37045</guid>
      <dc:creator>Hui_Ma</dc:creator>
      <dc:date>2016-10-11T05:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: FlexNV programming issue</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/FlexNV-programming-issue/m-p/619679#M37046</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you, Ma Hui, that led me on the right track.&amp;nbsp; It turns out the cache was enabled for the FlexNVM as well, so that also had to be disabled to see the change take effect.&amp;nbsp; Now that I understand what was going on I can figure out how to get the cache back in sync.&amp;nbsp; Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Oct 2016 12:51:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/FlexNV-programming-issue/m-p/619679#M37046</guid>
      <dc:creator>davidsherman</dc:creator>
      <dc:date>2016-10-11T12:51:32Z</dc:date>
    </item>
  </channel>
</rss>

