AnsweredAssumed Answered

IMX6ULEVK: Yocto Zeus build error with fsl-image-mfgtool-initramfs

Question asked by Sivakumar Rajachidambaram on May 26, 2020
Latest reply on Jun 9, 2020 by Sivakumar Rajachidambaram

Hi,

 

I am getting build error when I tried to build yocto zeus version of imx6ulevk. Can some one help?

 

$ repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-zeus -m imx-5.4.3-1.0.0.xml

$ repo sync

$ DISTRO=fsl-imx-xwayland MACHINE=imx6ulevk source imx-setup-release.sh -b build-xwayland

$ bitbake core-image-base

 

$ bitbake fsl-image-mfgtool-initramfs
WARNING: Host distribution "rhel-7.6" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Loading cache: 100% |########################################################################################################################################| Time: 0:00:00
Loaded 4067 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.44.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "rhel-7.6"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "imx6ulevk"
DISTRO = "fsl-imx-xwayland"
DISTRO_VERSION = "5.4-zeus"
TUNE_FEATURES = "arm vfp cortexa7 neon thumb callconvention-hard"
TARGET_FPU = "hard"
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:435f5e984856a943986491fddd061734a0b9eba5"
meta-browser = "HEAD:5f365ef0f842ba4651efe88787cf9c63bc8b6cb3"
meta-rust = "HEAD:5cda04c7c2158fc982502ca1e7893f71e4ca1729"
meta-gnome
meta-networking
meta-filesystems = "HEAD:aad5b3d070cd8c58828b0975cf861d8ebc90f460"
meta-qt5 = "HEAD:432ad2aa6c3a13253fefc909faba368851d21fb1"

Initialising tasks: 100% |###################################################################################################################################| Time: 0:00:02
Sstate summary: Wanted 83 Found 0 Missed 83 Current 884 (0% match, 91% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed

NOTE: Setscene tasks completed
ERROR: u-boot-imx-mfgtool-1_2019.04-r0 do_deploy: The recipe u-boot-imx-mfgtool is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/nobackup/sikumar3/zeus_evk/build-xwayland/tmp/deploy/images/imx6ulevk/u-boot-sd-optee-2019.04-r0.imx
(matched in manifest-imx6ulevk-u-boot-imx.deploy)
Please verify which recipe should provide the above files.

The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above.
ERROR: u-boot-imx-mfgtool-1_2019.04-r0 do_deploy: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.
ERROR: Logfile of failure stored in: /zeus_evk/build-xwayland/tmp/work/imx6ulevk-poky-linux-gnueabi/u-boot-imx-mfgtool/1_2019.04-r0/temp/log.do_deploy.7078
ERROR: Task /zeus_evk/sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx-mfgtool_2019.04.bb:do_deploy) failed with exit code '1'

Outcomes