Skip to main content
This section explains how to resolve common Yocto build failures and debug issues in the Qualcomm Linux workspace.

​
Debug tools

packagegroup-core-tools-debug defined in the <workspace>/layers/poky/meta directory adds debug tools as part of rootfs. The <workspace>/layers/meta-qcom-hwe/recipes-devtools directory contains the appended package group recipe as packagegroup-core-tools-debug.bbappend. This append file adds ltrace, perf, sysstat, and valgrind tools to this package group. For more information, see Debug Linux user space issues.

​
Common Yocto build failures

For common build failures related to QA issues such as version going backwards, see Verify QA issue: Version going backwards.

​
Layer exclusion issues

If BitBake didn’t parse a newly added layer, the recipes from that layer aren’t included in the image.
  1. Run the following command, and verify that you see the layer in the output:
  2. If you can’t find the layer, confirm the contents of the conf/bblayers.conf file to ensure that the layer is included.

​
Debug builds

To generate a debug build, run the following command:
To understand which kernel defconfig and config fragments are used when DEBUG_BUILD is set to 1, see Kernel recipe, under Kernel recipes. The following code snippet from recipes-kernel/linux/linux-qcom_6.18.bb enables the debug configuration fragment for the kernel being built:
For a dedicated debug build guide, see Create a build for debugging.

​
Tooling & logs

​
Verify QDL and ModemManager

If you are using a Linux distribution with systemd, use the systemctl command to stop ModemManager. The following is an example from Ubuntu 22.04:
  1. To verify the ModemManager status, run the following command:
  2. To stop ModemManager, run the following command:
  3. The ps aux command doesn’t show any entry for /usr/sbin/ModemManager. If you need ModemManager, you must restart it after the flashing is complete and verify if it has started: