Swi-fx30-catm_3.0.0 build error in swi-linux

Is it possible you have additional environment variables set? I was able to successfully build on a fresh ubuntu 18.04 vm without any issues. For that reason I don’t think this is a leaf issue

lpacyk@lukasz-ubuntu:~/leaf.ws/fx30_ravish/swi-linux-src$ make MACH=mdm9x28 PROD=fx30
"meta-columbia-x/meta-columbia-x-catm/build.sh" -p poky/ -o meta-openembedded/ -l meta-swi -x "kernel" -j 9 -t 9  -g -a "LEGATO_WORKDIR=/home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/legato/"    -a "IMA_SUPPORT_TOOLS_DIR=/home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/legato/3rdParty/" -a "IMA_SUPPORT_TOOLS_REPO=file://ima-support-tools" -a "IMA_SUPPORT_TOOLS_NAME=ima-support-tools"     -a LK_REPO_DIR="/home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src" -a LK_REPO_NAME="lk" -a LK_REPO="file://lk" -m swi-mdm9x28 -P fx30  -N -b build_bin -q -U
Poky dir: /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/poky
OE meta: /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-openembedded
SWI meta dir: /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi
Linux repo dir: /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/kernel
Number of make threads 9
Number of bitbake tasks 9
With Legato
Extra options added -  LEGATO_WORKDIR=/home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/legato/
Extra options added -  IMA_SUPPORT_TOOLS_DIR=/home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/legato/3rdParty/
Extra options added -  IMA_SUPPORT_TOOLS_REPO=file://ima-support-tools
Extra options added -  IMA_SUPPORT_TOOLS_NAME=ima-support-tools
Extra options added -  LK_REPO_DIR=/home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src
Extra options added -  LK_REPO_NAME=lk
Extra options added -  LK_REPO=file://lk
SWI machine: swi-mdm9x28
SWI product: fx30
SWI product family: fx
Build CATM
Build dir: /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/build_bin
Enable Qualcomm Proprietary bin
Build columbia-x public release image
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to, for
example, select a different MACHINE (target hardware). See conf/local.conf
for more information as common configuration options are commented.

You had no conf/bblayers.conf file. This configuration file has therefore been
created for you with some default values. To add additional metadata layers
into your configuration please add entries to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
    http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
    http://www.openembedded.org/


### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-sato
    meta-toolchain
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'
+ layer: meta-oe
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-openembedded/meta-oe
+ layer: meta-networking
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-openembedded/meta-networking
+ layer: meta-python
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-openembedded/meta-python
+ layer: meta-gplv2
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-gplv2
+ layer: meta-swi/common
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi/common
+ layer: meta-swi/meta-swi-mdm9xxx
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi/meta-swi-mdm9xxx
+ layer: meta-swi/meta-swi-mdm9x28
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi/meta-swi-mdm9x28
+ layer: meta-swi/meta-swi-mdm9x28-fx30
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi/meta-swi-mdm9x28-fx30
+ layer: meta-swi-extras/common
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi-extras/common
+ layer: meta-swi-extras/meta-swi-mdm9x28
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi-extras/meta-swi-mdm9x28
+ layer: meta-swi-extras/meta-swi-mdm9xxx-bin
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi-extras/meta-swi-mdm9xxx-bin
+ layer: meta-swi-extras/meta-swi-mdm9x28-bin
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi-extras/meta-swi-mdm9x28-bin
+ layer: meta-swi-extras/meta-swi-mdm9x28-fx30-bin
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi-extras/meta-swi-mdm9x28-fx30-bin
+ layer: meta-swi-extras/meta-swi-mdm9x28-fx30
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi-extras/meta-swi-mdm9x28-fx30
+ layer: meta-columbia-x/rootfs
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-columbia-x/rootfs
+ layer: meta-columbia-x/meta-columbia-x-bsp
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-columbia-x/meta-columbia-x-bsp
+ layer: meta-columbia-x/meta-columbia-x-public
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-columbia-x/meta-columbia-x-public
+ layer: meta-columbia-x/meta-columbia-x-app
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-columbia-x/meta-columbia-x-app
+ layer: meta-columbia-x-catm
         -> /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-columbia-x/meta-columbia-x-catm
Yocto machine: swi-mdm9x28-fx30
Adding option LEGATO_BUILD with value true
Adding option IMA_BUILD with value false
Adding option IMA_CONFIG with value 
Adding option IMA_LOCAL_CA_X509 with value 
Adding option IMA_PRIV_KEY with value 
Adding option IMA_PUB_CERT with value 
Adding option IMA_KERNEL_CMDLINE_OPTIONS with value 
Adding option ENABLE_IMA with value 0
Adding option IMA_PUBLIC_CERT with value 
Adding option IMA_PRIVATE_KEY with value 
Adding option IMA_SMACK with value 
Adding option ENABLE_FX30 with value true
Adding option ROOTFS_VERSION with value 
Adding option LEGATO_ROOTFS_TARGETS with value wp77xx
Adding option LEGATO_WORKDIR with value /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/legato/
Adding option IMA_SUPPORT_TOOLS_DIR with value /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/legato/3rdParty/
Adding option IMA_SUPPORT_TOOLS_REPO with value file://ima-support-tools
Adding option IMA_SUPPORT_TOOLS_NAME with value ima-support-tools
Adding option LK_REPO_DIR with value /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src
Adding option LK_REPO_NAME with value lk
Adding option LK_REPO with value file://lk
Adding option EXT_SWI_IMG with value false
Adding option INITRAMFS_IMAGE_BUNDLE with value 1
Adding option INITRAMFS_IMAGE with value mdm9x28-image-initramfs
Adding option FIRMWARE_PATH with value 
Adding option PACKAGECONFIG_remove with value gnutls
meta-columbia-x/meta-columbia-x-catm/build.sh: line 856: [: =: unary operator expected
Build image of minimal rootfs (for swi-mdm9x28).
WARNING: /home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi-extras/meta-swi-mdm9x28-bin/recipes/swimtd/swimtd_git.bb: Unable to get checksum for swimtd SRC_URI entry swimtd-bin.tar.bz2: file could not be found                                | ETA:  --:--:--
Parsing recipes: 100% |################################################################################################################################################################################################################################| Time: 0:00:23
Parsing of 2168 .bb files complete (0 cached, 2168 parsed). 3087 targets, 339 skipped, 0 masked, 0 errors.
WARNING: No bb files matched BBFILE_PATTERN_swi-mdm9x28-fx30-bin '^/home/lpacyk/leaf.ws/fx30_ravish/swi-linux-src/meta-swi-extras/meta-swi-mdm9x28-fx30-bin/'
NOTE: Resolving any missing task queue dependencies
NOTE: Multiple providers are available for runtime gps-utils (gps-utils, gpsd)
Consider defining a PREFERRED_RPROVIDER entry to match gps-utils

Build Configuration:
BB_VERSION           = "1.38.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-18.04"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "swi-mdm9x28-fx30"
DISTRO               = "poky-swi-ext"
DISTRO_VERSION       = "2.5.3"
TUNE_FEATURES        = "arm armv7a vfp neon"
TARGET_FPU           = "softfp"
meta                 
meta-poky            
meta-yocto-bsp       = "HEAD:cbb677e9a09d5dad34404a851f7c23aeb5122465"
meta-oe              
meta-networking      
meta-python          = "HEAD:8760facba1bceb299b3613b8955621ddaa3d4c3f"
meta-gplv2           = "HEAD:813b7d2b5573d8591c6cd8087b326f0a0703d6b9"
common               
meta-swi-mdm9xxx     
meta-swi-mdm9x28     
meta-swi-mdm9x28-fx30 = "HEAD:57e4574ed6b243881feee702a172ddaf321bb0fe"
common               
meta-swi-mdm9x28     
meta-swi-mdm9xxx-bin 
meta-swi-mdm9x28-bin = "HEAD:c0aad6c6bc29e4953e26a418824c4d55c3a73b74"
rootfs               
meta-columbia-x-bsp  
meta-columbia-x-app  
meta-columbia-x-catm 
meta-columbia-x-public = "<unknown>:<unknown>"
meta-swi-mdm9x28-fx30-bin 
meta-swi-mdm9x28-fx30 = "HEAD:c0aad6c6bc29e4953e26a418824c4d55c3a73b74"

NOTE: Fetching uninative binary shim from http://downloads.yoctoproject.org/releases/uninative/2.4/x86_64-nativesdk-libc.tar.bz2;sha256sum=06f91685b782f2ccfedf3070b3ba0fe4a5ba2f0766dad5c9d1642dccf95accd0
Initialising tasks: 100% |#############################################################################################################################################################################################################################| Time: 0:01:07
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: linux-libc-headers-3.18.140-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-if_ether-move-muslc-ethhdr-protection-to-uapi-file.patch
patching file include/uapi/linux/if_ether.h
Hunk #1 succeeded at 141 with fuzz 2 (offset 4 lines).

Now at patch 0001-if_ether-move-muslc-ethhdr-protection-to-uapi-file.patch
WARNING: linux-libc-headers-3.18.140-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0004-Avoid-in6_addr-redefinition.patch
patching file include/uapi/linux/if_bridge.h
Hunk #1 succeeded at 15 with fuzz 2.
patching file include/linux/netfilter.h
Hunk #1 succeeded at 5 (offset 1 line).

Now at patch 0004-Avoid-in6_addr-redefinition.patch
WARNING: system-core-1.0-r1 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch fix-big-endian-build.patch
patching file adb/usb_linux_client.c
Hunk #1 succeeded at 35 with fuzz 2 (offset 1 line).

Now at patch fix-big-endian-build.patch
WARNING: alsa-intf-1.0-r1 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0006-Wait-for-Audio-stream-to-end.patch
patching file libalsa-intf/aplay.c
Hunk #1 succeeded at 604 with fuzz 2 (offset 60 lines).

Now at patch 0006-Wait-for-Audio-stream-to-end.patch
WARNING: bridge-utils-1.6-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch kernel-headers_fix_in6_duplication.patch
patching file libbridge/libbridge.h
Hunk #1 succeeded at 24 with fuzz 1.

Now at patch kernel-headers_fix_in6_duplication.patch
WARNING: bluez5-5.50-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch
patching file Makefile.obexd
Hunk #1 succeeded at 1 with fuzz 2 (offset -1 lines).
patching file obexd/src/org.bluez.obex.service
patching file obexd/src/org.bluez.obex.service.in

Now at patch 0001-Allow-using-obexd-without-systemd-in-the-user-sessio.patch
WARNING: bluez5-5.50-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-Adding-MDM-specific-code-under-_PLATFORM_MDM_.patch
patching file tools/hciattach_rome.c
Hunk #1 succeeded at 1743 with fuzz 2 (offset 1 line).
Hunk #2 succeeded at 1876 (offset -1 lines).

Now at patch 0001-Adding-MDM-specific-code-under-_PLATFORM_MDM_.patch
WARNING: wpa-supplicant-2.6-r0 do_patch: 
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:

    devtool modify <recipe>
    devtool finish --force-patch-refresh <recipe> <layer_path>

Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch 0001-wpa-supplicant-2.6.patch
patching file src/ap/ap_drv_ops.c
Hunk #1 succeeded at 492 (offset -77 lines).
patching file src/ap/dfs.c
Hunk #1 succeeded at 659 with fuzz 2 (offset 52 lines).
patching file src/drivers/driver_wext.c
Hunk #1 succeeded at 1656 (offset 94 lines).
Hunk #2 succeeded at 2277 (offset 109 lines).
patching file wpa_supplicant/ap.c
Hunk #1 succeeded at 670 with fuzz 2 (offset 115 lines).

Now at patch 0001-wpa-supplicant-2.6.patch
WARNING: wl18xx-firmware-r8.a9.14-r4+gitrAUTOINC+2568d8f61f do_populate_lic: wl18xx-firmware: No generic license file exists for: TI-TSPA in any provider
WARNING: qca9377-bt-firmware-1.1-r0 do_populate_lic: qca9377-bt-firmware: No generic license file exists for: QCA-TSPA in any provider
WARNING: ima-policy-1.0-r1 do_install: IMA: Immutable files will not be protected.
WARNING: mdm9x28-image-minimal-1.0-r0.0 do_rootfs: The license listed QCA-TSPA was not in the licenses collected for recipe qca9377-bt-firmware
WARNING: mdm9x28-image-minimal-1.0-r0.0 do_rootfs: The license listed TI-TSPA was not in the licenses collected for recipe wl18xx-firmware
NOTE: Tasks Summary: Attempted 4204 tasks of which 7 didn't need to be rerun and all succeeded.

Summary: There were 15 WARNING messages shown.

strange that the first build is OK, but after that if I modify something in kernel driver, then I type “make MACH=mdm9x28 PROD=fx30”, I will hit the QA issue error

@lpacyk were you able to have a look at building after adding the Talon layer.
I am also observing the same error like @jyijyi mentioned , the first build is OK but once we modify something like in my case added the talon layer the mentioned error persists and the only option to rebuild was to delete the build folder(make clean) and issue the make(w/c options)

any updates, after the recent memory driver update … updating to R14 is a urgent requirement

@ravishkrishnan.kunch Can you please provide some details about the “Talon Module Layer”? Have you checked whether the Talon layer is compatible with yocto 2.5 on which FX30 CATM R14 is based?

I am not sure How i would check if the custom layer is compatible with yocto 2.5

For Adding the Talon layer i followed the stepps provided by @cchenry in FX30 (wp7702) and Talon IoT card - #2 by cchenry

But keeping aside adding the talon layer , even a simple Yocto customization on R14 is resulting in this error.
i tried adding a recipe to the make file by
Adding the Following lines after the << # Add > in the file << mdm9x28-image.inc >>

Add cronie package

IMAGE_INSTALL +=" cronie"

sorry instead of
IMAGE_INSTALL += " cronie"
I used
IMAGE_INSTALL_append = " cronie"

Has using IMAGE_INSTALL += " cronie" addressed the issue for you?

How about “make clean” first?
And then add cronie

And then “make MACH=mdm9x28 PROD=fx30”

Here I can build it:

Thanks @jyijyi
Adding cronie after “make clean”, i was able to build.

Another Yocto customization which we require is adding the custom Yocto layer like the above mention talon layer mention in FX30 (wp7702) and Talon IoT card - #2 by cchenry by @cchenry

Can you help us figure-out why adding this layer is resulting in “QA Issue: sierra-lowtempfix” error.

I don’t know, but if you do a make clean first, you should not see such issue

is there any other way other than “make clean”
when ever i am making changes - ex : adding a new recipe.
i am getting this error “sierra-lowtempfix” , and I have to make clean to again build it.
this is taking a lot of time to REBUILD

currently there is no solution.
Workaround is that you first use swi-fx30-catm-2.0.0 to do your development, after that port all your modification to swi-fx30-catm-3.0.0 and build after “make clean”

But “make clean” will delete the bblayer.conf file.
which is required to add a new custom layer.
How can be add a custom layer without editing the bblayer.conf

How about adding your recipe in current existing layer?

Hi @ravishkrishnan.kunch

A couple things you can try to improve your build time:

  1. Try the bitbake command directly:
    Type:
    make dev
    bitbake -c build

  2. Implement yocto share state cache. Basically, once you build the image, move the cache to another location, and then point to it. The next time you build with sstate cache, only the packages that are required will be built.

BR,
Chris

Thanks @cchenry
How to point to the copied state cache? is this some configuration.

i was able to build
But now i am unable to flash the cwe file using swiflash
**swiflash -m “wp77xx” -i boot-yocto-legato_wp77xx.cwe **
Detecting USB of the target
DONE
Communicating with the target
DONE
Switching to firmware download mode
…DONE
Downloading the firmware
…ERROR: Firmware Download failed. Callback status 59399DONE
ERROR: Firmware Download Failed

You can transfer the cwe file to module and use fwupdate command in target module to update

[quote=“jyijyi, post:26, topic:25090, full:true”]
You can transfer the cwe file to module and use fwupdate command in target module to update
[/quote
fwupdate also not working
root@fx30s:~# fwupdate download boot-yocto-legato_wp77xx.cwe
Connecting to service …
Can’t open file ‘boot-yocto-legato_wp77xx.cwe’ : No such file or directory
root@fx30s:~# ls
boot-yocto-legato_wp77xx.cwe

swiflash -m "wp77xx" -r is also working after flashing Sierra Wireless FX30 Firmware CatM
https://downloads.sierrawireless.com/airlink/FX30/CatM/FX30_WP77xx_full_R14.1.1.002-sierra-SWI9X06Y_02.36.06.00.cwe
Will the swiflash tool not work with R14.1.1 based Firmware ?
we have been using the swiflash in our production for R9.1.1 based firmware.