# Build with QSC Launcher
The following sections explain how to configure, download, compile, and flash Qualcomm Linux using the QSC Launcher.
## Host machine requirements
>
>
> | Configuration | Permissions |
> | --- | --- |
> | x86 machine | A `sudo` permission is required to run a few commands |
> | Quad-core CPU, for example, Intel i7-2600 at 3.4 GHz
(equivalent or better) | A `sudo` permission is required to run a few commands |
> | 300 GB free disk space (swap partition > 32 GB) | A `sudo` permission is required to run a few commands |
> | 16 GB RAM | A `sudo` permission is required to run a few commands |
> | Ubuntu 22.04 | A `sudo` permission is required to run a few commands |
> | | |
> | | |
> | | |
> | | |
## Install QSC using a GUI
1. Use your registered email ID to log in to [https://softwarecenter.qualcomm.com](https://softwarecenter.qualcomm.com), then click **Download Software Center**.
The QSC Debian package (`.deb`) is downloaded to your machine.
2. To install the QSC Debian package using the Ubuntu GNOME GUI, it is necessary to first ensure GDebi is installed. Run the following command on your Linux host machine to install GDebi:
sudo apt install gdebi
Copy to clipboard
3. Right-click on the downloaded QSC Debian file and click **Open with GDebi Package Installer**.
4. Click **Install Package**.
5. Enter the password for the current user. In the following image, the current user is Ubuntu.
6. Accept the license agreement. Click **Next**.
7. Click **I ACCEPT**.
Wait for the installation to complete.
8. To find the Qualcomm Software Center, click **Show Applications**.
## Use QSC Launcher
### Software download
1. To open the QSC Launcher desktop application, launch **Qualcomm Software Center** from the **Applications** menu.
Note
For the Launcher workflow to detect connected devices and flash software builds, ensure that the Qualcomm Product Configuration Assistant Tool (PCAT) and Qualcomm USB Driver (QUD) are installed on the host machine. Click **PCAT** to install PCAT and **QUD** to install QUD as shown in the following image:
**Or**
Install PCAT and QUD using `qpm-cli`:
qpm-cli --login
qpm-cli --install pcat --activate-default-license
qpm-cli --install qud --activate-default-license
Copy to clipboard
The `qpm-cli --help` command lists the help options.
For Ubuntu 22.04, you may encounter an issue while installing QUD where you are asked to enroll the public key on your Linux host for a
successful QUD installation. For more details, follow the steps provided in the `signReadme.txt` file available at the `/opt/QUIC/sign/` directory.
2. Use your registered email ID to log in to the QSC desktop application. The QSC Launcher dashboard page appears.
- If you do not have a connected device, click **Start Launcher** (A) on the top panel.
- If you have a connected device, click **Start Launcher** (B) for the appropriate device in the **Connected devices** panel.
3. On the **Specify Environment** page, select the appropriate values for **Category**, **Chipset**, **Host Operating System**, and **Target Operating System**.
Note
See [hardware SoCs (chipsets)](https://docs.qualcomm.com/bundle/publicresource/topics/80-70015-115/soc.html) that are supported on Qualcomm Linux.
4. Click **Next**. The **Select Resources** page appears.
1. In the **Base Workspace Path** text box, specify a directory where you want to download the software.
2. Select the **Software Product**.
3. Select the **Distribution** and the **Release Tag**.
Note
- For information on the supported distributions for your hardware SoCs, see the table *Access Controlled Distribution* in the [Release Notes](https://docs.qualcomm.com/bundle/publicresource/topics/RNO-240929204440/).
- For information on the Yocto layers, see [Qualcomm Linux metadata layers and descriptions](https://docs.qualcomm.com/bundle/publicresource/topics/80-70015-27/platform_software_features.html#qualcomm-linux-metadata-layers-overview).
- For information on the QIMP and QIRP SDKs, see the following guides:
- [QIMP SDK Quick Start Guide](https://docs.qualcomm.com/bundle/publicresource/topics/80-70015-51)
- [QIRP SDK 2.0 User Guide](https://docs.qualcomm.com/bundle/publicresource/topics/80-70015-265)
5. Click **Download** to download the selected compilable distribution or flashable binary. After the software is downloaded successfully, a *Download complete* status appears.
Note
You can also track the download progress through the **Downloads** option in the top menu bar.
You do not have to compile flashable binaries. If you have selected a flashable binary, follow the on-screen instructions to flash to a connected device.
### Build and flash default configuration
1. Compile the default build.
Note
For information on the default configurations, see the table *Default values of “MACHINE” and “QCOM\_SELECTED\_BSP” parameters for QSC* in the [Release Notes](https://docs.qualcomm.com/bundle/publicresource/topics/RNO-240929204440/).
1. After the download is complete, select **Compile** to start compiling. Depending on the size of the downloaded software and the host machine configuration, the compilation process may take a few hours.
2. To view the compilation progress, expand the logs panel.
Note
BitBake fetch errors are typically intermittent fetch failures. To resolve these errors, retry [step 1a](https://docs.qualcomm.com/doc/80-70015-254/topic/build_from_source_qsc_gui_intro.html#launcher-compile-step). If the issue persists, see [BitBake Fetcher Error](https://docs.qualcomm.com/doc/80-70015-254/topic/troubleshoot_sync_build_and_flash.html#do-fetch-error-1) for a solution.
2. Flash the software with the default configuration.
Note
Before you flash the software, ensure that the device is in Emergency Download (EDL) mode. For more information on how to force the device into EDL mode, see [Move to EDL mode](https://docs.qualcomm.com/doc/80-70015-254/topic/flash_images.html#section-vgg-mly-v1c).
1. Flash the software by selecting the device on which you want to flash the compiled software. If multiple devices are connected, select the correct target device.
2. Click **Flash on device**. The page is updated and displays a progress bar as QSC Launcher begins flashing the software. Leave the device connected while the software is being flashed.
3. To view the compilation progress of individual software images, expand the logs panel.
4. When the process is finished, the page displays a *Flash Complete* message.
5. Click **Done**.
Note
The device reboots after the flashing procedure is completed successfully. To verify the updated software version, see [Check software version](https://docs.qualcomm.com/bundle/publicresource/topics/80-70015-253/set_up_the_device.html#check-software-version).
### Build your own configuration
To build your own configuration, compile the build for default machine configuration and then compile the LE.QCLINUX.1.0.r1 image with your own MACHINE and QCOM\_SELECTED\_BSP parameter values.
1. [Compile the build for the default machine configuration](https://docs.qualcomm.com/doc/80-70015-254/topic/build_from_source_qsc_gui_intro.html#launcher-build-default-config).
2. Compile the LE.QCLINUX.1.0.r1 image with your own MACHINE and QCOM\_SELECTED\_BSP parameter values.
Note
For information on the supported machine configurations of the development kit, see the table *MACHINE and QCOM\_SELECTED\_BSP parameter value* in the [Release Notes](https://docs.qualcomm.com/bundle/publicresource/topics/RNO-240929204440/).
1. To run the build commands for a specific configuration, click **Compile using terminal**.
Note
Compilations initiated through the terminal are not tracked by the Qualcomm Software Center, making it impossible to track their progress on the Download page.
2. Click **Open Terminal**. A terminal window with expanded default build command appears.
3. Update the highlighted command with your own configuration and run it on the terminal:
For example, to build for Qualcomm® RB3 Gen 2 Core Development Kit, change the value of `MACHINE` in the preceding build command to `qcs6490-rb3gen2-core-kit`.
4. After a successful build, check that the `system.img` file is in the `/DEV/LE.QCLINUX.1.0.r1/build-/tmp-glibc/deploy/images//qcom-multimedia-image` directory with an updated timestamp. For example:
cd /build-qcom-wayland/tmp-glibc/deploy/images/qcs6490-rb3gen2-core-kit/qcom-multimedia-image
ls -al system.img
Copy to clipboard
Note
When compiling a software image other than `LE.QCLINUX.1.0.r1`, ensure that you also compile both the software product and `LE.QCLINUX.1.0.r1` in the same order.
For example, if you compile `BOOT.MXF.1.0.c1`, ensure that you also compile the software product (such as `QCM6490.LE.1.0`) and then `LE.QCLINUX.1.0.r1`.
3. To flash your build, see [Flash images](https://docs.qualcomm.com/doc/80-70015-254/topic/flash_images.html#flash-images).
Note
- Before flashing, update the build images path to the compiled build images workspace at `/DEV/LE.QCLINUX.1.0.r1/build-/tmp-glibc/deploy/images//qcom-multimedia-image`.
For example, `/build-qcom-wayland/tmp-glibc/deploy/images/qcs6490-rb3gen2-core-kit/qcom-multimedia-image`.
## Connect to UART shell and Network
After flashing and booting the device, follow these steps to connect to UART shell, Network and Login via SSH.
- [Connect to UART shell](https://docs.qualcomm.com/doc/80-70015-254/topic/how_to.html#section-ags-ssh-p1c-vinayjk-03-01-24-1109-49-684)
- [Connect to Network](https://docs.qualcomm.com/doc/80-70015-254/topic/how_to.html#section-hmw-vsh-p1c-vinayjk-03-01-24-1110-45-279)
- [Login via SSH](https://docs.qualcomm.com/doc/80-70015-254/topic/how_to.html#howto-login-via-ssh)
Last Published: Feb 03, 2026
[Previous Topic
Introduction](https://docs.qualcomm.com/bundle/publicresource/80-70015-254/topics/introduction.md) [Next Topic
Build with QSC CLI](https://docs.qualcomm.com/bundle/publicresource/80-70015-254/topics/build_from_source_QSC_CLI.md)
Source: [https://docs.qualcomm.com/doc/80-70015-254/topic/build_from_source_qsc_gui_intro.html](https://docs.qualcomm.com/doc/80-70015-254/topic/build_from_source_qsc_gui_intro.html)