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:
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
to access, manage, and build the Qualcomm software. Follow these steps to install
qsc-cli on your system:
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.
qsc-cli login
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.
Developers building for no modem with prebuilt firmware
Qualcomm_Linux.SPF.2.0|AP|Standard|OEM|NoModem
High level OS and firmware in source without modem
Developers building no modem firmware with HLOS
Qualcomm_Linux.SPF.2.0|AP|Standard|OEM
High-level OS and firmware (GPS only) source
Developers building firmware with GPS chipsets
Qualcomm_Linux.SPF.2.0|AMSS|Standard|OEM
High-level OS and firmware (GPS and modem) source
Developers building firmware with full modem
Supported SoCs
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:
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.
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.
The terminal displays a sample build command. Replace iq-9075-evk.yml with your
own machine configuration file and run the command. For example, to build IQ-8275-EVK,
replace it with iq-8275-evk.yml:
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.
ls build/tmp/deploy/images/iq-9075-evk/qcom-multimedia-proprietary-image-iq-9075-evk.rootfs.qcomflash.tar.gz
ls build/tmp/deploy/images/iq-8275-evk/qcom-multimedia-proprietary-image-iq-8275-evk.rootfs.qcomflash.tar.gz
ls build/tmp/deploy/images/iq-615-evk/qcom-multimedia-proprietary-image-iq-615-evk.rootfs.qcomflash.tar.gz
ls build/tmp/deploy/images/rb3gen2-core-kit/qcom-multimedia-proprietary-image-rb3gen2-core-kit.rootfs.qcomflash.tar.gz
ls build/tmp/deploy/images/iq-x7181-evk/qcom-multimedia-proprietary-image-iq-x7181-evk.rootfs.qcomflash.tar.gz
ls build/tmp/deploy/images/iq-x5121-evk/qcom-multimedia-proprietary-image-iq-x5121-evk.rootfs.qcomflash.tar.gz
ls build/tmp/deploy/images/shikra-evk/qcom-multimedia-proprietary-image-shikra-evk.rootfs.qcomflash.tar.gz
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.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.