<?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: external serial flash memory mapping with mkl16z256vlh4 in Kinetis Microcontrollers</title>
    <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/external-serial-flash-memory-mapping-with-mkl16z256vlh4/m-p/690329#M42512</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;SPI Flash is not memory mapped so it doesn't fit into the Kinetis address space. It is addressed by defining pages and offsets in the pages, which is not related to memory mapping in normal use and so also doesn't have any chance of collisions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It is however possible to virtually memory map it at the API layer - see this video showing this in the uTasker project: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPe9A8qsefzQ%26index%3D12%26list%3DPLWKlVb_MqDQFZAulrUywU30v869JBYi9Q" rel="nofollow" target="_blank"&gt;https://www.youtube.com/watch?v=Pe9A8qsefzQ&amp;amp;index=12&amp;amp;list=PLWKlVb_MqDQFZAulrUywU30v869JBYi9Q&lt;/A&gt;&lt;BR /&gt;It doesn't specifically discuss SPI Flash in the video but the technique is the same and you can in fact see SPi Flash in the diagrams.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The open source uTasker project on GitHub includes support for about 5 different SPI memory manufacturers on most Kinetis parts, including storage display allowing it to be accessed in a virtual memory mapped environment (for file system use, for example) and testing using the same commands shown in the video. It also allows the Kinetis parts, SPI and these SPI Flash devices to be simulated for simplified development and debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Aug 2017 15:46:18 GMT</pubDate>
    <dc:creator>mjbcswitzerland</dc:creator>
    <dc:date>2017-08-01T15:46:18Z</dc:date>
    <item>
      <title>external serial flash memory mapping with mkl16z256vlh4</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/external-serial-flash-memory-mapping-with-mkl16z256vlh4/m-p/690328#M42511</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Interface serial flash memory through SPI with MKL16Z256 controller. how &lt;SPAN style="color: #242729; background-color: #ffffff;"&gt;to know what addresses in the processors address space are to be mapped to that external memory for read and write some data....?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #242729; background-color: #ffffff;"&gt;please help&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Aug 2017 13:35:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/external-serial-flash-memory-mapping-with-mkl16z256vlh4/m-p/690328#M42511</guid>
      <dc:creator>durgeshk</dc:creator>
      <dc:date>2017-08-01T13:35:52Z</dc:date>
    </item>
    <item>
      <title>Re: external serial flash memory mapping with mkl16z256vlh4</title>
      <link>https://community.nxp.com/t5/Kinetis-Microcontrollers/external-serial-flash-memory-mapping-with-mkl16z256vlh4/m-p/690329#M42512</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;SPI Flash is not memory mapped so it doesn't fit into the Kinetis address space. It is addressed by defining pages and offsets in the pages, which is not related to memory mapping in normal use and so also doesn't have any chance of collisions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;It is however possible to virtually memory map it at the API layer - see this video showing this in the uTasker project: &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPe9A8qsefzQ%26index%3D12%26list%3DPLWKlVb_MqDQFZAulrUywU30v869JBYi9Q" rel="nofollow" target="_blank"&gt;https://www.youtube.com/watch?v=Pe9A8qsefzQ&amp;amp;index=12&amp;amp;list=PLWKlVb_MqDQFZAulrUywU30v869JBYi9Q&lt;/A&gt;&lt;BR /&gt;It doesn't specifically discuss SPI Flash in the video but the technique is the same and you can in fact see SPi Flash in the diagrams.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The open source uTasker project on GitHub includes support for about 5 different SPI memory manufacturers on most Kinetis parts, including storage display allowing it to be accessed in a virtual memory mapped environment (for file system use, for example) and testing using the same commands shown in the video. It also allows the Kinetis parts, SPI and these SPI Flash devices to be simulated for simplified development and debugging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Aug 2017 15:46:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Kinetis-Microcontrollers/external-serial-flash-memory-mapping-with-mkl16z256vlh4/m-p/690329#M42512</guid>
      <dc:creator>mjbcswitzerland</dc:creator>
      <dc:date>2017-08-01T15:46:18Z</dc:date>
    </item>
  </channel>
</rss>

