<?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>MCU BootloaderのトピックRe: blhost configure-memory operation: what is it actually doing?</title>
    <link>https://community.nxp.com/t5/MCU-Bootloader/blhost-configure-memory-operation-what-is-it-actually-doing/m-p/2356223#M1509</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/250963"&gt;@rdegliesposti&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thank you so much for your interest in our products and for using our community.&lt;/P&gt;
&lt;P&gt;Q:I would like to understand what they are actually doing, considering that the contents of the flash memory remain untouched.&lt;/P&gt;
&lt;P&gt;A: Yes. Those two&amp;nbsp;blhost&amp;nbsp;commands are not programming the flash contents.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#FF0000"&gt;1: fill-memory&lt;/FONT&gt;&amp;nbsp;writes the FlexSPI configuration option to RAM.&lt;/P&gt;
&lt;P&gt;2:&amp;nbsp;&lt;FONT color="#FF0000"&gt;configure-memory&lt;/FONT&gt;&amp;nbsp;tells the ROM bootloader/flashloader to use that RAM-resident option block to initialize/configure the external FlexSPI NOR interface.&lt;/P&gt;
&lt;P&gt;After that, the flash becomes accessible in the required mode, but its contents are still unchanged until a later command such as&amp;nbsp;flash-erase-region&amp;nbsp;,&amp;nbsp;write-memory&amp;nbsp;, or&amp;nbsp;flash-image&amp;nbsp;is issued.”&lt;/P&gt;
&lt;P&gt;For more detail information, you can refer to the application note below:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/docs/en/nxp/application-notes/AN12238.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/nxp/application-notes/AN12238.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mayliu1_0-1777257834092.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/383595i1E3FE00F3DA34FEA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mayliu1_0-1777257834092.png" alt="mayliu1_0-1777257834092.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;mayliu1_0-1777257834092.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;May Liu&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2026 02:48:27 GMT</pubDate>
    <dc:creator>mayliu1</dc:creator>
    <dc:date>2026-04-27T02:48:27Z</dc:date>
    <item>
      <title>blhost configure-memory operation: what is it actually doing?</title>
      <link>https://community.nxp.com/t5/MCU-Bootloader/blhost-configure-memory-operation-what-is-it-actually-doing/m-p/2354225#M1508</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I have a RT102x EVK on which I have enabled HAB and Encrypted XIP. With SPSDK I export a bootable image and then I write it to the Flash using J-Link. The firmware doesn't start. I have verified that it is correctly written by using SEC.&lt;BR /&gt;If I try to write the same binary using SEC's Flash Programmer tool, it runs.&lt;BR /&gt;Upon further investigation, after writing the flash using J-Link, I try to execute `&lt;SPAN&gt;secureprovisioningtool/ProvaCoro1/ext_memory_setup.sh`, and this way the firmware starts.&lt;BR /&gt;In particular, the last two commands seem to be what makes it work:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;echo "### Configure FlexSPI NOR memory using options on address 0x2000 ###"
"$blhost" $blhost_connect -j -- fill-memory 0x2000 4 0xC0000007 word
if [ $? -ge 2 ]; then
    exit 2
fi

"$blhost" $blhost_connect -j -- configure-memory 9 0x2000
if [ $? -ge 2 ]; then
    exit 2
fi&lt;/LI-CODE&gt;&lt;P&gt;&lt;SPAN&gt;I would like to understand what they are actually doing, considering that the contents of the flash memory remain untouched.&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Apr 2026 11:21:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCU-Bootloader/blhost-configure-memory-operation-what-is-it-actually-doing/m-p/2354225#M1508</guid>
      <dc:creator>rdegliesposti</dc:creator>
      <dc:date>2026-04-21T11:21:43Z</dc:date>
    </item>
    <item>
      <title>Re: blhost configure-memory operation: what is it actually doing?</title>
      <link>https://community.nxp.com/t5/MCU-Bootloader/blhost-configure-memory-operation-what-is-it-actually-doing/m-p/2356223#M1509</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/250963"&gt;@rdegliesposti&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P&gt;Thank you so much for your interest in our products and for using our community.&lt;/P&gt;
&lt;P&gt;Q:I would like to understand what they are actually doing, considering that the contents of the flash memory remain untouched.&lt;/P&gt;
&lt;P&gt;A: Yes. Those two&amp;nbsp;blhost&amp;nbsp;commands are not programming the flash contents.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#FF0000"&gt;1: fill-memory&lt;/FONT&gt;&amp;nbsp;writes the FlexSPI configuration option to RAM.&lt;/P&gt;
&lt;P&gt;2:&amp;nbsp;&lt;FONT color="#FF0000"&gt;configure-memory&lt;/FONT&gt;&amp;nbsp;tells the ROM bootloader/flashloader to use that RAM-resident option block to initialize/configure the external FlexSPI NOR interface.&lt;/P&gt;
&lt;P&gt;After that, the flash becomes accessible in the required mode, but its contents are still unchanged until a later command such as&amp;nbsp;flash-erase-region&amp;nbsp;,&amp;nbsp;write-memory&amp;nbsp;, or&amp;nbsp;flash-image&amp;nbsp;is issued.”&lt;/P&gt;
&lt;P&gt;For more detail information, you can refer to the application note below:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/docs/en/nxp/application-notes/AN12238.pdf" target="_blank"&gt;https://www.nxp.com/docs/en/nxp/application-notes/AN12238.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mayliu1_0-1777257834092.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/383595i1E3FE00F3DA34FEA/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mayliu1_0-1777257834092.png" alt="mayliu1_0-1777257834092.png" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;mayliu1_0-1777257834092.png&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best Regards&lt;/P&gt;
&lt;P&gt;May Liu&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 02:48:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/MCU-Bootloader/blhost-configure-memory-operation-what-is-it-actually-doing/m-p/2356223#M1509</guid>
      <dc:creator>mayliu1</dc:creator>
      <dc:date>2026-04-27T02:48:27Z</dc:date>
    </item>
  </channel>
</rss>

