<?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>i.MX SolutionsのトピックRe: [iMX8MM] Programming and loading M4 firmware and Linux image on eMMC</title>
    <link>https://community.nxp.com/t5/i-MX-Solutions/iMX8MM-Programming-and-loading-M4-firmware-and-Linux-image-on/m-p/2059647#M586</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/80560"&gt;@alanlow&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I have only experience from the iMX7ULP, but I guess the process is similar.&lt;BR /&gt;&lt;BR /&gt;On page 11 in the "Getting started with MCU Expressor for evk imx7ulp" under point 7:&lt;/P&gt;&lt;P&gt;&lt;A title="MCUXSDKIMX7ULPGSUG" href="https://mcuxpresso.nxp.com/api_doc/dev/4662_doc/Getting%20Started%20with%20MCUXpresso%20SDK%20for%20EVK-MCIMX7ULP.pdf" target="_self"&gt;Getting Started with MCUXpresso SDK for EVK-MCIMX7ULP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The text is providing the following information:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;7. Power on the board and hit any key to stop autoboot in the terminals, then enter to U-Boot command-line&amp;nbsp;mode. You can then write the image and run it from QSPI Flash with the following commands (Assume&amp;nbsp;that image size is less than 0x20000, otherwise the sf erase and write command size parameter must be&amp;nbsp;enlarged. If the image size is bigger than 0x20000 (128 kB), change 0x20000 to a number larger or equal to&amp;nbsp;the image size.):&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;The following are the commands to load the image for the M4 processor:&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;sf probe.&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;sf erase 0x0 0x20000&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;fatload mmc 0:1 0x62000000 sdk20-app.img&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;sf write 0x62000000 0x0 0x20000.&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I would interpretate the last line such that the image is written to the memory location starting at 0x62000000. I guess that it must be something similar for the iMX8?&lt;/P&gt;</description>
    <pubDate>Tue, 11 Mar 2025 15:19:51 GMT</pubDate>
    <dc:creator>HenrikZ</dc:creator>
    <dc:date>2025-03-11T15:19:51Z</dc:date>
    <item>
      <title>[iMX8MM] Programming and loading M4 firmware and Linux image on eMMC</title>
      <link>https://community.nxp.com/t5/i-MX-Solutions/iMX8MM-Programming-and-loading-M4-firmware-and-Linux-image-on/m-p/2056115#M584</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I need to store both M4 firmware and Linux image into eMMC and load the M4 firmware to M4 core followed by Linux bootup upon system start up.&lt;/P&gt;&lt;P&gt;Need help on understanding the followings:&lt;/P&gt;&lt;P&gt;- Any specific eMMC location use to store M4 firmware?&lt;/P&gt;&lt;P&gt;- How to use "uuu" to program M4 firmware to specific eMMC location?&lt;/P&gt;&lt;P&gt;- How to load M4 firmware to M4 MCU from specific eMMC location?&lt;/P&gt;&lt;P&gt;Any documentation or examples would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 05 Mar 2025 08:41:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Solutions/iMX8MM-Programming-and-loading-M4-firmware-and-Linux-image-on/m-p/2056115#M584</guid>
      <dc:creator>alanlow</dc:creator>
      <dc:date>2025-03-05T08:41:47Z</dc:date>
    </item>
    <item>
      <title>Re: [iMX8MM] Programming and loading M4 firmware and Linux image on eMMC</title>
      <link>https://community.nxp.com/t5/i-MX-Solutions/iMX8MM-Programming-and-loading-M4-firmware-and-Linux-image-on/m-p/2059647#M586</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/80560"&gt;@alanlow&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I have only experience from the iMX7ULP, but I guess the process is similar.&lt;BR /&gt;&lt;BR /&gt;On page 11 in the "Getting started with MCU Expressor for evk imx7ulp" under point 7:&lt;/P&gt;&lt;P&gt;&lt;A title="MCUXSDKIMX7ULPGSUG" href="https://mcuxpresso.nxp.com/api_doc/dev/4662_doc/Getting%20Started%20with%20MCUXpresso%20SDK%20for%20EVK-MCIMX7ULP.pdf" target="_self"&gt;Getting Started with MCUXpresso SDK for EVK-MCIMX7ULP&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The text is providing the following information:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;7. Power on the board and hit any key to stop autoboot in the terminals, then enter to U-Boot command-line&amp;nbsp;mode. You can then write the image and run it from QSPI Flash with the following commands (Assume&amp;nbsp;that image size is less than 0x20000, otherwise the sf erase and write command size parameter must be&amp;nbsp;enlarged. If the image size is bigger than 0x20000 (128 kB), change 0x20000 to a number larger or equal to&amp;nbsp;the image size.):&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;The following are the commands to load the image for the M4 processor:&lt;BR /&gt;&lt;STRONG&gt;&lt;EM&gt;sf probe.&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;sf erase 0x0 0x20000&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;fatload mmc 0:1 0x62000000 sdk20-app.img&lt;/EM&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;EM&gt;sf write 0x62000000 0x0 0x20000.&lt;/EM&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I would interpretate the last line such that the image is written to the memory location starting at 0x62000000. I guess that it must be something similar for the iMX8?&lt;/P&gt;</description>
      <pubDate>Tue, 11 Mar 2025 15:19:51 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Solutions/iMX8MM-Programming-and-loading-M4-firmware-and-Linux-image-on/m-p/2059647#M586</guid>
      <dc:creator>HenrikZ</dc:creator>
      <dc:date>2025-03-11T15:19:51Z</dc:date>
    </item>
  </channel>
</rss>

