IMX6Q and EDM-Fairy support

Dear TechNexion devs,

For the past 4 weeks, I've been trying to set up any kind of distribution for our IMX6Q and Fairy baseboard product but without any luck. I've managed to build and run some buildroot distros but they are not suitable for the end product. Therefore, I've been trying to compile your Yocto distribution, but to be honest I found the build process very disturbing and not so well documentet. Im not saying that you made anything wrong, but because of my lack of experience in Yocto I can only assume what the entire process should looke like, because I am not able to get it from this repository readme file. Can you please help me with configuring this repository for EDM Fairy and imx6q? I don't see any suitable config files for this setup.

I have also tried to build your older yocto version from your archived repo but I am not able to set up any proper configuration (mostly some paths problems). Strangely, despite following instructions in your README default configs always fail and I can't manage to get it running.

What I need is a working Linux distro with ability to run GTK3 app, playing sounds through alsa, with enabled GPIO and USB drivers.

Thanks in advance!

Yours faithfully, Jakub Dąbroś

@jdabros

To build yocto, could you try the instruction below? https://github.com/TechNexion/edm-yocto-bsp/tree/rocko_4.9.y_GA#for-edm-imx6

FAIRY baseboard, QT5 with X11 image for 7 inch LVDS panel:

For EDM-IMX6 with QCA WLAN: $: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=qca DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=fairy source edm-setup-release.sh -b build-x11-edm-imx6 For EDM-IMX6 with BRCM WLAN: $: DISPLAY=lvds7 WIFI_FIRMWARE=y WIFI_MODULE=brcm DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=fairy source edm-setup-release.sh -b build-x11-edm-imx6 $: bitbake fsl-image-qt5-validation-imx

BR,

Richard

Hi Richard, thanks for your time. I did try that - I've linked to that repo in my first post. Got multiple different errors after playing with it for a couple of hours. Just to make it simpler for you I've made (hopefully) a clean run through build process described in that archived repo.

(base) jdabros@jdabros-HP-Laptop-15-bs0xx:~/edm_yocto$ DISPLAY=lvds7 DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=fairy source edm-setup-release.sh -b build-x11-edm-imx6

Build directory: build-x11-edm-imx6

(...) License stuff here (...)

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    meta-toolchain
    meta-toolchain-sdk
    adt-installer
    meta-ide-support

Your build environment has been configured with:

    MACHINE=edm-imx6
    SDKMACHINE=i686
    DISTRO=fsl-imx-x11
    EULA=
meta-freescale directory found
WARNING - No WIFI_FIRMWARE specified
Selected wifi firmwares: 

(base) jdabros@jdabros-HP-Laptop-15-bs0xx:~/edm_yocto/build-x11-edm-imx6$ bitbake fsl-image-qt5-validation-imx

WARNING: /home/jdabros/edm_yocto/sources/poky/meta/lib/oe/maketype.py:99: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
  if not isinstance(obj, collections.Callable):

NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: Host distribution "ubuntu-19.10" 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.
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry CadenceLicense.txt: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry bdwlan30.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry otp30.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry qwlan30.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry utf30.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry CadenceLicense.txt: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry bdwlan30.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry otp30.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry qwlan30.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry utf30.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry cfg.dat: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry qcom_cfg.ini: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry qcom_cfg.ini: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry notice.txt: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry nvm_tlv_3.2.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry rampatch_tlv_3.2.tlv: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry fw_bcm4339a0_ag.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry fw_bcm4339a0_ag_apsta.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry nvram_ap6335.txt: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry bcm4339a0.hcd: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry fw_bcm43438a0.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry fw_bcm43438a0_apsta.bin: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry nvram_ap6212.txt: file could not be found
WARNING: /home/jdabros/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry bcm43438a0.hcd: file could not be found
Parsing recipes: 100% |#################################################################################################################| Time: 0:02:52
Parsing of 2433 .bb files complete (0 cached, 2433 parsed). 3274 targets, 212 skipped, 10 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Multiple providers are available for virtual/imxvpu (imx-vpu, imx-vpu-hantro)
Consider defining a PREFERRED_PROVIDER entry to match virtual/imxvpu
ERROR: Nothing RPROVIDES 'xf86-video-imxfb-vivante' (but /home/jdabros/edm_yocto/sources/poky/meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'xf86-video-imxfb-vivante' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['xf86-video-imxfb-vivante']
NOTE: Runtime target 'packagegroup-core-x11-xserver' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-core-x11-xserver', 'xf86-video-imxfb-vivante']
NOTE: Runtime target 'packagegroup-core-x11-base' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-core-x11-base', 'packagegroup-core-x11-xserver', 'xf86-video-imxfb-vivante']
ERROR: Required build target 'fsl-image-qt5-validation-imx' has no buildable providers.
Missing or unbuildable dependency chain was: ['fsl-image-qt5-validation-imx', 'packagegroup-core-x11-base', 'packagegroup-core-x11-xserver', 'xf86-video-imxfb-vivante']

Summary: There were 26 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Any ideas how can I repair that?

Just to mention - there was also an error about Python version ( which I've fixed by creaitng some symbolic links to a proper version).

OpenEmbedded requires 'python' to be python v2 (>= 2.7.3), not python v3.
Please set up python v2 as your default 'python' interpreter.

@jdabros

I validate the build for Yocto 2.4, it completes the Yocto build without problem. I'm afraid i can't reproduce the same build problem you mention on our side. (I think it's probably the same procedure as yours. ) My build steps:

Fetch Yocto 2.4 source:
# repo init -u https://github.com/TechNexion/edm-yocto-bsp.git -b rocko_4.9.y_GA -m imx-4.9.88-2.0.0_ga.xml
# repo sync -j8

Configure build target and start the build
# DISPLAY=lvds7 DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=fairy source edm-setup-release.sh -b build-x11-edm-imx6
# bitbake fsl-image-qt5-validation-imx

I notice there is strange warning message from your error message.

ERROR: Nothing RPROVIDES 'xf86-video-imxfb-vivante' (but /home/jdabros/edm_yocto/sources/poky/meta/recipes-graphics/packagegroups/packagegroup-core-x11-xserver.bb RDEPENDS on or otherwise requires it) NOTE: Runtime target 'xf86-video-imxfb-vivante' is unbuildable, removing...

xf86-video-imxfb-vivante package should not be included in fsl-image-qt5-validation-imx. Because the backend you configure is fsl-imx-x11(x-wiindow).

You can check it via the command: # bitbake -g fsl-image-qt5-validation-imx && cat pn-buildlist | grep imxfb

If xf86-video-imxfb-vivante is included in the xf86-video-imxfb-vivante . It's quite unusual.

About python version problem, i notice the ubuntu version you use is ubuntu 19.10. I am not sure that if python 3.0 becomes the default python in ubuntu 19.10. To avoid more build problem, we suggest to try ubuntu 16.04 as your build environment. https://github.com/TechNexion/edm-yocto-bsp/tree/rocko_4.9.y_GA#method-1

Or using virtual machine environment(is based on virtualbox and runs ubuntu 16.04) that TechNexion prepares to build yocto 2.4/2.5. https://github.com/TechNexion/edm-yocto-bsp/tree/rocko_4.9.y_GA#method-2 ftp://ftp.technexion.net/development_resources/development_tools/vm/Build_Env_Ubuntu_x64_16.04-20190307.zip

Running ubuntu 16.04 in docker is alternative. https://github.com/TechNexion/edm-yocto-bsp/tree/rocko_4.9.y_GA#method-3

BR,

Richard

Dear @richard-hu

I have tried using your virtual machine a couple times now. To make it simple I deleted my previous VM and started a new one, freshly from the archive from Technexion.

With first attempt, there was an error about lack of memory. I have solved that through resizing virtual disk and repartitioning of existing hard drives in Ubunut 16.04 virtual machine.

Durign my second try I've encountered another error:

user@user-VirtualBox:~/edm_yocto/build-x11-edm-imx6$ bitbake fsl-image-qt5-validation-imx
NOTE: Your conf/bblayers.conf has been automatically updated.
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry CadenceLicense.txt: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry bdwlan30.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry otp30.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry qwlan30.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry utf30.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry CadenceLicense.txt: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry bdwlan30.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry otp30.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry qwlan30.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry utf30.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry cfg.dat: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry qcom_cfg.ini: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry qcom_cfg.ini: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry notice.txt: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry nvm_tlv_3.2.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-qca-tn.bb: Unable to get checksum for linux-firmware-qca-tn SRC_URI entry rampatch_tlv_3.2.tlv: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry fw_bcm4339a0_ag.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry fw_bcm4339a0_ag_apsta.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry nvram_ap6335.txt: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry bcm4339a0.hcd: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry fw_bcm43438a0.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry fw_bcm43438a0_apsta.bin: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry nvram_ap6212.txt: file could not be found
WARNING: /home/user/edm_yocto/sources/meta-edm-bsp-release/recipes-kernel/linux-firmware/linux-firmware-brcm-tn.bb: Unable to get checksum for linux-firmware-brcm-tn SRC_URI entry bcm43438a0.hcd: file could not be found
Parsing recipes: 100% |##########################################| Time: 0:04:05
Parsing of 2433 .bb files complete (0 cached, 2433 parsed). 3274 targets, 212 skipped, 10 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Multiple providers are available for virtual/imxvpu (imx-vpu, imx-vpu-hantro)
Consider defining a PREFERRED_PROVIDER entry to match virtual/imxvpu

Build Configuration:
BB_VERSION           = "1.36.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-16.04"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "edm-imx6"
DISTRO               = "fsl-imx-x11"
DISTRO_VERSION       = "4.9.88-2.0.0"
TUNE_FEATURES        = "arm armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU           = "hard"
meta                 
meta-poky            = "HEAD:0ec241873367e18f5371a3ad9aca1e2801dcd4ee"
meta-oe              
meta-multimedia      = "HEAD:dacfa2b1920e285531bec55cd2f08743390aaf57"
meta-freescale       = "HEAD:49ac225a38f6d84519798e3264f2e4d19b84f70a"
meta-freescale-3rdparty = "HEAD:1d6d5961dbf82624b28bb318b4950a64abc31d12"
meta-freescale-distro = "HEAD:0ec6d7e206705702b5b534611754de0787f92b72"
meta-edm-bsp-release = "HEAD:32c22dc4812d7cfb0af4d10165e38571d118e5bb"
meta-bsp             
meta-sdk             = "HEAD:d65692ecb3a4136fc1cc137152634e8633ddb3c6"
meta-browser         = "HEAD:d6f9aed41c73b75a97d71bff060b03a66ee087b1"
meta-gnome           
meta-networking      
meta-python          
meta-filesystems     = "HEAD:dacfa2b1920e285531bec55cd2f08743390aaf57"
meta-qt5             = "HEAD:32bb7d18a08d1c48873d7ab6332d4cc3815a4dff"

Initialising tasks: 100% |#######################################| Time: 0:00:36
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: opkg-utils-0.3.5-r0 do_fetch: Failed to fetch URL http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.3.5.tar.gz, attempting MIRRORS if available
ERROR: opkg-utils-0.3.5-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-InXXutkZNG"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/user/edm_yocto/sources/poky/scripts:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/opkg-utils/0.3.5-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/opkg-utils/0.3.5-r0/recipe-sysroot/usr/bin/crossscripts:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/opkg-utils/0.3.5-r0/recipe-sysroot-native/usr/sbin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/opkg-utils/0.3.5-r0/recipe-sysroot-native/usr/bin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/opkg-utils/0.3.5-r0/recipe-sysroot-native/sbin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/opkg-utils/0.3.5-r0/recipe-sysroot-native/bin:/home/user/edm_yocto/sources/poky/bitbake/bin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/hosttools"; export HOME="/home/user"; /usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/user/edm_yocto/downloads/ 'http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.3.5.tar.gz' --progress=dot -v failed with exit code 4, output:
--2020-02-09 19:31:07--  http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.3.5.tar.gz
Resolving git.yoctoproject.org (git.yoctoproject.org)... failed: Temporary failure in name resolution.
wget: unable to resolve host address ‘git.yoctoproject.org’

ERROR: opkg-utils-0.3.5-r0 do_fetch: Fetcher failure for URL: 'http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.3.5.tar.gz'. Unable to fetch URL from any source.
ERROR: opkg-utils-0.3.5-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /home/user/edm_yocto/build-x11-edm-imx6/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/opkg-utils/0.3.5-r0/temp/log.do_fetch.3652
ERROR: Task (/home/user/edm_yocto/sources/poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.3.5.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 258 tasks of which 0 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/user/edm_yocto/sources/poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.3.5.bb:do_fetch
Summary: There were 25 WARNING messages shown.
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

My console log looks like this:

1279  PATH=${PATH}:~/bin
 1280  mkdir edm_yocto
 1281  cd edm_yocto
 1282  sudo repo init -u https://github.com/TechNexion/edm-yocto-bsp.git -b rocko_4.9.y_GA -m imx-4.9.88-2.0.0_ga.xml
 1283  printenv
 1284  chmod a+x ~/bin/repo
 1285  PATH=${PATH}:~/bin
 1286  cd edm_yocto
 1287  repo init -u https://github.com/TechNexion/edm-yocto-bsp.git -b rocko_4.9.y_GA -m imx-4.9.88-2.0.0_ga.xml
 1288  repo sync -j8
 1289  DISPLAY=lvds7 DISTRO=fsl-imx-x11 MACHINE=edm-imx6 BASEBOARD=fairy source edm-setup-release.sh -b build-x11-edm-imx6
 1290  bitbake fsl-image-qt5-validation-imx
 1291  uname -a
 1292  history

Is there any mistake made by me? It surely has to be something that I do or I do not since you are able to build Yocto without trouble.

Best regards, Jakub

@jdabros

ERROR: opkg-utils-0.3.5-r0 do_fetch: Fetcher failure for URL: 'http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.3.5.tar.gz'. Unable to fetch URL from any source. ERROR: opkg-utils-0.3.5-r0 do_fetch: Function failed: base_do_fetch

This error results from Yocto is unable to fetch opkg-utils-0.3.5.tar.gz. It seems the source package server is down temporarily.

I just try to download it. It works well. Could you try to use wget to download opkg-utils-0.3.5.tar.gz manually from http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/snapshot/opkg-utils-0.3.5.tar.gz

Yocto refers to many opensource projects and downloads the source packages individually.
Some source server sometimes are unavailable temporarily. You can try it later or download the source tarball somewhere else manually. Then, put the source tarball in downloads directory,

BR,

Richard

To be honest, each time I am trying to use bitbake to build Yocto there is some fetching problem. This time I've had:

ERROR: libdnf-native-0.9.3-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-EFMoMJzksZ"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/user/edm_yocto/sources/poky/scripts/native-intercept:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libdnf-native/0.9.3-r0/recipe-sysroot-native/usr/bin/python3-native:/home/user/edm_yocto/sources/poky/scripts:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libdnf-native/0.9.3-r0/recipe-sysroot-native/usr/bin/x86_64-linux:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libdnf-native/0.9.3-r0/recipe-sysroot-native/usr/bin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libdnf-native/0.9.3-r0/recipe-sysroot-native/usr/sbin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libdnf-native/0.9.3-r0/recipe-sysroot-native/usr/bin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libdnf-native/0.9.3-r0/recipe-sysroot-native/sbin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libdnf-native/0.9.3-r0/recipe-sysroot-native/bin:/home/user/edm_yocto/sources/poky/bitbake/bin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/hosttools"; export HOME="/home/user"; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/rpm-software-management/libdnf /home/user/edm_yocto/downloads//git2/github.com.rpm-software-management.libdnf --progress failed with exit code 128, output:
Cloning into bare repository '/home/user/edm_yocto/downloads//git2/github.com.rpm-software-management.libdnf'...
fatal: unable to connect to github.com:
github.com: Temporary failure in name resolution

ERROR: libdnf-native-0.9.3-r0 do_fetch: Fetcher failure for URL: 'git://github.com/rpm-software-management/libdnf'. Unable to fetch URL from any source.
ERROR: libdnf-native-0.9.3-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libdnf-native/0.9.3-r0/temp/log.do_fetch.1365
NOTE: recipe libdnf-native-0.9.3-r0: task do_fetch: Failed
ERROR: Task (virtual:native:/home/user/edm_yocto/sources/poky/meta/recipes-devtools/libdnf/libdnf_0.9.3.bb:do_fetch) failed with exit code '1'
NOTE: Running task 4870 of 8346 (/home/user/edm_yocto/sources/poky/meta/recipes-extended/less/less_487.bb:do_populate_sysroot)
NOTE: recipe less-487-r0: task do_populate_sysroot: Started
NOTE: recipe less-487-r0: task do_populate_sysroot: Succeeded
ERROR: libcomps-native-0.1.8+gitAUTOINC+01a4759894-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-EFMoMJzksZ"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/user/edm_yocto/sources/poky/scripts/native-intercept:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libcomps-native/0.1.8+gitAUTOINC+01a4759894-r0/recipe-sysroot-native/usr/bin/python3-native:/home/user/edm_yocto/sources/poky/scripts:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libcomps-native/0.1.8+gitAUTOINC+01a4759894-r0/recipe-sysroot-native/usr/bin/x86_64-linux:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libcomps-native/0.1.8+gitAUTOINC+01a4759894-r0/recipe-sysroot-native/usr/bin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libcomps-native/0.1.8+gitAUTOINC+01a4759894-r0/recipe-sysroot-native/usr/sbin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libcomps-native/0.1.8+gitAUTOINC+01a4759894-r0/recipe-sysroot-native/usr/bin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libcomps-native/0.1.8+gitAUTOINC+01a4759894-r0/recipe-sysroot-native/sbin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libcomps-native/0.1.8+gitAUTOINC+01a4759894-r0/recipe-sysroot-native/bin:/home/user/edm_yocto/sources/poky/bitbake/bin:/home/user/edm_yocto/build-x11-edm-imx6/tmp/hosttools"; export HOME="/home/user"; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/rpm-software-management/libcomps.git /home/user/edm_yocto/downloads//git2/github.com.rpm-software-management.libcomps.git --progress failed with exit code 128, output:
Cloning into bare repository '/home/user/edm_yocto/downloads//git2/github.com.rpm-software-management.libcomps.git'...
fatal: unable to connect to github.com:
github.com: Temporary failure in name resolution

ERROR: libcomps-native-0.1.8+gitAUTOINC+01a4759894-r0 do_fetch: Fetcher failure for URL: 'git://github.com/rpm-software-management/libcomps.git'. Unable to fetch URL from any source.
ERROR: libcomps-native-0.1.8+gitAUTOINC+01a4759894-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /home/user/edm_yocto/build-x11-edm-imx6/tmp/work/x86_64-linux/libcomps-native/0.1.8+gitAUTOINC+01a4759894-r0/temp/log.do_fetch.1282
NOTE: recipe libcomps-native-0.1.8+gitAUTOINC+01a4759894-r0: task do_fetch: Failed
ERROR: Task (virtual:native:/home/user/edm_yocto/sources/poky/meta/recipes-devtools/libcomps/libcomps_git.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4870 tasks of which 0 didn't need to be rerun and 2 failed.

Do I really need to have so much luck to build yocto? Or do I really have to download one tarball after another? Every time I make a clean build it takes a couple of hours, so this seems like it may take a while. :smile: May it be that there's something wrong with my virtual machine setup?

@jdabros

Do I really need to have so much luck to build yocto? Or do I really have to download one tarball after another?

It sounds unusual. If you are unable to download those tarballs manually in the virtual machine, it explains there is something wrong about network. I am thinking that if it's possible to tarball the whole download directory for you... It might takes tons of gigabytes for this tarball.

Every time I make a clean build it takes a couple of hours, so this seems like it may take a while.

Once the packages are downloaded, they are put in the download directory. So it would not need to fetch those packages again in the next build even after you execute bitbake fsl-image-qt5-validation-imx -c cleanall.

May it be that there's something wrong with my virtual machine setup?

The error you have is fetch error instead of compilation error. So i don't think your VM environment has library dependency problem. If there is problem in VM, it looks more like network problem.(I'm not sure)

BR,

Richard

@jdabros

I create a temporary download link below to send the tarball of download directory: https://takeafile.com/?f=beyocefona (I will close the download link after 24 hours.)

The file size is about 20G bytes. I am not sure if it's a good way to solve your fetching problem. It's the easiest way i can think. :)

BR,

Richard

@jdabros

The download speed in the previous link is awful. Could you try another one? https://file.direct/f/fFG28LMTtiJhgEpY

Richard

@jdabros

The download speed in the previous link is awful. Could you try another one? https://file.direct/f/fFG28LMTtiJhgEpY

Richard

Thank you very much, I will try this.

@jdabros :

Do you get better speed?

Yes I did get a better download speed. Unfortunately I left downloading for the night and when I came back it was interrupted.

I think that I will just have to work throguh this fetching problem on my own. Thank you for your very kind and helpful cooperation. I will keep you up posted when I reach the next step. Please do not close this thread until then.

@jdabros

Sorry to bother you :)

Does everything go smoothly so far? If you still need help, please feel free to leave your comment :)

Hi,

I've finally managed to build Yocto from TechNexion, but unfortunately it didn't solve any of my problems. After more than a year of complaint we tried to process with TechNexion and trying to work through our issues with hardware on EDM1 Fairy we decided to change platform to another vendor.

Regardless of that, many thanks for your effort and guiding me through the process.

@jdabros

Anyway, thanks for your feedback, although i don't really understand what kind of HW issue you encounter on EDM1 Fairy... We apologize for any inconvenience caused... It's still welcome if you need any kind of support about software on TechNexion products .

BR,

Richard

TechNexion / tn-imx-yocto-manifest

IMX6Q and EDM-Fairy support #1