topic IMX6ULEVK: Yocto Zeus build error with fsl-image-mfgtool-initramfs in i.MX Processors

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

sikumar3 — Tue, 26 May 2020 14:21:01 GMT

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'

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

gusarambula — Tue, 26 May 2020 16:25:33 GMT

Hello Sivakumar Rajachidambaram,

This error is most likely due to the Host OS. It looks like you are using Red Hat Linux. The only supported host OS for the i.MX Linux BSP releases is Ubuntu 16.04 or 18.04. (Yocto itself may run in other Linux distributions, but some of the recipes used on the i.MX BSP requires these releases of Ubuntu to work correctly).

Would it be possible for you to switch your host OS to Ubuntu 16.04 or 18.04?

My apologies for the inconvenience.

Regards,

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

sikumar3 — Tue, 26 May 2020 17:07:06 GMT

Hi,

" bitbake fsl-image-mfgtool-initramfs" builds fine in the same RedHat Linux system for Yocto SUMO version.

I am not sure why it is not working for Zeus. I will try the same in Ubuntu 16.04!

Thanks.

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

sikumar3 — Thu, 04 Jun 2020 06:19:38 GMT

I tried to build ubuntu 16.04 and getting the below error. Please find the attachment for the complete log.

sikumar3@88bc6a04a7a0:~/zeus/build$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
Release: 16.04
Codename: xenial
sikumar3@88bc6a04a7a0:~/zeus/build$
sikumar3@88bc6a04a7a0:~/zeus/build$
sikumar3@88bc6a04a7a0:~/zeus/build$
sikumar3@88bc6a04a7a0:~/zeus/build$ bitbake core-image-base
Loading cache: 100% |####################################################################################| Time: 0:00:02
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 = "ubuntu-16.04"
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:06
Sstate summary: Wanted 51 Found 0 Missed 51 Current 1221 (0% match, 95% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
ERROR: core-image-base-1.0-r0 do_image_wic: Execution of '/home/sikumar3/zeus/build/tmp/work/imx6ulevk-poky-linux-gnueabi/core-image-base/1.0-r0/temp/run.do_image_wic.36799' failed with exit code 1:
INFO: Creating image(s)...

Traceback (most recent call last):
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/filemap.py", line 36, in get_block_size
binary_data = fcntl.ioctl(file_obj, 2, struct.pack('I', 0))
OSError: [Errno 22] Invalid argument

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/filemap.py", line 95, in __init__
self.block_size = get_block_size(self._f_image)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/filemap.py", line 38, in get_block_size
raise IOError("Unable to determine block size")
OSError: Unable to determine block size

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/home/sikumar3/zeus/sources/poky/scripts/wic", line 525, in <module>
sys.exit(main(sys.argv[1:]))
File "/home/sikumar3/zeus/sources/poky/scripts/wic", line 520, in main
return hlp.invoke_subcommand(args, parser, hlp.wic_help_usage, subcommands)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/help.py", line 83, in invoke_subcommand
subcmd[0](args, usage)
File "/home/sikumar3/zeus/sources/poky/scripts/wic", line 220, in wic_create_subcommand
native_sysroot, options)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/engine.py", line 189, in wic_create
plugin.do_create()
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/plugins/imager/direct.py", line 86, in do_create
self.create()
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/plugins/imager/direct.py", line 179, in create
self._image.prepare(self)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/plugins/imager/direct.py", line 354, in prepare
imager.kernel_dir, imager.native_sysroot)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/partition.py", line 174, in prepare
kernel_dir, rootfs_dir, native_sysroot)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/plugins/source/rawcopy.py", line 68, in do_prepare_partition
sparse_copy(src, dst)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/filemap.py", line 550, in sparse_copy
fmap = api(src_fname)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/filemap.py", line 532, in filemap
return FilemapFiemap(image, log)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/filemap.py", line 350, in __init__
_FilemapBase.__init__(self, image, log)
File "/home/sikumar3/zeus/sources/poky/scripts/lib/wic/filemap.py", line 98, in __init__
% (self._image_path, err))
wic.filemap.Error: cannot get block size for '/home/sikumar3/zeus/build/tmp/deploy/images/imx6ulevk/u-boot.imx': Unable to determine block size
WARNING: exit code 1 from a shell command.

ERROR: Logfile of failure stored in: /home/sikumar3/zeus/build/tmp/work/imx6ulevk-poky-linux-gnueabi/core-image-base/1.0-r0/temp/log.do_image_wic.36799

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

gusarambula — Thu, 04 Jun 2020 20:29:12 GMT

Hello Sivakumar Rajachidambaram,

I’m sorry to hear you are still encountering problems. Have you installed the requires packages listed on the i.MX Yocto Project User’s Guide?

I’ll try to replicate this error as it does not appear to be a reported issue.

Regards,

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

sikumar3 — Fri, 05 Jun 2020 05:04:12 GMT

Hi,

I have installed all the packages suggested in i.MX Yocto Project User's Guide Rev. L5.4.3_1.0.0, 03/2020.

I am able to resolve the above error using the attached patch file.

Now I am hitting the original issue with fsl-image-mfgtool-initramfs command in Ubuntu 16.04.

$ bitbake -DDD fsl-image-mfgtool-initramfs

DEBUG: u-boot-imx-mfgtool-1_2019.04-r0 do_deploy: Staging files from /home/sikumar3/zeus/build/tmp/work/imx6ulevk-poky-linux-gnueabi/u-boot-imx-mfgtool/1_2019.04-r0/deploy-u-boot-imx-mfgtool to /home/sikumar3/zeus/build/tmp/deploy/images/imx6ulevk
DEBUG: mmc-utils-0.1+gitAUTOINC+aef913e31b-r0 do_populate_sysroot: Executing python function sstate_hardcode_path_unpack
DEBUG: mmc-utils-0.1+gitAUTOINC+aef913e31b-r0 do_populate_sysroot: Python function sstate_hardcode_path_unpack finished
DEBUG: mmc-utils-0.1+gitAUTOINC+aef913e31b-r0 do_populate_sysroot: Staging files from /home/sikumar3/zeus/build/tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/mmc-utils/0.1+gitAUTOINC+aef913e31b-r0/sysroot-destdir to /home/sikumar3/zeus/build/tmp/sysroots-components/cortexa7t2hf-neon/mmc-utils
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:
/home/sikumar3/zeus/build/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.
DEBUG: u-boot-imx-mfgtool-1_2019.04-r0 do_deploy: Python function sstate_task_postfunc finished
ERROR: Logfile of failure stored in: /home/sikumar3/zeus/build/tmp/work/imx6ulevk-poky-linux-gnueabi/u-boot-imx-mfgtool/1_2019.04-r0/temp/log.do_deploy.57913
ERROR: Task (/home/sikumar3/zeus/sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx-mfgtool_2019.04.bb:do_deploy) failed with exit code '1'

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

gusarambula — Sat, 06 Jun 2020 00:35:52 GMT

Hello Sivakumar Rajachidambaram,

I’m glad that you fixed the original problem with the patch, and thank you for sharing it.

The odd thing is that I couldn’t reproduce the issue – I was suspecting a problem with the i.MX6UL EVK Machine configuration but I didn’t encountered any errors.

The error message seems to be because there were some files already built and changes to the configuration, so it’s recommended to perform a clean. Please try doing a clean and baking again and it should work correctly with your patch.

$ bitbake -c clean core-image-base

(This shouldn’t erase sstate so it shouldn’t take as long as with a clean build directory)

I hope this helps!

Regards,

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

sikumar3 — Sat, 06 Jun 2020 01:43:31 GMT

Hi,

I tried "$ bitbake -c clean core-image-base" and baked again. But, it didn't help to resolve the error.

I am getting the same error message in both RHEL 7.4 and Ubuntu 16.04 (Docker) with fsl-image-mfgtool-initramfs.

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

sikumar3 — Wed, 10 Jun 2020 05:51:03 GMT

Hi,

I am able to get past the error with fsl-image-mfgtool-initramfs by adding below line in sources/meta-imx/meta-bsp/recipes-bsp/u-boot/u-boot-imx-mfgtool_2019.04.bb

SSTATE_DUPWHITELIST = "/"

I am not sure whether this is the right way.

Since i am getting the same error with both RHEL 7.4 and Ubuntu 16.04, is there any way to find out the root cause?