<?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 u-boot-imx FIT image support in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1829321#M221330</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm a bit confused regarding which u-boot to use (mainline or nxp).&lt;/P&gt;&lt;P&gt;As I can see, the u-boot-imx does not support FIT images. Is that correct?&lt;/P&gt;&lt;P&gt;(see bootm command &lt;A href="https://github.com/nxp-imx/uboot-imx/blob/lf_v2022.04/cmd/bootm.c" target="_blank"&gt;https://github.com/nxp-imx/uboot-imx/blob/lf_v2022.04/cmd/bootm.c&lt;/A&gt; )&lt;/P&gt;&lt;P&gt;Can you confirm this?&lt;BR /&gt;What's the reason for that decision? I thought u-boot-nxp was supposed to stay close to mainline?&lt;/P&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 15 Mar 2024 10:21:33 GMT</pubDate>
    <dc:creator>mprt42</dc:creator>
    <dc:date>2024-03-15T10:21:33Z</dc:date>
    <item>
      <title>u-boot-imx FIT image support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1829321#M221330</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm a bit confused regarding which u-boot to use (mainline or nxp).&lt;/P&gt;&lt;P&gt;As I can see, the u-boot-imx does not support FIT images. Is that correct?&lt;/P&gt;&lt;P&gt;(see bootm command &lt;A href="https://github.com/nxp-imx/uboot-imx/blob/lf_v2022.04/cmd/bootm.c" target="_blank"&gt;https://github.com/nxp-imx/uboot-imx/blob/lf_v2022.04/cmd/bootm.c&lt;/A&gt; )&lt;/P&gt;&lt;P&gt;Can you confirm this?&lt;BR /&gt;What's the reason for that decision? I thought u-boot-nxp was supposed to stay close to mainline?&lt;/P&gt;&lt;P&gt;Thanks a lot!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Mar 2024 10:21:33 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1829321#M221330</guid>
      <dc:creator>mprt42</dc:creator>
      <dc:date>2024-03-15T10:21:33Z</dc:date>
    </item>
    <item>
      <title>Re: u-boot-imx FIT image support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1831489#M221492</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;I cannot find such limitation, could you share where did you see such?&lt;BR /&gt;&lt;BR /&gt;Best regards/Saludos,&lt;BR /&gt;Aldo.&lt;/P&gt;</description>
      <pubDate>Tue, 19 Mar 2024 23:11:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1831489#M221492</guid>
      <dc:creator>AldoG</dc:creator>
      <dc:date>2024-03-19T23:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: u-boot-imx FIT image support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1841810#M222211</link>
      <description>&lt;P&gt;Hello AldoG,&lt;/P&gt;&lt;P&gt;First of all, this "case IMAGE_FORMAT_FIT" is missing in the do_bootm function:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/t5/i-MX-Processors/Patch-for-u-boot-imx-Using-FIT-and-HAB-in-bootm-command/m-p/1164472" target="_blank"&gt;https://community.nxp.com/t5/i-MX-Processors/Patch-for-u-boot-imx-Using-FIT-and-HAB-in-bootm-command/m-p/1164472&lt;/A&gt;&lt;/P&gt;&lt;P&gt;And in addition to that, I get some cache alignment errors when the sha256 of my FIT image components are calculated.&lt;/P&gt;&lt;PRE&gt;## Checking Image at 12000000 ...&lt;BR /&gt;FIT image found&lt;BR /&gt;FIT description: Kernel fitImage for NXP i.MX Release Distro/5.15.71+gitAUTOINC+50912be386/acp-imx6pos&lt;BR /&gt;Created: 2023-09-12 22:17:59 UTC&lt;BR /&gt;Image 0 (kernel-1)&lt;BR /&gt;Description: Linux kernel&lt;BR /&gt;Created: 2023-09-12 22:17:59 UTC&lt;BR /&gt;Type: Kernel Image&lt;BR /&gt;Compression: uncompressed&lt;BR /&gt;Data Start: 0x12000108&lt;BR /&gt;Data Size: 9274656 Bytes = 8.8 MiB&lt;BR /&gt;Architecture: ARM&lt;BR /&gt;OS: Linux&lt;BR /&gt;Load Address: 0x10008000&lt;BR /&gt;Entry Point: 0x10008000&lt;BR /&gt;Hash algo: sha256&lt;BR /&gt;Hash value: 3198aa66117966a11ea3c07f3e3d7c613bb9958f70e999c8e8897642d7544c7b&lt;BR /&gt;Image 1 (fdt-imx6dl.dtb)&lt;BR /&gt;Description: Flattened Device Tree blob&lt;BR /&gt;Created: 2023-09-12 22:17:59 UTC&lt;BR /&gt;Type: Flat Device Tree&lt;BR /&gt;Compression: uncompressed&lt;BR /&gt;Data Start: 0x128d873c&lt;BR /&gt;Data Size: 44419 Bytes = 43.4 KiB&lt;BR /&gt;Architecture: ARM&lt;BR /&gt;Hash algo: sha256&lt;BR /&gt;Hash value: 50751df99acda6d9bfe27dc0a558216e493c707f9fecce2238adcfb2f6788863&lt;BR /&gt;Default Configuration: 'conf-imx6dl.dtb'&lt;BR /&gt;Configuration 0 (conf-imx6dl.dtb)&lt;BR /&gt;Description: 1 Linux kernel, FDT blob&lt;BR /&gt;Kernel: kernel-1&lt;BR /&gt;FDT: fdt-imx6dl.dtb&lt;BR /&gt;Hash algo: sha256&lt;BR /&gt;Hash value: unavailable&lt;BR /&gt;## Checking hash(es) for FIT Image at 12000000 ...&lt;BR /&gt;Hash(es) for Image 0 (kernel-1): sha256CACHE: Misaligned operation at range [12000108, 128d8648]&lt;BR /&gt;CACHE: Misaligned operation at range [4e76b0d8, 4e76b118]&lt;BR /&gt;CACHE: Misaligned operation at range [4e76b0d8, 4e76b118]&lt;BR /&gt;ERROR: v7_outer_cache_inval_range - start address is not aligned - 0x4e76b0d8&lt;BR /&gt;ERROR: v7_outer_cache_inval_range - stop address is not aligned - 0x4e76b118&lt;BR /&gt;CACHE: Misaligned operation at range [4e76b0d8, 4e76b118]&lt;BR /&gt;CACHE: Misaligned operation at range [4e76b0d8, 4e76b118]&lt;BR /&gt;ERROR: v7_outer_cache_inval_range - start address is not aligned - 0x4e76b0d8&lt;BR /&gt;ERROR: v7_outer_cache_inval_range - stop address is not aligned - 0x4e76b118&lt;BR /&gt;error!&lt;BR /&gt;Bad hash value for 'hash-1' hash node in 'kernel-1' image node&lt;BR /&gt;Bad hash in FIT image&amp;nbsp;&lt;/PRE&gt;&lt;P&gt;It seems to me as if FIT images are not widely used and tested yet.&lt;BR /&gt;Is there any "known-good" way to build a FIT-image-based distro and u-boot for example for imx6dlsabresd?&lt;BR /&gt;&lt;BR /&gt;Also, u-boot-imx and mainline (or fslc) have deviated quite a bit, making switching very complicated.&lt;BR /&gt;Do you have any plans on getting back closer to mainline? If not, may I learn the motivation behind maintaining your "own u-boot"?&lt;BR /&gt;&lt;BR /&gt;Thanks a lot!&lt;/P&gt;</description>
      <pubDate>Sun, 07 Apr 2024 21:38:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1841810#M222211</guid>
      <dc:creator>mprt42</dc:creator>
      <dc:date>2024-04-07T21:38:34Z</dc:date>
    </item>
    <item>
      <title>Re: u-boot-imx FIT image support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1846044#M222445</link>
      <description>&lt;P&gt;Furthermore, here &lt;SPAN class=""&gt;&lt;A href="https://community.nxp.com/t5/user/viewprofilepage/user-id/207913" target="_self"&gt;&lt;SPAN class=""&gt;hector_delgado&lt;/SPAN&gt;&lt;/A&gt;&lt;/SPAN&gt; states that you don't support FIT images (at all?) on the i.MX 6UL:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/t5/i-MX-Processors/u-boot-crashed-at-caam-hash-while-verifying-sha256-checksum-of/m-p/1729105/highlight/true#M213133" target="_blank" rel="noopener"&gt;https://community.nxp.com/t5/i-MX-Processors/u-boot-crashed-at-caam-hash-while-verifying-sha256-checksum-of/m-p/1729105/highlight/true#M213133&lt;/A&gt;&lt;/P&gt;&lt;P&gt;can you elaborate a bit more on that?&lt;BR /&gt;What's the current state?&lt;/P&gt;</description>
      <pubDate>Fri, 12 Apr 2024 10:41:13 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1846044#M222445</guid>
      <dc:creator>mprt42</dc:creator>
      <dc:date>2024-04-12T10:41:13Z</dc:date>
    </item>
    <item>
      <title>Re: u-boot-imx FIT image support</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1848130#M222597</link>
      <description>&lt;P&gt;I made some further experiments and it turns out that somehow the hardware accellerated SHA256 requires the data to be cache aligned.&lt;BR /&gt;If i disable FSL_CAAM, i.e. force software SHA256, it works.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Is there any way to solve this?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Apr 2024 12:36:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/u-boot-imx-FIT-image-support/m-p/1848130#M222597</guid>
      <dc:creator>mprt42</dc:creator>
      <dc:date>2024-04-16T12:36:36Z</dc:date>
    </item>
  </channel>
</rss>

