Skip to main content

​
Introduction

This document provides instructions to sync, build, and flash images using the qsc-cli tool. It is intended for registered users who have access to Qualcomm’s proprietary resources. The qsc-cli tool streamlines the workflow by providing a unified interface that runs tasks in containerized environments, ensuring simplicity, consistency, and reproducibility. At a high level, you will learn the following:

​
Supported SoCs

The following SoCs are supported in this guide. If you do not see your SoC listed, the QSC CLI build process described here does not apply to your device. The following SoCs are supported by this document. If your chipset is not listed, the firmware build process described here does not apply to your device.
QSC CLI currently does not support compilation for the distributions Qualcomm_Linux.SPF.2.0|AP|Standard|OEM| and Qualcomm_Linux.SPF.2.0|AMSS|Standard|OEM|. Please refer to the BSP image build with firmware document for manual compilation steps.

​
Host Requirements

  • Operating System
    • Ubuntu
  • Configuration
    • Quad-core CPU, for example, Intel i7-2600 at 3.4 GHz (equivalent or better)
    • 300 GB free disk space (swap partition > 32 GB)
    • 16 GB RAM

​
Install QSC-CLI

qsc-cli is a command-line tool provided by Qualcomm that offers an end-to-end workflow for accessing, managing, and building Qualcomm software. Follow these steps to install qsc-cli on your system:
  • Register your Qualcomm email ID by visiting the Qualcomm Support Page.
  • Download the Debian package for qsc-cli:
  • Install the qsc-cli Debian package:
  • Sign in to qsc-cli using your Qualcomm ID. For most users, your Qualcomm ID is your email address. This opens a browser window to complete authentication. If the browser doesn’t open automatically, copy the link printed in the terminal and paste it into your browser to complete authentication.

​
Configuration parameters

The following tables lists the --product, --release, --image and --distribution parameter values used by the chip-software download and chip-software compile commands.

​
Download the software

Download a software release using the chip-software download command. Use the previous tables to look up the --product, --release, and --distribution values for your SoC:

​
Build the default configuration

​
Compile

When the download is complete, start the compilation process. Depending on the size of the software and the host computer configuration, the compilation process can take a few hours.
This process builds the necessary Qualcomm firmware and completes the Qualcomm Linux build.

​
Recompile

To recompile individual software images after any modifications to the software release, use your existing workspace built using QSC CLI:

​
Build your own configuration

To build your own configuration, you must compile the build with the default machine configuration and then compile the software product with your own machine and distribution configuration files. When compiling a software image, ensure that you also compile the software product. For example, if you compile BOOT.MXF.1.0.c1, ensure that you also compile the software product (such as QCS9100.LE.2.0).
  • Compile the build for the default machine configuration.
  • Compile the software product with your own machine and distribution configuration files.
    This command opens a terminal.
  • Update the highlighted command according to your own machine configuration and run it on the terminal. For example, to build IQ-9075-EVK, change the value of <machine.yml> to iq-9075-evk.yml. build-own-config
  • The build creates a single tarball containing all the relevant files to perform a full clean flash, including partition metadata, boot firmware, ESP partition and the rootfs. After a successful build, check if the qcomflash tarball exists in the build artifacts. The following examples use qcom-multimedia-proprietary-image as the image name.
An environment is set up to run your own build commands for a specific software image. QSC won’t track the status of input workspaces in future releases, and you cannot flash these workspaces with qsc-cli.