<?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>LPC Microcontrollersのトピック[LPC5536] Is it possible to access flash below offset when using Dual Boot?</title>
    <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC5536-Is-it-possible-to-access-flash-below-offset-when-using/m-p/1879951#M56185</link>
    <description>&lt;P&gt;If the flash is divided into 2&lt;SPAN&gt;&amp;nbsp;block sizes of 0x1EE00 and the device boots to the 2nd block with an offset of&amp;nbsp;0x1EE00, is it possible to read the flash region below&amp;nbsp;0x1EE00 from within the program? From the example I tried reading a block at a lower flash address like so:&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;memcpy(readPage,&amp;nbsp;0x0,&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;512&lt;/SPAN&gt;&lt;SPAN&gt;);&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;But because the offset is enabled, 0x0 starts at&amp;nbsp;0x1EE00. Is there any way around this to read/write to the lower region?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 03 Jun 2024 15:33:45 GMT</pubDate>
    <dc:creator>bvp</dc:creator>
    <dc:date>2024-06-03T15:33:45Z</dc:date>
    <item>
      <title>[LPC5536] Is it possible to access flash below offset when using Dual Boot?</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC5536-Is-it-possible-to-access-flash-below-offset-when-using/m-p/1879951#M56185</link>
      <description>&lt;P&gt;If the flash is divided into 2&lt;SPAN&gt;&amp;nbsp;block sizes of 0x1EE00 and the device boots to the 2nd block with an offset of&amp;nbsp;0x1EE00, is it possible to read the flash region below&amp;nbsp;0x1EE00 from within the program? From the example I tried reading a block at a lower flash address like so:&lt;/SPAN&gt;&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;memcpy(readPage,&amp;nbsp;0x0,&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;512&lt;/SPAN&gt;&lt;SPAN&gt;);&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;But because the offset is enabled, 0x0 starts at&amp;nbsp;0x1EE00. Is there any way around this to read/write to the lower region?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 03 Jun 2024 15:33:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC5536-Is-it-possible-to-access-flash-below-offset-when-using/m-p/1879951#M56185</guid>
      <dc:creator>bvp</dc:creator>
      <dc:date>2024-06-03T15:33:45Z</dc:date>
    </item>
    <item>
      <title>Re: [LPC5536] Is it possible to access flash below offset when using Dual Boot?</title>
      <link>https://community.nxp.com/t5/LPC-Microcontrollers/LPC5536-Is-it-possible-to-access-flash-below-offset-when-using/m-p/1885827#M56227</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;First of all, in dual image boot, the application code image can be put to different flash address, it is okay that the application code is put in the higher half flash space and executed, and you can access the lower half flash space.&lt;/P&gt;
&lt;P&gt;Regarding the function memcpy(readPage, 0x0, 512); I suppose that the readPage destination address is absolute RAM address, when the source address is in lower half flash space(0x0), you will access the lower half flash space, when the source address is in higher half flash space(0x20000), you will access the higher half flash space.&lt;/P&gt;
&lt;P&gt;Hope it can help you&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;XiangJun Rong&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 06:28:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/LPC-Microcontrollers/LPC5536-Is-it-possible-to-access-flash-below-offset-when-using/m-p/1885827#M56227</guid>
      <dc:creator>xiangjun_rong</dc:creator>
      <dc:date>2024-06-12T06:28:45Z</dc:date>
    </item>
  </channel>
</rss>

