<?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 Processors中的主题 Re: Multiple U-Boot Partitions Possible ?</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Multiple-U-Boot-Partitions-Possible/m-p/1346065#M180611</link>
    <description>&lt;P&gt;Instead of two different partitions for u-boot, I guess if there was a way to keep two copies of u-boot in that partition and for the firmware to somehow have a way to decide which one to load.&lt;/P&gt;&lt;P&gt;something similar to how the Raspberry Pi recently introduced tryboot.txt option.&lt;/P&gt;&lt;P&gt;Of course in the absence of such a possibility the only way would be to never update u-boot over OTA. However that doesn't really sound like a "good" approach IMO. How would we patch any u-boot CVEs then or bug in the bootloader ?&lt;/P&gt;</description>
    <pubDate>Sat, 25 Sep 2021 00:24:00 GMT</pubDate>
    <dc:creator>om26er</dc:creator>
    <dc:date>2021-09-25T00:24:00Z</dc:date>
    <item>
      <title>Multiple U-Boot Partitions Possible ?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Multiple-U-Boot-Partitions-Possible/m-p/1346062#M180610</link>
      <description>&lt;P&gt;I am trying to implement A/B partition scheme for OTA updates. The partition structure could look like this:&lt;/P&gt;&lt;P&gt;1. uboot partition 1&lt;/P&gt;&lt;P&gt;2. uboot partition 2&lt;/P&gt;&lt;P&gt;3 rootfs 1 (includes kernel and dtb)&lt;/P&gt;&lt;P&gt;4 rootfs 2 (includes kernel and dtb)&lt;/P&gt;&lt;P&gt;I am trying to understand how does the i.MX 8MM "knows" where to load the bootloader from ? Is there a way to tell the firmware to load the bootloader (u-boot) from a different partition ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;I could go with a simpler approach where I have one u-boot partition and two rootfs. However this comes with a risk of breakage if an OTA update of the u-boot partition goes bad due to some reason. Hence I was wondering if it's possible to have bootloader redundancy in the iMX platform ?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Sep 2021 00:24:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Multiple-U-Boot-Partitions-Possible/m-p/1346062#M180610</guid>
      <dc:creator>om26er</dc:creator>
      <dc:date>2021-09-25T00:24:31Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple U-Boot Partitions Possible ?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Multiple-U-Boot-Partitions-Possible/m-p/1346065#M180611</link>
      <description>&lt;P&gt;Instead of two different partitions for u-boot, I guess if there was a way to keep two copies of u-boot in that partition and for the firmware to somehow have a way to decide which one to load.&lt;/P&gt;&lt;P&gt;something similar to how the Raspberry Pi recently introduced tryboot.txt option.&lt;/P&gt;&lt;P&gt;Of course in the absence of such a possibility the only way would be to never update u-boot over OTA. However that doesn't really sound like a "good" approach IMO. How would we patch any u-boot CVEs then or bug in the bootloader ?&lt;/P&gt;</description>
      <pubDate>Sat, 25 Sep 2021 00:24:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Multiple-U-Boot-Partitions-Possible/m-p/1346065#M180611</guid>
      <dc:creator>om26er</dc:creator>
      <dc:date>2021-09-25T00:24:00Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple U-Boot Partitions Possible ?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Multiple-U-Boot-Partitions-Possible/m-p/1346566#M180663</link>
      <description>&lt;P&gt;Hi Omer&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;gt;I am trying to understand how does the i.MX 8MM "knows" where to load the bootloader from ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;one can look at Table 1. Image layout, Table 53. Board-specific default values&amp;nbsp;&amp;nbsp; &lt;A style="box-sizing: border-box; background-color: transparent; color: #215bd6; text-decoration: none; cursor: pointer;" href="https://www.nxp.com/docs/en/user-guide/IMX_LINUX_USERS_GUIDE.pdf" target="_blank" rel="noopener"&gt;i.MX Linux User’s Guide​&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;some addresses (like loadaddr) can be found in&lt;/P&gt;
&lt;P&gt;&lt;A href="https://source.codeaurora.org/external/imx/uboot-imx/tree/include/configs/imx8mm_evk.h?h=lf_v2021.04" target="_blank"&gt;https://source.codeaurora.org/external/imx/uboot-imx/tree/include/configs/imx8mm_evk.h?h=lf_v2021.04&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards&lt;BR /&gt;igor&lt;/P&gt;</description>
      <pubDate>Mon, 27 Sep 2021 07:11:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Multiple-U-Boot-Partitions-Possible/m-p/1346566#M180663</guid>
      <dc:creator>igorpadykov</dc:creator>
      <dc:date>2021-09-27T07:11:12Z</dc:date>
    </item>
  </channel>
</rss>

