# Debug

Source: [https://docs.qualcomm.com/doc/80-70014-27/topic/debug.html](https://docs.qualcomm.com/doc/80-70014-27/topic/debug.html)

Debug provides the pointers on how users can customize the Yocto based workspace and how
            users can overcome general problems and issues.

## QDL and ModemManager

Source: [https://docs.qualcomm.com/doc/80-70014-27/topic/debug.html](https://docs.qualcomm.com/doc/80-70014-27/topic/debug.html)

### About this task

If you are using a Linux distribution with `systemd`,
                    `ModemManager` can be stopped by using
                `systemctl`. The following is an example from Ubuntu 22.04:

### Procedure

1. Verify the `ModemManager` status:
                
systemctl status ModemManagerCopy to clipboard

        ModemManager.service - Modem Manager
           Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
           Active: active (running) since Tue 2023-11-28 16:28:15 IST; 3 months 4 days ago
         Main PID: 1338 (ModemManager)
            Tasks: 3 (limit: 4915)
           CGroup: /system.slice/ModemManager.service
                   └─1338 /usr/sbin/ModemManager --filter-policy=strictCopy to clipboard

        ps aux | grep -i modemmanagerCopy to clipboard

        root      1338  0.0  0.0 434332  9544 ?        Ssl   2023  10:39 /usr/sbin/ModemManager --filter-policy=strictCopy to clipboard
2. Stop `ModemManager`:
                
systemctl stop ModemManager
        systemctl status ModemManagerCopy to clipboard

        ModemManager.service - Modem Manager
           Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
           Active: inactive (dead) since Sun 2024-03-03 20:08:32 IST; 4s ago
          Process: 1338 ExecStart=/usr/sbin/ModemManager --filter-policy=strict (code=exited, status=0/SUCCESS)
         Main PID: 1338 (code=exited, status=0/SUCCESS)Copy to clipboard
3. The `ps aux` command does not 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:
                
systemctl start ModemManager
        systemctl status ModemManagerCopy to clipboard

        ModemManager.service - Modem Manager
           Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
           Active: active (running) since Sun 2024-03-03 20:11:46 IST; 43s ago
         Main PID: 14785 (ModemManager)
            Tasks: 3 (limit: 4915)
           CGroup: /system.slice/ModemManager.service
                   └─14785 /usr/sbin/ModemManager --filter-policy=strictCopy to clipboard

        ps aux | grep -i modemmanagerCopy to clipboard

        root     14785  4.6  0.0 434332  9160 ?        Ssl  20:11   0:00 /usr/sbin/ModemManager --filter-policy=strictCopy to clipboard

## Newly added layer excluded from build

Source: [https://docs.qualcomm.com/doc/80-70014-27/topic/debug.html](https://docs.qualcomm.com/doc/80-70014-27/topic/debug.html)

If you are not able to include recipes from a newly added layer in the image, it is
            because BitBake did not parse the layer. Run the following command, and verify if you
            see the layer in the
            output:

    bitbake -e | grep ^BBLAYERS=Copy to clipboard

If you cannot find the layer, confirm the contents of the file
                `conf/bblayers.conf`, to ensure that the layer is included
            here:

    # These layers hold recipe metadata not found in OE-core, but lack any machine or distro content
    BASELAYERS ?= " \
      ${WORKSPACE}/layers/meta-openembedded/meta-oe \
      ${WORKSPACE}/layers/meta-openembedded/meta-filesystems \
      ${WORKSPACE}/layers/meta-openembedded/meta-networking \
      ${WORKSPACE}/layers/meta-openembedded/meta-perl \
      ${WORKSPACE}/layers/meta-openembedded/meta-python \
      ${WORKSPACE}/layers/meta-openembedded/meta-gnome \
      ${WORKSPACE}/layers/poky/meta \
      ${WORKSPACE}/layers/poky/meta-poky \
      ${WORKSPACE}/layers/meta-security \
      ${WORKSPACE}/layers/meta-selinux \
      ${WORKSPACE}/layers/meta-virtualization \
    "
     
    # These layers hold machine specific content, aka Board Support Packages
    BSPLAYERS ?= " \
      ${WORKSPACE}/layers/meta-qcom-hwe \
      ${WORKSPACE}/layers/meta-qcom \
    "
     
    # Add your overlay location to EXTRALAYERS
    # Make sure to have a conf/layers.conf in there
    EXTRALAYERS ?= "${WORKSPACE}/layers/meta-qcom-extras"
     
    BBLAYERS = " \
      ${WORKSPACE}/layers/meta-qcom-distro \
      ${EXTRALAYERS} \
      ${BASELAYERS} \
      ${BSPLAYERS} \
    "Copy to clipboard

Last Published: Jul 11, 2024

[Previous Topic
User customizations](https://docs.qualcomm.com/bundle/publicresource/80-70014-27/topics/user_customizations.md) [Next Topic
References](https://docs.qualcomm.com/bundle/publicresource/80-70014-27/topics/references.md)