linaro/meta-qcom

OpenEmbedded/Yocto Project BSP layer for Qualcomm based platforms

meta-qcom

Introduction

OpenEmbedded/Yocto Project layer for Qualcomm based platforms.

This layer depends on:

URI: https://github.com/openembedded/openembedded-core.git
layers: meta
branch: master
revision: HEAD

This layers has an optional dependency on meta-oe layer:

URI: https://github.com/openembedded/meta-openembedded.git
layers: meta-oe
branch: master
revision: HEAD

The dependency is optional, and not strictly required. When meta-oe is enabled in the build (e.g. it is used in BBLAYERS) then additional recipes from meta-qcom are added to the metadata. You can refer to meta-qcom/conf/layer.conf for the implementation details.

Device support

All contemporary boards are supported by a single qcom-armv8a machine. Please use it instead of using the per-board configuration file. In order to enable support for the particular device extend the qcom-armv8a.conf file .

Quick build

If you're new to the Yocto Project, you might want to read the document in order to setup your Yocto Project build environment.

From inside poky folder, clone this repository:

git clone git://git.yoctoproject.org/meta-qcom

Now, from inside poky folder initialize your build folder:

source oe-init-build-env build/qcom-armv8a

The script will cd into the newly created build/qcom-armv8a folder. From within this folder, add meta-qcom layer:

bitbake-layers add-layer ../../meta-qcom

Change MACHINE variable into conf/local.conf to:

MACHINE ?= "qcom-armv8a"

Finally, build your image:

bitbake core-image-minimal

Contributing

If you want to contribute changes, you can send Github pull requests at https://github.com/Linaro/meta-qcom/pulls.

You can discuss about this layer, on #linaro on Libera Chat IRC network.

Reporting issues

Please report any issue on https://github.com/Linaro/meta-qcom/issues

Maintainer(s)

Dmitry Baryshkov [email protected]

meta-qcom's Issues

Weston client failure when starting app over ssh

Issue: Starting any weston client app over ssh causes a failure (no display found).

Note: It seems that the "wayland-0" socket file is not created at startup in the /var/run/user/0/ folder. Needs to be verified, but this may be an issue on all meta-96boards builds.

Workaround:

$ systemctl restart weston

wifi/bt/gps modules not listed in MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS

I'm assuming they are enabled in the kernel build. The EULA has been accepted:

root@dragonboard-410c:~# opkg list_installed | grep dragon
firmware-qcom-dragonboard410c - 1.1.0-r0.0

And:

root@dragonboard-410c:~# opkg list_installed | grep kernel
kernel - 4.2-r0.1
kernel-4.2.0+yocto - 4.2-r0.1
kernel-image-4.2.0+yocto - 4.2-r0.1
kernel-module-configfs - 4.2-r0.1
kernel-module-g-ether - 4.2-r0.1
kernel-module-g-mass-storage - 4.2-r0.1
kernel-module-g-serial - 4.2-r0.1
kernel-module-libcomposite - 4.2-r0.1
kernel-module-u-ether - 4.2-r0.1
kernel-module-usb-f-mass-storage - 4.2-r0.1
kernel-module-usb-f-rndis - 4.2-r0.1
root@dragonboard-410c:~# 

Network issues

I'm not sure what's at fault here, but wifi won't get a proper ipv6 address:

3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP8000> mtu 1500 qdisc mq qlen 1000
    link/ether 00:0a:f5:a5:a4:d7 brd ff:ff:ff:ff:ff:ff
    inet 172.20.0.116/24 brd 172.20.0.255 scope global wlan0
       valid_lft forever preferred_lft forever
    inet6 fe80::20a:f5ff:fea5:a4d7/64 scope link 
       valid_lft forever preferred_lft forever

And avahi can't see anything on the network:

root@dragonboard-410c:~# avahi-browse -at
+  wlan0 IPv4 dragonboard-410c                              _ssh._tcp            local
+  wlan0 IPv4 dragonboard-410c [00:0a:f5:a5:a4:d7]          _workstation._tcp    local
+  wlan0 IPv4 dragonboard-410c   
root@dragonboard-410c:~#

Around the same time errors like these pop up:

[ 5775.279347] wcn36xx: ERROR SMD_EVENT (259) not supported

This is with the latest meta-qcom, kernel "Linux dragonboard-410c 4.2.0+linaro #1 SMP PREEMPT Sat Oct 17 14:48:34 CEST 2015 aarch64 GNU/Linux"

Enable CONFIG_NETFILTER_XT_MATCH_HASHLIMIT in kernel defconfig

While compiling wireguard-module on dragon board 410c it fails to build due to the above option being unset

| /mnt/oe/openembedded-core/build/tmp-glibc/work/dragonboard_410c-oe-linux/wireguard-module/0.0.20170324-r0/WireGuard-0.0.20170324/src/Kbuild:30: *** "WireGuard requires CONFIG_NETFILTER_XT_MATCH_HASHLIMIT to be configured in your kernel. See https://www.wireguard.io/install/#kernel-requirements for more info". Stop.

Only one CPU with krogoth branch, massive tracebacks in dmesg

I built and flashed an angstrom build yesterday and I get only one cpu:

root@dragonboard-410c:~# cat /proc/cpuinfo 
processor   : 0
BogoMIPS    : 38.40
Features    : fp asimd evtstrm crc32
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part    : 0xd03
CPU revision    : 0

root@dragonboard-410c:~# 

and

root@dragonboard-410c:~# uname -a
Linux dragonboard-410c 4.4.23+linaro #1 SMP PREEMPT Sat Oct 15 09:52:50 CEST 2016 aarch64 aarch64 aarch64 GNU/Linux

Full dmesg: http://sprunge.us/UUXb

The krogoth branch at this commit:

commit cd38876d03bbe25e5baa623574088f67aea324e9
Author: Nicolas Dechesne <[email protected]>
Date:   Tue Oct 11 22:34:25 2016 +0100

    linux-linaro-qcomlt_4.4: update with Linaro 16.09 release

    * merged 4.4.23
    * switch to PSCI by default: so it requires the latest bootloader with PSCI
      enabled

    Signed-off-by: Nicolas Dechesne <[email protected]>

IMAGE_FSTYPES should not use _append but ?=

We should not _append to IMAGE_FSTYPES but use ?= to let the user choose the output format w/o us adding another item on-top (unconditionally).

The current setting of IMAGE_FSTYPES_append breaks initrd builds here.

Can I enable CSI/camera for 845c board?

I am building yocto for Qualcomm RB3 ( Dragonboard 845c ).
But its camera cannot work under this version.

I have seen 410c can enable it.

I wonder whether I can do similar for 845c?

I have enabled qcom-camss and ov8856 modules, but I think what I am missing is correct DTS?

Rocko branch bbappends wrong version

You bbappend gpsd-3.17 whereas http://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-navigation/gpsd?h=rocko&id=352531015014d1957d6444d114f4451e241c4d23 has 3.16 .

Error:
Parsing recipes: 100% |################################################################################################################################################################| Time: 0:00:57
Parsing of 2367 .bb files complete (0 cached, 2367 parsed). 3262 targets, 297 skipped, 0 masked, 0 errors.
ERROR: No recipes available for:
/build-master2/meta-qcom/openembedded-layer/recipes-navigation/gpsd/gpsd_3.17.bbappend

QCOM license not displayed for 32bit build

Steps to reproduce:

• Call source setup-environment and select dragonboard-410c-32.

OUTPUT
`kuscsik@zoli-xps:~/rpb$ source setup-environment

The BSP for dragonboard-410c depends on packages and firmware which are covered by an End
User License Agreement (EULA). To have the right to use these binaries
in your images, you need to read and accept the following...

Would you like to read the EULA ? (y/n) y
more: stat of ../layers/meta-qcom/conf/eula/dragonboard-410c
../layers/meta-qcom/conf/eula/dragonboard-410c-32 failed: No such file or directory

Do you accept the EULA you just read? (y/n) y
EULA has been accepted.

Welcome to OpenEmbedded Reference Platform Build (OE RPB)

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

Your build environemnt has been configured with:

MACHINE = dragonboard-410c
SDKMACHINE = x86_64
DISTRO = rpb-wayland

You can now run 'bitbake '

Some of common targets are:
rpb-console-image
rpb-desktop-image
rpb-weston-image
core-image-base
core-image-minimal

kuscsik@zoli-xps:~/rpb/build-rpb-wayland$ ls`

Linux-firmware can't be installed in 'rocko' due to comflicts with firmware-qcom-dragonboard410c

When using an image with 'linux-firmware' in it I get the following:

Collected errors:
 * check_data_file_clashes: Package linux-firmware wants to install file /build/jenkins/v2017.12/Domoticz/machine/dragonboard-410c/build/tmp-angstrom-glibc/work/dragonboard_410c-angstrom-linux/domoticz-image/1.0-r0/rootfs/lib/firmware/a300_pfp.fw
	But that file is already provided by package  * firmware-qcom-dragonboard410c
 * check_data_file_clashes: Package linux-firmware wants to install file /build/jenkins/v2017.12/Domoticz/machine/dragonboard-410c/build/tmp-angstrom-glibc/work/dragonboard_410c-angstrom-linux/domoticz-image/1.0-r0/rootfs/lib/firmware/qcom/venus-1.8/venus.b02
	But that file is already provided by package  * firmware-qcom-dragonboard410c
 * check_data_file_clashes: Package linux-firmware wants to install file /build/jenkins/v2017.12/Domoticz/machine/dragonboard-410c/build/tmp-angstrom-glibc/work/dragonboard_410c-angstrom-linux/domoticz-image/1.0-r0/rootfs/lib/firmware/qcom/venus-1.8/venus.b00
	But that file is already provided by package  * firmware-qcom-dragonboard410c
 * check_data_file_clashes: Package linux-firmware wants to install file /build/jenkins/v2017.12/Domoticz/machine/dragonboard-410c/build/tmp-angstrom-glibc/work/dragonboard_410c-angstrom-linux/domoticz-image/1.0-r0/rootfs/lib/firmware/qcom/venus-1.8/venus.b01
	But that file is already provided by package  * firmware-qcom-dragonboard410c
 * check_data_file_clashes: Package linux-firmware wants to install file /build/jenkins/v2017.12/Domoticz/machine/dragonboard-410c/build/tmp-angstrom-glibc/work/dragonboard_410c-angstrom-linux/domoticz-image/1.0-r0/rootfs/lib/firmware/qcom/venus-1.8/venus.b03
	But that file is already provided by package  * firmware-qcom-dragonboard410c
 * check_data_file_clashes: Package linux-firmware wants to install file /build/jenkins/v2017.12/Domoticz/machine/dragonboard-410c/build/tmp-angstrom-glibc/work/dragonboard_410c-angstrom-linux/domoticz-image/1.0-r0/rootfs/lib/firmware/qcom/venus-1.8/venus.mdt
	But that file is already provided by package  * firmware-qcom-dragonboard410c
 * check_data_file_clashes: Package linux-firmware wants to install file /build/jenkins/v2017.12/Domoticz/machine/dragonboard-410c/build/tmp-angstrom-glibc/work/dragonboard_410c-angstrom-linux/domoticz-image/1.0-r0/rootfs/lib/firmware/qcom/venus-1.8/venus.b04
	But that file is already provided by package  * firmware-qcom-dragonboard410c
 * check_data_file_clashes: Package linux-firmware wants to install file /build/jenkins/v2017.12/Domoticz/machine/dragonboard-410c/build/tmp-angstrom-glibc/work/dragonboard_410c-angstrom-linux/domoticz-image/1.0-r0/rootfs/lib/firmware/a300_pm4.fw
	But that file is already provided by package  * firmware-qcom-dragonboard410c
g.

Bluetooth issue with newer 4.9.56 linux kernel

Hi everyone,

I built a custom yocto image for dragonboard-410c using this meta-qcom layer. Everything built fine. But after I load the image, the bluetooth is not working. Hence, when I do $ hciconfig hci0 up, it gives me this error message: Operation not supported. Btw, the wifi is working.

So, I am wondering if this is a known issue or not. So for now, i just used the older version of the linux kernel 4.9.39. This version worked perfectly.

BG
Jay

Gstreamer player fail to play [yocto -snapdragaon 820]

i am trying play mp3 files , while failed and error log is:
$gst-play-1.0 test.mp3

Press 'k' to see a list of keyboard shortcuts.
Now playing /home/root/test.mp3
WARNING No decoder available for type 'application/x-id3'.
WARNING debug information: /home/le820nanosom/test_2/poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0-plugins-base/1.10.2-r0/gst-plugin0
ERROR Your GStreamer installation is missing a plug-in. for file:///home/root/test.mp3
ERROR debug information: /home/le820nanosom/test_2/poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0-plugins-base/1.10.2-r0/gst-plugins-:
no suitable plugins found:
/home/le820nanosom/test_2/poky/build/tmp-glibc/work/aarch64-oe-linux/gstreamer1.0-plugins-base/1.10.2-r0/gst-plugins-base-1.10.2/gst/playback/:
no suitable plugins found:
Missing decoder: ID3 tag (application/x-id3)

Reached end of play list.

how to fix this bug??

KERNEL_DEVICETREE fails with latest oe-core master

Commit 2e7f3b2b9318d1e5395ad58131eafb873f614326 in openembedded-core causes kernel to fail to build:

Build Configuration:
BB_VERSION           = "1.39.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "opensuseleap-15.0"
TARGET_SYS           = "aarch64-oe-linux"
MACHINE              = "dragonboard-410c"
DISTRO               = "nodistro"
DISTRO_VERSION       = "nodistro.0"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""
meta-qcom            = "master:dc97efd7064ca8316115e140d6f37f2faae2eaa0"
meta                 = "master:b11c3b3e9ae69e218d8f0271697a5a5d0b49949b"
meta-oe              
meta-gnome           
meta-python          
meta-networking      
meta-multimedia      = "master:b56fc26fefff498b10236ea6486a5d5624f726cc"
meta-browser         = "master:8e159ff95e0583c4a821d5e59c8bb1972820f10d"
meta-qt5             = "master:2b01a6d8b8e39030afe5e6a5876f873505bbc112"
meta-qt5-extra       = "master:1d5f83ab500ab4ae57ef17295130b42e163582b0"
meta-realtime        = "master:00b8a8938fdd045a0c09f9e3e4f6e392a995d5cf"

failure:

|   CC      scripts/mod/empty.o
|   CC      scripts/mod/devicetable-offsets.s
|   MKELF   scripts/mod/elfconfig.h
|   HOSTCC  scripts/mod/modpost.o
|   HOSTCC  scripts/mod/sumversion.o
|   GEN     scripts/mod/devicetable-offsets.h
|   HOSTCC  scripts/mod/file2alias.o
|   HOSTLD  scripts/mod/modpost
| make[3]: *** No rule to make target 'arch/arm64/boot/dts/dts/apq8016-sbc.dtb'.  Stop.
| make[2]: *** [arch/arm64/Makefile:114: dts/qcom/apq8016-sbc.dtb] Error 2
| make[1]: *** [Makefile:150: sub-make] Error 2
| make: *** [Makefile:24: __sub-make] Error 2
| ERROR: oe_runmake failed

bad commit:

commit 2e7f3b2b9318d1e5395ad58131eafb873f614326
Author: Paulo Neves <[email protected]>
Date:   Mon Jul 2 17:03:44 2018 +0200

    kernel-devicetree: Corrected normalize_dtb
    
    The normalize_dtb function was buggy because
    it only converted from .dts suffix to .dtb
    suffix if the user passed a full source path to
    KERNEL_DEVICETREE containing the /dts/ path.
    The problem is that if the user did that there
    would be a warning.
    
    On the othet hand if user just set the variable
    KERNEL_DEVICETREE="file.dts" the bbclass translation
    to the respective .dtb target did not occur and
    make would fail saying it has no rule to make target
    file.dts
    
    This patch decouples the logic of having /dts/ in the
    path from the target translation.
    
    Signed-off-by: Paulo Neves <[email protected]>
    Signed-off-by: Richard Purdie <[email protected]>

diff --git a/meta/classes/kernel-devicetree.bbclass b/meta/classes/kernel-devicetree.bbclass
index 4f80cc62eb..9866d844ab 100644
--- a/meta/classes/kernel-devicetree.bbclass
+++ b/meta/classes/kernel-devicetree.bbclass
@@ -13,8 +13,8 @@ normalize_dtb () {
        DTB="$1"
        if echo ${DTB} | grep -q '/dts/'; then
                bbwarn "${DTB} contains the full path to the the dts file, but only the dtb name should be used."
-               DTB=`basename ${DTB} | sed 's,\.dts$,.dtb,g'`
        fi
+       DTB=`basename ${DTB} | sed 's,\.dts$,.dtb,g'`
        echo "${DTB}"
 }

The KERNEL_DEVICETREE variable is correctly set to "qcom/apq8016-sbc.dtb" but it looks like the normalize function is stripping off the "qcom/" (??). In any case, reverting the oe-core commit solves the issue, and the issue only came up today (it had been fine in nightly builds over the past couple days).

No 4k output on Qualcomm Robotics RB3 Platform(SDA845) (Thundercomm)

Using the thundercomm board for the 845c. Built an image using the warrior branch 5.2 kernel. The HDMI output maxes out at 1920x1080p @ 60Hz. The hardware manual I believe says the HDMI can output 4k @ 30hz.

There is also an issue drawing to the display, when using gstreamer to draw multiple videos on the screen, the videos would decode but the screen has a hard time drawing the videos to the screen. I've tried both an X11 and Weston image but still see the weird screen drawing issue. Using the v4l2decoder with gstreamer with the xvimagesink on X11 and the waylandsink on Weston. The videos would flicker on the screen. I also launched a GTK application and that flickered briefly as well. It also crashes the device frequently whenever I run the gstreamer pipelines.

Kernel fault - v4l-compliance

Note: Probably this wont be relevant after moving to the new v4l2 implementation.

Issue: Kernel null pointer deference. System hangs.
Dmesg: https://paste.ubuntu.com/23322887/

Steps to reproduce:

1. Using OE build v4l-utils and deploy it on an RPB build.
2. On the target run:
   $ v4l2-compliance

Resolving builds.96boards.org (builds.96boards.org)... failed: Name or service not known.

WARNING: firmware-qcom-dragonboard820c-01700.1-r0 do_fetch: Failed to fetch URL http://builds.96boards.org/releases/dragonboard820c/qualcomm/firmware/linux-board-support-package-r01700.1.zip, attempting MIRRORS if available
ERROR: firmware-qcom-dragonboard820c-01700.1-r0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-ahD33yNvjU,guid=840d7b839b4278f676d0f88c5a9e6815"; export SSH_AGENT_PID="7555"; export SSH_AUTH_SOCK="/home/dl9pf/.byobu/.ssh-agent"; export PATH="/home/scratch/AGL/repobuild-local/build-820c/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/scratch/AGL/repobuild-local/build-820c/tmp/work/dragonboard_820c-agl-linux/firmware-qcom-dragonboard820c/01700.1-r0/recipe-sysroot-native/usr/bin/tar-native:/home/scratch/AGL/repobuild-local/poky/scripts:/home/scratch/AGL/repobuild-local/build-820c/tmp/work/dragonboard_820c-agl-linux/firmware-qcom-dragonboard820c/01700.1-r0/recipe-sysroot-native/usr/bin/aarch64-agl-linux:/home/scratch/AGL/repobuild-local/build-820c/tmp/work/dragonboard_820c-agl-linux/firmware-qcom-dragonboard820c/01700.1-r0/recipe-sysroot/usr/bin/crossscripts:/home/scratch/AGL/repobuild-local/build-820c/tmp/work/dragonboard_820c-agl-linux/firmware-qcom-dragonboard820c/01700.1-r0/recipe-sysroot-native/usr/sbin:/home/scratch/AGL/repobuild-local/build-820c/tmp/work/dragonboard_820c-agl-linux/firmware-qcom-dragonboard820c/01700.1-r0/recipe-sysroot-native/usr/bin:/home/scratch/AGL/repobuild-local/build-820c/tmp/work/dragonboard_820c-agl-linux/firmware-qcom-dragonboard820c/01700.1-r0/recipe-sysroot-native/sbin:/home/scratch/AGL/repobuild-local/build-820c/tmp/work/dragonboard_820c-agl-linux/firmware-qcom-dragonboard820c/01700.1-r0/recipe-sysroot-native/bin:/home/scratch/AGL/repobuild-local/poky/bitbake/bin:/home/scratch/AGL/repobuild-local/build-820c/tmp/hosttools"; export HOME="/home/dl9pf"; /usr/bin/env wget -t 2 -T 30 -nv --passive-ftp --no-check-certificate -P /home/dl9pf/.yocto/shared_downloads/ 'http://builds.96boards.org/releases/dragonboard820c/qualcomm/firmware/linux-board-support-package-r01700.1.zip' --progress=dot -v failed with exit code 4, output:
--2018-03-07 18:13:13-- http://builds.96boards.org/releases/dragonboard820c/qualcomm/firmware/linux-board-support-package-r01700.1.zip
Resolving builds.96boards.org (builds.96boards.org)... failed: Name or service not known.
wget: unable to resolve host address ‘builds.96boards.org’

ERROR: firmware-qcom-dragonboard820c-01700.1-r0 do_fetch: Fetcher failure for URL: 'http://builds.96boards.org/releases/dragonboard820c/qualcomm/firmware/linux-board-support-package-r01700.1.zip'. Unable to fetch URL from any source.
ERROR: firmware-qcom-dragonboard820c-01700.1-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /home/scratch/AGL/repobuild-local/build-820c/tmp/work/dragonboard_820c-agl-linux/firmware-qcom-dragonboard820c/01700.1-r0/temp/log.do_fetch.13797
ERROR: Task (/home/scratch/AGL/repobuild-local/meta-qcom/recipes-bsp/firmware/firmware-qcom-dragonboard820c_01700.1.bb:do_fetch) failed with exit code '1'

please forward port alsa-lib patches

I am seeing this warning

WARNING: No recipes available for:
 /mnt/b/yoe/sources/meta-qcom/recipes-multimedia/alsa/alsa-lib_1.1.%.bbappend

oe-core now has updated to alsa-lib-1.2

not able to get plug-in on 820[gstreamer]

i added gstreamer in .inc file. i am able to get api gst-player, gstreamer-launch, gstreamer-inspect.
But not getting supported plug in.
all yocto based stuff i am using.

how to use aDSP of snapdragaon820

i want play some mp3, mp4 etc file. i have alsa framework but it support only .raw, .wav file only. i am using yocto project . any framework or tool available ??

thud branch ath10k fix does not build properly with yocto

The ath10k fix from pull request #93 breaks my build with yocto. It seems like the arch specific pre install function messes up the noarch linux-firmware recipe. I get the follwing bitbake error:

No match for argument: linux-firmware-ath10k
Error: Unable to find a match

MSM8996 Support

Hi, I am trying to ran a meta-qcom build on a spare OnePlus-3 device. I took latest version of meta-qcom as well as a recent version of poky:master branch. From the generated artifacts I try to boot the device via:

$ fastboot boot boot-apq8096-db820c-qcom-armv8a.img
Sending 'boot.img' (8040 KB)                       OKAY [  0.280s]
Booting                                            FAILED (remote: 'dtb not found')
fastboot: error: Command failed

So you have any hint why a dtb might not be landed in the img file? The overall Yocto process though complained (warnings) about missing adreno and furth qcom firmware but succeeded without error.

Resize rootfs on first boot

Out of the box there is very little space (~25MiB) available, we should try to resize the partition on first boot.

The following worked for me:

 opkg install e2fsprogs-resize2fs ; resize2fs  /dev/disk/by-partlabel/rootfs

My proposal is to have a recipe called something like 'resize-rootfs.bb' that RDEPENDS on e2fsprogs-resize2fs and does 'resize2fs /dev/disk /by-partlabel/rootfs' as on-device postinst.

make-mod-scripts is not buildable with linux-linaro-qcomlt

If we enable any feature or package that requires out-of-tree kernel modules to be built then meta-qcom based builds fail because linux-linaro-qcomlt is not compatible with make-mod-scripts. In particular this makes is difficult to set the tools-profile image feature (because it tries to build lttng-modules).

So far I have tested only the dunfell packages. Is linux-linaro-qcomlt expected to support out-of-tree kernel modules?

Currently I have adopted the following trivial workaround but if this is something that should be fixed...

# Disable LTTng dependencies when building for qcom family parts. This is
# required because linux-linaro-qcomlt does not support out-of-tree
# module builds so we must avoid pulling in lttng-modules.
LTTNGUST:pn-packagegroup-core-tools-profile:qcom = ""
LTTNGTOOLS:pn-packagegroup-core-tools-profile:qcom = ""
LTTNGMODULES:pn-packagegroup-core-tools-profile:qcom = ""

Wish: Please support Qualcomm ARM Kryo 260 based SoC

Hi,
I am wondering if there are any interest to enable this SoC for this machine:

Relate-to: https://forums.quectel.com/t/sc66-yocto-support/11815/2
Relate-to: https://www.quectel.com/product/lte-sc66-e-332-smart-module/#

ALSA Compress-Offload support

I am trying to use the ALSA Compress-Offload support on a Dragonboard 410c. When I start the Android image on the eMMC, I see that Compress-Offload works - I see /dev/snd/compr* devices.

But when I build an image with your meta-qcom branch, I do not see such device nodes in /dev/snd/ . I do add firmware-qcom-dragonboard410c to the image. I also see that the various qdsp6 modules are on the image, but not auto-loaded. Compiling the qdsp6 modules into the kernel did not help.

Furthermore, I see a crash at boot time. Here's the log. I currently do not know if this is related to the issue I mentioned.

I am using Yocto Kirkstone. meta-qcom is at commit 83049ef84b3d1f13a1175aa169b2539a8c58156b.

Rocko: Build fails with

Hi,

I'm attempting to build core-image-minimal for dragonboard-410c.
The build fails with:

martyn@hades:~/Documents/yocto/build-dragonboard-rocko$ bitbake core-image-minimal
Parsing recipes: 100% |############################################################################################################################################| Time: 0:00:37
Parsing of 1980 .bb files complete (0 cached, 1980 parsed). 2774 targets, 113 skipped, 0 masked, 0 errors.
NOTE: There are 1 recipes to be removed from sysroot aarch64, removing...
NOTE: There are 1 recipes to be removed from sysroot dragonboard-410c, removing...
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.36.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal-4.9"
TARGET_SYS        = "aarch64-poky-linux"
MACHINE           = "dragonboard-410c"
DISTRO            = "poky"
DISTRO_VERSION    = "2.4"
TUNE_FEATURES     = "aarch64"
TARGET_FPU        = ""
meta              
meta-poky         
meta-yocto-bsp    = "rocko:f7b90ab3eaf832bd81f3efc1dab4dcf6863ac284"
meta-oe           
meta-python       
meta-multimedia   
meta-networking   = "rocko:6e3fc5b8d904d06e3aa77e9ec9968ab37a798188"
meta-qcom         = "master:0385b8d77360fcdcd9b416e5e9f0011268625d9f"

Initialising tasks: 100% |#########################################################################################################################################| Time: 0:00:03
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: core-image-minimal-1.0-r0 do_image_wic: Function failed: do_image_wic (log file is located at /home/martyn/Documents/yocto/build-dragonboard-rocko/tmp/work/dragonboard_410c-poky-linux/core-image-minimal/1.0-r0/temp/log.do_image_wic.31942)
ERROR: Logfile of failure stored in: /home/martyn/Documents/yocto/build-dragonboard-rocko/tmp/work/dragonboard_410c-poky-linux/core-image-minimal/1.0-r0/temp/log.do_image_wic.31942
Log data follows:
| DEBUG: Executing python function set_image_size
| DEBUG: Python function set_image_size finished
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/fdisk/gptfdisk_1.0.3.bb:do_populate_sysroot', '/home/martyn/Documents/yocto/poky/meta/recipes-core/glibc/ldconfig-native_2.12.1.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/makedevs/makedevs_1.0.1.bb:do_populate_sysroot', '/home/martyn/Documents/yocto/poky/meta/recipes-kernel/kmod/depmodwrapper-cross_1.0.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-extended/pigz/pigz_2.3.4.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-extended/parted/parted_3.2.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/prelink/prelink_git.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/createrepo-c/createrepo-c_git.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/mtools/mtools_4.0.18.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/opkg/opkg_0.3.5.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/rpm/rpm_git.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-core/update-rc.d/update-rc.d_0.7.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/dnf/dnf_2.6.3.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/pseudo/pseudo_1.8.2.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/dosfstools/dosfstools_4.1.bb:do_populate_sysroot', '/home/martyn/Documents/yocto/meta-qcom/recipes-bsp/firmware/firmware-qcom-dragonboard410c-bootloader-sdcard_17.09.bb:do_populate_sysroot', '/home/martyn/Documents/yocto/poky/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_populate_sysroot', 'virtual:native:/home/martyn/Documents/yocto/poky/meta/recipes-devtools/opkg-utils/opkg-utils_0.3.5.bb:do_populate_sysroot', '/home/martyn/Documents/yocto/poky/meta/recipes-devtools/mklibs/mklibs-native_0.1.43.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['gptfdisk-native', 'ldconfig-native', 'makedevs-native', 'depmodwrapper-cross', 'pigz-native', 'parted-native', 'prelink-native', 'createrepo-c-native', 'mtools-native', 'opkg-native', 'rpm-native', 'update-rc.d-native', 'dnf-native', 'pseudo-native', 'dosfstools-native', 'firmware-qcom-dragonboard410c-bootloader-sdcard', 'qemuwrapper-cross', 'opkg-utils-native', 'mklibs-native', 'popt-native', 'ncurses-native', 'util-linux-native', 'quilt-native', 'kmod-native', 'qemu-native', 'zlib-native', 'gnu-config-native', 'texinfo-dummy-native', 'autoconf-native', 'readline-native', 'libtool-native', 'gettext-minimal-native', 'automake-native', 'pkgconfig-native', 'xz-native', 'binutils-native', 'elfutils-native', 'expat-native', 'cmake-native', 'libxml2-native', 'file-native', 'sqlite3-native', 'openssl-native', 'curl-native', 'python3-native', 'glib-2.0-native', 'libarchive-native', 'libsolv-native', 'shadow-native', 'nss-native', 'bzip2-native', 'dbus-native', 'db-native', 'libdnf-native', 'librepo-native', 'libcomps-native', 'python3-iniparse-native', 'glibc', 'gcc-runtime', 'lzo-native', 'gtk-doc-native', 'pixman-native', 'libsdl-native', 'dtc-native', 'alsa-lib-native', 'm4-native', 'flex-native', 'bison-native', 'cryptodev-linux-native', 'makedepend-native', 'gettext-native', 'libpcre-native', 'libffi-native', 'e2fsprogs-native', 'nspr-native', 'gobject-introspection-native', 'libcheck-native', 'gpgme-native', 'attr-native', 'python3-six-native', 'linux-libc-headers', 'libgcc', 'util-macros-native', 'libpng-native', 'libxext-native', 'libxrender-native', 'libxrandr-native', 'libx11-native', 'xproto-native', 'libassuan-native', 'swig-native', 'libgpg-error-native', 'python3-setuptools-native', 'xextproto-native', 'renderproto-native', 'randrproto-native', 'libxcb-native', 'inputproto-native', 'xtrans-native', 'kbproto-native', 'unzip-native', 'xcb-proto-native', 'libxau-native', 'libpthread-stubs-native', 'libxdmcp-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_image_wic
| INFO: Creating image(s)...
| 
| ERROR: /home/martyn/Documents/yocto/meta-qcom/scripts/lib/wic/canned-wks/dragonboard410c-sd.wks:8: unrecognized arguments: --part-name
| 
| WARNING: /home/martyn/Documents/yocto/build-dragonboard-rocko/tmp/work/dragonboard_410c-poky-linux/core-image-minimal/1.0-r0/temp/run.do_image_wic.31942:1 exit 1 from 'BUILDDIR="/home/martyn/Documents/yocto/build-dragonboard-rocko" wic create "$wks" --vars "/home/martyn/Documents/yocto/build-dragonboard-rocko/tmp/sysroots/dragonboard-410c/imgdata/" -e "core-image-minimal" -o "$out/"'
| ERROR: Function failed: do_image_wic (log file is located at /home/martyn/Documents/yocto/build-dragonboard-rocko/tmp/work/dragonboard_410c-poky-linux/core-image-minimal/1.0-r0/temp/log.do_image_wic.31942)
ERROR: Task (/home/martyn/Documents/yocto/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_wic) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2965 tasks of which 2958 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/martyn/Documents/yocto/poky/meta/recipes-core/images/core-image-minimal.bb:do_image_wic
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
martyn@hades:~/Documents/yocto/build-dragonboard-rocko$ 

What am I doing wrong?

Trying to find MDM9607 support

Hello everyone. I try to compile the basic template FW for MDM9607 CPU.
But system says: "MACHINE=mdm9607 is invalid. Please set a valid MACHINE in your local.conf"
I figured out that there are no such machine in meta-qcom, but this was mentioned some time ago as existing:
the-modem-distro/pinephone_modem_sdk#1

The global question, that I have. How can I adjust properly my environment specially for MDM9607 CPU?? Due I cannot find any mentions in meta-qcom.

Thanks.

Dragonboard 410c qcom_camss dma attach fails (kernel crash) when booting

Hi,

I am having trouble loading the camss module for my camera testing. I have built a custom morty image. As the title said the camss trying to attach to the memory with iommu, but the kernel crashed. I am not sure if this is the qcom error. here is the log.

Can someone please help? Thank you in advance. Let me know if you want more information.

Best Regards
Jay

[    4.043798] msm_cci 1b0c000.qcom,cci: Entity type for entity msm_cci was not initialized!
[    4.043864] msm_cci_init_gpio_params:1383 gpio count 0
[    4.053292] iommu: Adding device 1b0ac00.camss to group 0
[    4.056155] ------------[ cut here ]------------
[    4.061454] WARNING: CPU: 3 PID: 2102 at /home/gumstix/yocto/build/tmp/work-shared/dragonboard-410
c/kernel-source/arch/arm64/mm/dma-mapping.c:843 arch_teardown_dma_ops+0x28/0x48
[    4.066143] Modules linked in: msm_rng(+) rng_core venus_core(+) qcom_camss(+) mdt_loader videobuf
2_dma_sg v4l2_mem2mem videobuf2_memops qcom_cci videobuf2_v4l2 videobuf2_core
[    4.097200]
[    4.097466] CPU: 3 PID: 2102 Comm: systemd-udevd Not tainted 4.9.27+linaro #12
[    4.099032] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[    4.106063] task: ffff8000361e6800 task.stack: ffff800035b28000
[    4.112922] PC is at arch_teardown_dma_ops+0x28/0x48
[    4.118562] LR is at arch_teardown_dma_ops+0x14/0x48
[    4.123769] pc : [<ffff000008096828>] lr : [<ffff000008096814>] pstate: 20000145
[    4.128719] sp : ffff800035b2bad0
[    4.136093] x29: ffff800035b2bad0 x28: 0000000000000124
[    4.144422] x27: ffff00000990b000 x26: ffff000008131cb0
[    4.149717] x25: 0000000000000001 x24: ffff800034a55948
[    4.155012] x23: 000000000000002a x22: 00000000ffffffed
[    4.160307] x21: ffff000000aaac38 x20: ffff000009162000
[    4.165602] x19: ffff8000365c1010 x18: 0000000000000000
[    4.170898] x17: 0000ffffb4798400 x16: ffff000008135d18
[    4.176192] x15: 0000000000000000 x14: 00014db100014da9
[    4.181487] x13: 0000000000000002 x12: 0000000000000002
[    4.186783] x11: 00000000021a6383 x10: ffff800035f85c00
[    4.192078] x9 : 0000000000000001 x8 : ffff80000eb34180
[    4.197373] x7 : ffff800037f6db08 x6 : 0000000000895440
[    4.202668] x5 : ffff8000361e6800 x4 : ffff8000361e6880
[    4.207964] x3 : 0000000000000002 x2 : ffff800034b2b9b8
[    4.213259] x1 : 0000000000000000 x0 : ffff800034b2ba28
[    4.218553]
[    4.218729] ---[ end trace e501593c863bd5c3 ]---
[    4.220297] Call trace:
[    4.224895] Exception stack(0xffff800035b2b900 to 0xffff800035b2ba30)
[    4.227072] b900: ffff8000365c1010 0001000000000000 ffff800035b2bad0 ffff000008096828
[    4.233669] b920: ffff800035b2b940 ffff0000080e222c ffff80000eb34100 ffff800037f6da80
[    4.241483] b940: ffff800035b2b970 ffff0000080e3c8c ffff80000eb34100 0000000000000000
[    4.249295] b960: ffff80000eb34834 00000000000001c0 ffff800035b2b9d0 ffff0000080e3e04
[    4.257107] b980: 0000000000000002 ffff800036578200 ffff000008fa7a78 ffff000009133748
[    4.264919] b9a0: ffff800034b2ba28 0000000000000000 ffff800034b2b9b8 0000000000000002
[    4.272731] b9c0: ffff8000361e6880 ffff8000361e6800 0000000000895440 ffff800037f6db08
[    4.280544] b9e0: ffff80000eb34180 0000000000000001 ffff800035f85c00 00000000021a6383
[    4.288357] ba00: 0000000000000002 0000000000000002 00014db100014da9 0000000000000000
[    4.296169] ba20: ffff000008135d18 0000ffffb4798400
[    4.303980] [<ffff000008096828>] arch_teardown_dma_ops+0x28/0x48
[    4.308671] [<ffff00000885bcec>] of_dma_deconfigure+0xc/0x18
[    4.314919] [<ffff0000085c2574>] dma_deconfigure+0xc/0x18
[    4.320561] [<ffff0000085aa234>] driver_probe_device+0x36c/0x440
[    4.325856] [<ffff0000085aa41c>] __driver_attach+0x114/0x118
[    4.331931] [<ffff0000085a7da0>] bus_for_each_dev+0x60/0xa0
[    4.337575] [<ffff0000085a9838>] driver_attach+0x20/0x28
[    4.342867] [<ffff0000085a92a8>] bus_add_driver+0x1f0/0x2a8
[    4.348424] [<ffff0000085aac60>] driver_register+0x60/0xf8
[    4.353720] [<ffff0000085abebc>] __platform_driver_register+0x44/0x50
[    4.359297] [<ffff000000ab1018>] qcom_camss_driver_init+0x18/0x1000 [qcom_camss]
[    4.365789] [<ffff0000080830d8>] do_one_initcall+0x38/0x128
[    4.373251] [<ffff00000816e9bc>] do_init_module+0x5c/0x1b8
[    4.378547] [<ffff000008135464>] load_module+0x1c54/0x2318
[    4.384101] [<ffff000008135e30>] SyS_finit_module+0x118/0x128
[    4.389571] [<ffff000008082f4c>] __sys_trace_return+0x0/0x4
[    4.395999] iommu: Adding device 1d00000.video-codec to group 1

${DATETIME} causes autobuilder meltdown

do_deploy and friends will be re-executed every build, leading to a lot of clutter (e.g. http://dominion.thruhere.net/angstrom/nightlies/v2015.12/dragonboard-410c/ ).

PRSERV should be used to get monotonically increasing versioning, not ${DATETIME}

fido branch

I'm running into issues with repo updating git trees that have their revisions locked down in the manifest and the most failure proof fix is to create release branches everywhere. I've prepared a fido branch for meta-qcom here: https://github.com/koenkooi/meta-qcom/tree/fido

Since I'm using fido myself I also volunteer to backport things from master/jethro and keep it working with oe-core fido updates.