i.MX93 meta-imx broken due to rogue change of firmware-ele-imx-0.1.3-4b30ee5.bin

[lw1]

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 https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.3-4b30ee5.bin

The new file is missing the mx93a1-ahab-container.img and mx91a0-ahab-container.img!

This made it impossible to build yocto images for i.MX91 and i.MX93 even in existing BSP checkouts that previously worked.

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).

THIS IS A MAJOR F*CK*P that is absolutely inacceptable.

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.

Lothar Waßmann

[GiseleKing]

Wow, a serious issue! Missing image files definitely break builds. This reminds me of the frustration when failing a hard Geometry Dash 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.

[Louis-HQ]

mx93a1-ahab-container.img is missing from:
https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.2-4ed450a.bin

For my platform, boundary-bsp-platform repos (https://github.com/boundarydevices/boundary-bsp-platform) were a bit outdated and mx93a1-ahab-container.img is packaged within:
https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-1.3.0-17945fc.bin

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 :
https://raw.githubusercontent.com/Freescale/meta-freescale/be9267fca85959c79b19ab65e48c8f3d7faf2b40/...
https://raw.githubusercontent.com/Freescale/meta-freescale/be9267fca85959c79b19ab65e48c8f3d7faf2b40/...

[marcocavallini]

Unfortunately the only (not disrupting) and possible solution at the moment is the one suggested by @Louis-HQ

Thank you Louis

If you want to keep the state-of-the-art you have in your build system you have to add the recipe firmware-ele-imx_1.3.0.bb in your custom layer or into nxp-imx/meta-imx

It is into https://github.com/nxp-imx/meta-imx/tree/scarthgap-6.6.52-2.2.0

recipes-bsp/firmware-imx/firmware-ele-imx_1.3.0.bb

And replace the class containing the checksum directly into meta-freescale (yes this solution sucks)

It is in https://github.com/Freescale/meta-freescale/tree/scarthgap

classes/fsl-eula-unpack.bbclass

--

Marco Cavallini | KOAN sas
Bergamo - Italia
embedded software engineering
https://KoanSoftware.com

[marcocavallini]

#
# 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

[janmg]

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

The meta-imx scarthgap-6.6.36-2.1.0 branch uses 4b30ee5, which lacks the imx91 and imx93 support.

https://github.com/nxp-imx/meta-imx/commits/scarthgap-6.6.52-2.2.0/meta-imx-bsp/recipes-bsp/firmware...

So Freescale used the correct values and NXP didn't sync the values all branches.

[janmg]

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.

Apparently the version update confusion was caused while fixing a vulnerability on ELE for IMX91 and IMX93, YOCIMX-8724

https://github.com/nxp-imx/meta-imx/commit/7f8409555aa71138e5f0b18dc73f20ddabeaff1a
"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"

[marcocavallini]

Of course moving forward to scarthgap-6.6.52-2.2.0 is the perfect solution.
The note I posted is a temporary solution for those ho can't upgrade the current situation for several reasons.

[Harvey021]

Hello @lw1 

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.

Regards

Harvey

[dtjones]

Would you be able to e-mail myself @dtjones and @fabioaiuto as well? We are both having the same issue.

[Harvey021]

Hi @dtjones  and @fabioaiuto 

As the firmware-ele associates to security, would you please raise a private support ticket with Confidential assistance? I'll share that for you both over there, 

Support | NXP Semiconductors

Regards

Harvey

[fabioaiuto]

@Harvey021 , any chance to get 6.6.23 fixed, please let me know...

[fabioaiuto]

@Harvey021 ,

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.

I tried to open a support ticket but that was misleading to me. Feel free to contact me.

Fabio

[dtjones]

Both mx93a1-ahab-container.img and mx91a0-ahab-container.img were also removed in https://www.nxp.com/lgfiles/NMG/MAD/YOCTO//firmware-ele-imx-0.1.2-4ed450a.bin which is also preventing me from building.

[Harvey021]

Hello @lw1 

Please accept my sincere apologies for the inconvenience this issue has caused you. I have reported this issue to internal R&D and will get back to you as soon as possible.

Regards

Harvey

[andygoulden]

Please inform me when the i.MX93 firmware has been returned to the download.

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.

[fabioaiuto]

I have the same issue, no mx93a1-ahab-container.img from https://www.nxp.com/lgfiles/NMG/MAD/YOCTO/firmware-ele-imx-0.1.2-4ed450a.bin so I cannot build for my board anymore