Fail to build Yocto image for imx8mm-var-dart

General Discussions
,
1

Hi Drew,

I have tried the exact instruction above to build an image, but bitbake gives this error during build process:

ERROR: u-boot-variscite-1.0-r0 do_patch: Command Error: ‘quilt --quiltrc /home/user/mender-variscite/build/tmp/work/imx8mm_var_dart-poky-linux/u-boot-variscite/1.0-r0/recipe-sysroot-native/etc/quiltrc push’ exited with 0 Output:
Applying patch 0001-Switch-to-CONFIG_DISTRO_DEFAULTS-for-bootcmd.patch
patching file configs/imx8mm_var_dart_defconfig
patching file include/configs/imx8mm_var_dart.h
Hunk #2 FAILED at 103.
Hunk #3 FAILED at 129.
Hunk #4 succeeded at 238 (offset 9 lines).
Hunk #5 succeeded at 304 (offset 9 lines).
2 out of 5 hunks FAILED – rejects in file include/configs/imx8mm_var_dart.h
Patch 0001-Switch-to-CONFIG_DISTRO_DEFAULTS-for-bootcmd.patch does not apply (enforce with -f)
ERROR: Logfile of failure stored in: /home/user/mender-variscite/build/tmp/work/imx8mm_var_dart-poky-linux/u-boot-variscite/1.0-r0/temp/log.do_patch.3275585
ERROR: Task (/home/user/mender-variscite/sources/meta-variscite-imx/recipes-bsp/u-boot/u-boot-variscite.bb:do_patch) failed with exit code ‘1’

This is the build configuration:

Build Configuration:
BB_VERSION = “1.44.0”
BUILD_SYS = “x86_64-linux”
NATIVELSBSTRING = “ubuntu-20.04”
TARGET_SYS = “aarch64-poky-linux”
MACHINE = “imx8mm-var-dart”
DISTRO = “fsl-imx-xwayland”
DISTRO_VERSION = “5.4-zeus”
TUNE_FEATURES = “aarch64 cortexa53 crc crypto”
TARGET_FPU = “”
meta
meta-poky = “HEAD:0275e68b0576cdefc19718e4b1977044f9f43f48”
meta-oe
meta-multimedia
meta-python = “HEAD:aad5b3d070cd8c58828b0975cf861d8ebc90f460”
meta-freescale = “HEAD:0be39721cea6e04c589a419f4bb07fabd0da6704”
meta-freescale-3rdparty = “HEAD:aea3771baa77e74762358ceb673d407e36637e5f”
meta-freescale-distro = “HEAD:ca27d12e4964d1336e662bcc60184bbff526c857”
meta-bsp
meta-sdk
meta-ml = “HEAD:64918e055f82e7c1d622a28856fb7ca1d1b93b47”
meta-browser = “HEAD:5f365ef0f842ba4651efe88787cf9c63bc8b6cb3”
meta-rust = “HEAD:5cda04c7c2158fc982502ca1e7893f71e4ca1729”
meta-gnome
meta-networking
meta-filesystems = “HEAD:aad5b3d070cd8c58828b0975cf861d8ebc90f460”
meta-qt5 = “HEAD:432ad2aa6c3a13253fefc909faba368851d21fb1”
meta-swupdate = “HEAD:8ad6a75e1778cdda671b3d6aea2a9692613020ec”
meta-virtualization = “HEAD:514ce5f6b240600f06b9956737be1e33900bacac”
meta-variscite-imx = “HEAD:037ae3cab30fcaeb17d465ff41efcb68c0a21a22”
meta-mender-core
meta-mender-demo = “HEAD:ecf6cf362db527a6a03e6f3c4163234a2ea6c732”
meta-mender-variscite = “HEAD:74ef87d353d952351a32038425a6eb9bb05dca5a”

Any Idea?

Thanks
Hadi

2

It seems something has changed in the u-boot sources since this config was last tested. You’ll need to figure out how to modify the patch in question to get it to build. But note that Zeus has been unsupported for several years by now so you may be better off starting with a newer build from Variscite.

Drew

3

Hi Drew

Thanks for your quick answer. Actually I am doing board integration for this board (VAR-SOM-mx8m-mini) for dunfell and so far It has been unsuccessful. So, I thought maybe it is a good idea to first see how it has done on previous version (zeus). It is really strange that why there is nothing about that for dunfell in community. Is there any specific problem about dunfell so nobody have had success?

B.R
Hadi

4

Not likely anything specific; just nobody has had the need to do it.
Drew

1 Like
5

@h_fotoohi what @drewmoseley said :slight_smile:

If you get started and run into problems, please just ask and we can work them out.

Greetz,
Josef