<?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 Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2025762#M232870</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/83537"&gt;@lw1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please accept my sincere apologies for the inconvenience this issue has caused you. I have reported this issue to internal R&amp;amp;D and will get back to you as soon as possible.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Harvey&lt;/P&gt;</description>
    <pubDate>Fri, 10 Jan 2025 11:51:21 GMT</pubDate>
    <dc:creator>Harvey021</dc:creator>
    <dc:date>2025-01-10T11:51:21Z</dc:date>
    <item>
      <title>i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2025478#M232855</link>
      <description>&lt;P&gt;Someone very clever at NXP has changed the firmware-ele-imx-0.1.3-4b30ee5.bin file that is downloaded by the meta-imx recipe via &lt;A href="https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.3-4b30ee5.bin" target="_blank"&gt;https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.3-4b30ee5.bin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;The new file is missing the mx93a1-ahab-container.img and mx91a0-ahab-container.img!&lt;/P&gt;&lt;P&gt;This made it impossible to build yocto images for i.MX91 and i.MX93 even in existing BSP checkouts that previously worked.&lt;/P&gt;&lt;P&gt;They also moved the tag 'rel_imx_6.6.36_2.1.0' meta-imx repository to point to a different commit in the git tree (to fixup the sha256 checksum of the file).&lt;/P&gt;&lt;P&gt;THIS IS A MAJOR F*CK*P that is absolutely inacceptable.&lt;/P&gt;&lt;P&gt;Moving a tag in git is like changing the order numbers in a warehouse catalog after it has been published, so that someone ordering a dish washer from the catalogue will be delivered with a coffee maker instead.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Lothar Waßmann&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 05:48:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2025478#M232855</guid>
      <dc:creator>lw1</dc:creator>
      <dc:date>2025-01-10T05:48:56Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2025762#M232870</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/83537"&gt;@lw1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please accept my sincere apologies for the inconvenience this issue has caused you. I have reported this issue to internal R&amp;amp;D and will get back to you as soon as possible.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Harvey&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 11:51:21 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2025762#M232870</guid>
      <dc:creator>Harvey021</dc:creator>
      <dc:date>2025-01-10T11:51:21Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2025819#M232876</link>
      <description>&lt;P&gt;Both&amp;nbsp;&lt;SPAN&gt;mx93a1-ahab-container.img and mx91a0-ahab-container.img were also removed in&amp;nbsp;&lt;A href="https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.2-4ed450a.bin" target="_blank"&gt;https://www.nxp.com/lgfiles/NMG/MAD/YOCTO//firmware-ele-imx-0.1.2-4ed450a.bin&lt;/A&gt;&amp;nbsp;which is also preventing me from building.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jan 2025 12:52:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2025819#M232876</guid>
      <dc:creator>dtjones</dc:creator>
      <dc:date>2025-01-10T12:52:14Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2026607#M232930</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/83537"&gt;@lw1&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As the firmware associates to security, I've already replied back to you with system service email. Please feel free to let me know if further concern.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Harvey&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jan 2025 09:15:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2026607#M232930</guid>
      <dc:creator>Harvey021</dc:creator>
      <dc:date>2025-01-13T09:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2026721#M232935</link>
      <description>I have the same issue, no mx93a1-ahab-container.img from &lt;A href="https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.2-4ed450a.bin" target="_blank"&gt;https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.2-4ed450a.bin&lt;/A&gt; so I cannot build for my board anymore</description>
      <pubDate>Mon, 13 Jan 2025 11:56:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2026721#M232935</guid>
      <dc:creator>fabioaiuto</dc:creator>
      <dc:date>2025-01-13T11:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2026754#M232937</link>
      <description>Would you be able to e-mail myself &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/245423"&gt;@dtjones&lt;/a&gt; and &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/234063"&gt;@fabioaiuto&lt;/a&gt; as well? We are both having the same issue.</description>
      <pubDate>Mon, 13 Jan 2025 12:42:17 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2026754#M232937</guid>
      <dc:creator>dtjones</dc:creator>
      <dc:date>2025-01-13T12:42:17Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2027212#M232962</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/245423"&gt;@dtjones&lt;/a&gt;&amp;nbsp; and&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/234063"&gt;@fabioaiuto&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As the firmware-ele associates to security, would you please raise a private support ticket with&amp;nbsp;&lt;SPAN&gt;Confidential assistance&lt;/SPAN&gt;? I'll share that for you both over there,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.nxp.com/support/support:SUPPORTHOME" target="_blank"&gt;Support | NXP Semiconductors&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Harvey&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2025 03:04:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2027212#M232962</guid>
      <dc:creator>Harvey021</dc:creator>
      <dc:date>2025-01-14T03:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2027425#M232977</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/192970"&gt;@Harvey021&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;I'm sorry but this is not related to security. Developers from NXP should only fix the BUG present in scarthgap 6.6.23. The firmware-ele-imx package from meta-imx layer is broken. THe binary downloaded is missing some files. Just push the right recipe fix, please.&lt;BR /&gt;&lt;BR /&gt;I tried to open a support ticket but that was misleading to me. Feel free to contact me.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fabio&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2025 08:51:01 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2027425#M232977</guid>
      <dc:creator>fabioaiuto</dc:creator>
      <dc:date>2025-01-14T08:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2028862#M233042</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/192970"&gt;@Harvey021&lt;/a&gt;&amp;nbsp;, any chance to get 6.6.23 fixed, please let me know...&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2025 08:46:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2028862#M233042</guid>
      <dc:creator>fabioaiuto</dc:creator>
      <dc:date>2025-01-16T08:46:50Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2029255#M233066</link>
      <description>&lt;P&gt;mx93a1-ahab-container.img is missing from:&lt;BR /&gt;&lt;A href="https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.2-4ed450a.bin" target="_blank"&gt;https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.2-4ed450a.bin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;For my platform, boundary-bsp-platform repos (&lt;A href="https://github.com/boundarydevices/boundary-bsp-platform" target="_blank"&gt;https://github.com/boundarydevices/boundary-bsp-platform&lt;/A&gt;) were a bit outdated and mx93a1-ahab-container.img is packaged within:&lt;BR /&gt;&lt;A href="https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-1.3.0-17945fc.bin" target="_blank"&gt;https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-1.3.0-17945fc.bin&lt;/A&gt;&lt;/P&gt;&lt;P&gt;For me, the way to fix it was to update the firmware-ele-imx recipe and fsl-eula-unpack class with the lastest commit on the scarthgap branch :&lt;BR /&gt;&lt;A href="https://raw.githubusercontent.com/Freescale/meta-freescale/be9267fca85959c79b19ab65e48c8f3d7faf2b40/recipes-bsp/firmware-imx/firmware-ele-imx_1.3.0.bb" target="_blank"&gt;https://raw.githubusercontent.com/Freescale/meta-freescale/be9267fca85959c79b19ab65e48c8f3d7faf2b40/recipes-bsp/firmware-imx/firmware-ele-imx_1.3.0.bb&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://raw.githubusercontent.com/Freescale/meta-freescale/be9267fca85959c79b19ab65e48c8f3d7faf2b40/classes/fsl-eula-unpack.bbclass" target="_blank"&gt;https://raw.githubusercontent.com/Freescale/meta-freescale/be9267fca85959c79b19ab65e48c8f3d7faf2b40/classes/fsl-eula-unpack.bbclass&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2025 19:49:34 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2029255#M233066</guid>
      <dc:creator>Louis-HQ</dc:creator>
      <dc:date>2025-01-16T19:49:34Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2033158#M233289</link>
      <description>&lt;P&gt;Please inform me when the i.MX93 firmware has been returned to the download.&lt;/P&gt;&lt;P&gt;I agree with Lothar on this, changing the contents of a download after the URL has been published is absolutely unacceptable, and is having an impact on our work.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jan 2025 11:20:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2033158#M233289</guid>
      <dc:creator>andygoulden</dc:creator>
      <dc:date>2025-01-23T11:20:41Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2036497#M233523</link>
      <description>The meta-freescale and the meta-imx scarthgap-6.6.52-2.2.0 branch both point to 17945fc in firmware-ele-imx_1.3.0.bb&lt;BR /&gt;&lt;BR /&gt;The meta-imx scarthgap-6.6.36-2.1.0 branch uses 4b30ee5, which lacks the imx91 and imx93 support.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://github.com/nxp-imx/meta-imx/commits/scarthgap-6.6.52-2.2.0/meta-imx-bsp/recipes-bsp/firmware-imx/firmware-ele-imx_1.3.0.bb" target="_blank"&gt;https://github.com/nxp-imx/meta-imx/commits/scarthgap-6.6.52-2.2.0/meta-imx-bsp/recipes-bsp/firmware-imx/firmware-ele-imx_1.3.0.bb&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;So Freescale used the correct values and NXP didn't sync the values all branches.</description>
      <pubDate>Fri, 31 Jan 2025 09:25:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2036497#M233523</guid>
      <dc:creator>janmg</dc:creator>
      <dc:date>2025-01-31T09:25:16Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057187#M234783</link>
      <description>&lt;P&gt;Unfortunately the only (not disrupting) and possible solution at the moment is the one suggested by &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/245680"&gt;@Louis-HQ&lt;/a&gt;&lt;/P&gt;&lt;P&gt;Thank you Louis &lt;LI-EMOJI id="lia_winking-face" title=":winking_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;&lt;P&gt;If you want to keep the state-of-the-art you have in your build system you have to add the recipe &lt;STRONG&gt;firmware-ele-imx_1.3.0.bb&lt;/STRONG&gt; in your custom layer or into &lt;STRONG&gt;nxp-imx/meta-imx&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;It is into &lt;A href="https://github.com/nxp-imx/meta-imx/tree/scarthgap-6.6.52-2.2.0" target="_self"&gt;https://github.com/nxp-imx/meta-imx/tree/scarthgap-6.6.52-2.2.0&lt;/A&gt;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;recipes-bsp/firmware-imx/firmware-ele-imx_1.3.0.bb&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And replace the class containing the checksum directly into &lt;STRONG&gt;meta-freescale&lt;/STRONG&gt; (yes this solution sucks)&lt;/P&gt;&lt;P&gt;It is in &lt;A href="https://github.com/Freescale/meta-freescale/tree/scarthgap" target="_self"&gt;https://github.com/Freescale/meta-freescale/tree/scarthgap&lt;/A&gt;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;classes/fsl-eula-unpack.bbclass&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Marco Cavallini | KOAN sas&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Bergamo - Italia &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;embedded software engineering &lt;/EM&gt;&lt;BR /&gt;&lt;A href="https://KoanSoftware.com" target="_self"&gt;&lt;EM&gt;https://KoanSoftware.com&lt;/EM&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Mar 2025 16:15:53 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057187#M234783</guid>
      <dc:creator>marcocavallini</dc:creator>
      <dc:date>2025-03-06T16:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057229#M234784</link>
      <description>&lt;LI-CODE lang="python"&gt;#
# workaround-firmware-ele-imx.sh
#
# Workaround for
# i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin
#
# Run these commands into the 'sources' directory

wget https://raw.githubusercontent.com/Freescale/meta-freescale/be9267fca85959c79b19ab65e48c8f3d7faf2b40/recipes-bsp/firmware-imx/firmware-ele-imx_1.3.0.bb
wget https://raw.githubusercontent.com/Freescale/meta-freescale/be9267fca85959c79b19ab65e48c8f3d7faf2b40/classes/fsl-eula-unpack.bbclass
cp firmware-ele-imx_1.3.0.bb meta-imx/meta-imx-bsp/recipes-bsp/firmware-imx
cp fsl-eula-unpack.bbclass meta-freescale/classes/fsl-eula-unpack.bbclass&lt;/LI-CODE&gt;</description>
      <pubDate>Thu, 06 Mar 2025 16:59:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057229#M234784</guid>
      <dc:creator>marcocavallini</dc:creator>
      <dc:date>2025-03-06T16:59:28Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057558#M234800</link>
      <description>&lt;P&gt;The commit below fixes 6.6.36, but also has comments that encourge to use scarthgap-6.6.52-2.2.0. The firmware-ele-imx-1.3.0.bb uses 17945fc version of, but the preferred version was firmware-ele-imx-0.1.3.bb which uses 4b30ee5.&lt;BR /&gt;&lt;BR /&gt;Apparently the version update confusion was caused while fixing a vulnerability on ELE for IMX91 and IMX93, &lt;SPAN class=""&gt;YOCIMX-8724&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://github.com/nxp-imx/meta-imx/commit/7f8409555aa71138e5f0b18dc73f20ddabeaff1a" target="_blank" rel="noopener"&gt;https://github.com/nxp-imx/meta-imx/commit/7f8409555aa71138e5f0b18dc73f20ddabeaff1a&lt;/A&gt;&lt;BR /&gt;"The firmware-ele-imx 1.3.0 version is not production tested and should be used for development only for i.MX 91 and i.MX 93. Please upgrade to the 6.6.52-2.2.0 release for full production software BSP"&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2025 06:20:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057558#M234800</guid>
      <dc:creator>janmg</dc:creator>
      <dc:date>2025-03-07T06:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057565#M234802</link>
      <description>&lt;P&gt;Wow, a serious issue! Missing image files definitely break builds. This reminds me of the frustration when failing a hard &lt;A href="https://geometrydashjump.com/" target="_self"&gt;Geometry Dash&lt;/A&gt; level near the end. NXP needs a robust version control system. Is there a temporary workaround? Are there public bug reports where we can track progress? Sharing checksums of the correct file would be helpful.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Mar 2025 06:30:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057565#M234802</guid>
      <dc:creator>GiseleKing</dc:creator>
      <dc:date>2025-03-07T06:30:50Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057633#M234806</link>
      <description>Of course moving forward to scarthgap-6.6.52-2.2.0 is the perfect solution.&lt;BR /&gt;The note I posted is a temporary solution for those ho can't upgrade the current situation for several reasons.</description>
      <pubDate>Fri, 07 Mar 2025 07:43:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-meta-imx-broken-due-to-rogue-change-of-firmware-ele-imx-0/m-p/2057633#M234806</guid>
      <dc:creator>marcocavallini</dc:creator>
      <dc:date>2025-03-07T07:43:06Z</dc:date>
    </item>
  </channel>
</rss>

