<?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 internal flash execution in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193063#M2330</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;We are considering to use Kinetis part with flex memory of 128K. I would like to partition our flexNVM:&lt;/DIV&gt;&lt;DIV&gt;sector 1) 48 K program code&lt;/DIV&gt;&lt;DIV&gt;sector 2) 48 K program code&lt;/DIV&gt;&lt;DIV&gt;sector 3) 32 K Eprom data storage.&lt;/DIV&gt;&lt;DIV&gt;If my program is executing from internal flash flexNVM in sector 1, can this program write into sector 2 or sector 3.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thank you for your help,&lt;/DIV&gt;&lt;DIV&gt;Alex B.&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 24 Mar 2011 04:12:13 GMT</pubDate>
    <dc:creator>alex_br</dc:creator>
    <dc:date>2011-03-24T04:12:13Z</dc:date>
    <item>
      <title>internal flash execution</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193063#M2330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;Hi,&lt;/DIV&gt;&lt;DIV&gt;We are considering to use Kinetis part with flex memory of 128K. I would like to partition our flexNVM:&lt;/DIV&gt;&lt;DIV&gt;sector 1) 48 K program code&lt;/DIV&gt;&lt;DIV&gt;sector 2) 48 K program code&lt;/DIV&gt;&lt;DIV&gt;sector 3) 32 K Eprom data storage.&lt;/DIV&gt;&lt;DIV&gt;If my program is executing from internal flash flexNVM in sector 1, can this program write into sector 2 or sector 3.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Thank you for your help,&lt;/DIV&gt;&lt;DIV&gt;Alex B.&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 24 Mar 2011 04:12:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193063#M2330</guid>
      <dc:creator>alex_br</dc:creator>
      <dc:date>2011-03-24T04:12:13Z</dc:date>
    </item>
    <item>
      <title>Re: internal flash execution</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193064#M2331</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Because sector 1 and 2 are on the same flexNVM block, read data cannot be guaranteed from a Flash block that is being writen.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2011 16:06:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193064#M2331</guid>
      <dc:creator>dani85</dc:creator>
      <dc:date>2011-03-25T16:06:54Z</dc:date>
    </item>
    <item>
      <title>Re: internal flash execution</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193065#M2332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for respose,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you please explain in more details why read data is not garantee during writing to the same block? Is it just protection issue?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Mar 2011 23:42:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193065#M2332</guid>
      <dc:creator>alex_br</dc:creator>
      <dc:date>2011-03-30T23:42:57Z</dc:date>
    </item>
    <item>
      <title>Re: internal flash execution</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193066#M2333</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I found the explanation in the K60 manual:&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;Flash Reads and Ignored Writes&lt;/P&gt;&lt;P&gt;The FTFL module requires only the flash address to execute a flash memory read. MCU&lt;/P&gt;&lt;P&gt;read access is available to all flash blocks.&lt;/P&gt;&lt;P&gt;The MCU must not read from the flash memory while commands are running (as&lt;/P&gt;&lt;P&gt;evidenced by CCIF=0) on that block. Read data cannot be guaranteed from a flash block&lt;/P&gt;&lt;P&gt;while any command is processing within that block. The block arbitration logic detects&lt;/P&gt;&lt;P&gt;any simultaneous access and reports this as a read collision error (see the&lt;/P&gt;&lt;P&gt;FSTAT[RDCOLERR] bit).&lt;/P&gt;&lt;P&gt;"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Apr 2011 21:56:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/internal-flash-execution/m-p/193066#M2333</guid>
      <dc:creator>alex_br</dc:creator>
      <dc:date>2011-04-01T21:56:54Z</dc:date>
    </item>
  </channel>
</rss>

