i.MX Image Build

[SQ1]

Hello NXP team,

I'm now building configurations for FRDM i.MX8MP and select MACHINE = "imx8mp-lpddr4-evk". But Yocto ultimately adopted the Olimex configuration and generated Olimex i.MX8MP EVB. Is this why? Do I need to rebuild the image?

Thanks for the response.

FRDM-IMX8MPLUS 

[pengyong_zhang]

Hi @SQ1 

No, i have not compile it.

B.R

[pengyong_zhang]

Hi @SQ1 

The minimum hard disk space required is about 50 GB.
It is recommended that at least 120 GB is provided, which is enough to compile all backends together. For
building machine learning components, at least 250 GB is recommended.

But, For imx-image-full image and SDK, i suggest you need to reserve at least 500GB disk space size.

B.R

[SQ1]

Do you have the compiled image or SDK file?

[pengyong_zhang]

Hi @SQ1 

what is version do you use? i will try to reproduce your problem in my site. BTW, did you change any code?

B.R

[SQ1]

5.4.0-150-generic. And I‘ve changed <linux/mount.h> to <sys/mount.h> in 'qstorageinfo_linux.cpp' to avoid using patch. I'm now doing 'bitbake imx-image-full' and 'bitbake meta-toolchain-qt6'.

I'm worried that there's not enough disk space for that. Do you have compiled .wic .sh files?

[pengyong_zhang]

HI @SQ1 

For imx8mp frdm board, you should run the MACHINE = "imx8mp-lpddr4-frdm".

B.R

[SQ1]

Hello,

when running 'bitbake imx-image-full', I encountered a compilation error reporting that ‘<linux/mount.h>’ was not found. This header file was unavailable in the SDK or Yocto cross-compilation environment. I attempted to generate a patch and substituted '<sys/mount.h>' but also failed.