<?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 Uboot Upgrade Stategy in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Uboot-Upgrade-Stategy/m-p/848740#M129902</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I wanted to know if there was a document detailing a standard strategy to upgrading uboot in the field using the second boot partition.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using eMMC and kernel uboot&amp;nbsp;U-Boot 2014.04. Our kernel is based on version&amp;nbsp;3.14.28&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Obviously we want to use the unused partition to upgrade and then only permanently switch to it once it is known to be good. This will stop bricking in the field. (Most devices have an network interface but not USB (or a way to force serial boot mode).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Naveed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Sep 2018 00:51:02 GMT</pubDate>
    <dc:creator>naveedghori</dc:creator>
    <dc:date>2018-09-20T00:51:02Z</dc:date>
    <item>
      <title>Uboot Upgrade Stategy</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Uboot-Upgrade-Stategy/m-p/848740#M129902</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I wanted to know if there was a document detailing a standard strategy to upgrading uboot in the field using the second boot partition.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are using eMMC and kernel uboot&amp;nbsp;U-Boot 2014.04. Our kernel is based on version&amp;nbsp;3.14.28&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Obviously we want to use the unused partition to upgrade and then only permanently switch to it once it is known to be good. This will stop bricking in the field. (Most devices have an network interface but not USB (or a way to force serial boot mode).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Naveed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2018 00:51:02 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Uboot-Upgrade-Stategy/m-p/848740#M129902</guid>
      <dc:creator>naveedghori</dc:creator>
      <dc:date>2018-09-20T00:51:02Z</dc:date>
    </item>
    <item>
      <title>Re: Uboot Upgrade Stategy</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Uboot-Upgrade-Stategy/m-p/848741#M129903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naveed,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10.0pt;"&gt;As you may known, the details for it already in "4.5.7 Software Update and Wipe &lt;STRONG&gt;Partition&lt;/STRONG&gt; using Recovery Mode" in User Guide.&lt;BR /&gt; &lt;BR /&gt; For more details, you may search the information from web. For example :&lt;BR /&gt; &lt;A href="http://www.londatiga.net/it/how-to-create-android-update-zip-package/"&gt;http://www.londatiga.net/it/how-to-create-android-update-zip-package/&lt;/A&gt;&lt;BR /&gt; &lt;BR /&gt; Note that :&lt;BR /&gt; &lt;BR /&gt; setenv bootcmd_android_recovery 'run bootargs_base bootargs_android_recovery;mmc read 0 ${loadaddr} 0x800 0x1800;bootm'&lt;BR /&gt; &lt;BR /&gt; 0x1800 is the size may be too small . Please modify the value that match you needed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Sep 2018 14:53:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Uboot-Upgrade-Stategy/m-p/848741#M129903</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2018-09-21T14:53:57Z</dc:date>
    </item>
    <item>
      <title>Re: Uboot Upgrade Stategy</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Uboot-Upgrade-Stategy/m-p/848742#M129904</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you misunderstand me. I want a strategy to saftely update uboot so that any possibility of bricking the device is removed. THis is for while the device is already programmed and operational in the field.&lt;/P&gt;&lt;P&gt;The switch to the new uboot partition should only happen once we are sure that the new uboot image works.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Current&amp;nbsp;into linux via current uboot&lt;/LI&gt;&lt;LI&gt;Detect current uboot partition&lt;/LI&gt;&lt;LI&gt;Write new uboot into alternative uboot partition&lt;/LI&gt;&lt;LI&gt;Somehow check new partition: eg&amp;nbsp;boot into new uboot once somehow and if it boot then switch on next reboot, if it fails then on next reset we will boot from the previous uboot partition.&lt;/LI&gt;&lt;LI&gt;Once we are happy that the new uboot is good we switch to it.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Hope this is clearer now.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2018 01:56:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Uboot-Upgrade-Stategy/m-p/848742#M129904</guid>
      <dc:creator>naveedghori</dc:creator>
      <dc:date>2018-09-27T01:56:39Z</dc:date>
    </item>
  </channel>
</rss>

