# Update the Qualcomm Linux software
Note
Qualcomm Visual Studio Code Extension isn’t available in the QLI 2.0 RC3 release. It will be available in a future release.
To update the software on your Qualcomm Dragonwing^™^ RB3 Gen 2 development kit, download and flash the prebuilt images of the latest software using one of the following methods.
Caution
Updating the software with the prebuilt images erases all data on your device and installs a newer image. Back up important data before you start.
**Use the Qualcomm Visual Studio Code Extension to update the software**
Update the software using the Qualcomm Visual Studio Code Extension integrated development environment from an Ubuntu or Windows^®^-based host computer. For instructions, see [Qualcomm Visual Studio Code Extension Reference Guide](https://docs.qualcomm.com/bundle/publicresource/topics/80-79972-1/quick_start.html).
https://docs.qualcomm.com/bundle/publicresource/topics/80-79972-1/quick_start.html
**Use a host computer to manually update the software**
Update the software manually using an Ubuntu, Windows^®^, or macOS^®^-based host computer. For instructions, see [Update the Qualcomm Linux software manually using a host computer](https://docs.qualcomm.com/doc/80-80022-251/topic/upgrade-rb3gen2-software.html#update-sw-manually).
https://docs.qualcomm.com/doc/80-80022-251/topic/upgrade-rb3gen2-software.html#update-sw-manually
**Use over-the-air update tools to update the software**
Update the software incrementally using over-the-air (OTA) tools such as Capsule and the OSTree tool. For instructions, see [Qualcomm Linux Yocto Guide](https://docs.qualcomm.com/bundle/publicresource/topics/80-80022-27/update_fw_and_os_qualcomm_linux_using_capsule_and_ostree_mechanisms.html).
https://docs.qualcomm.com/bundle/publicresource/topics/80-80022-27/update_fw_and_os_qualcomm_linux_using_capsule_and_ostree_mechanisms.html
## Update the Qualcomm Linux software manually using a host computer
Use the following workflow to upgrade the software manually from an Ubuntu, Windows, or macOS-based host computer.
**Figure: Software upgrade workflow of Dragonwing RB3 Gen 2 Development Kit**
### Prerequisites
- Back up any important data on your Dragonwing RB3 Gen 2 device.
- Check that the host computer has enough free storage. The software requires at least 19 GB of space.
### Procedure
To update the Qualcomm Linux software, complete the following steps based on the OS of your host computer.
Tab Ubuntu
Tab Windows
Tab macOS
- *class* tabincludedirective
- #### Download the software
1. [Download the software](https://artifacts.codelinaro.org/artifactory/qli-ci/flashable-binaries/meta-qcom/rb3gen2-core-kit/qli-2.0-rc3-qcom-multimedia-proprietary-image.zip).
2. Extract the contents of the downloaded zip file on the host computer.
#### Force device into emergency download mode
The device enters emergency download (EDL) mode under two conditions:
- If the device doesn’t have installed software upon initial power-up
- If the currently installed software malfunctions
To facilitate software flashing, you must force the device into EDL mode using one of the following methods.
**Using ADB shell**
To force the device into EDL mode, run the following command:
adb shell reboot edl
Copy to clipboard
For information about how to install ADB, see [FAQs](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#install-adb).
**Using F\_DL button**
1. Connect the device to the host computer through the USB Type-C connector.
2. Hold down the **F\_DL** button.
**Figure: Location of the USB Type-C port and F\_DL button**
3. Connect the device to a 12-V wall power supply.
4. Release the **F\_DL** button. The device should now be in EDL mode.
5. To verify whether the device has entered EDL mode, run the following command on your host computer:
lsusb
Copy to clipboard
**Sample output**
Bus 002 Device 014: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
#### Update udev rules
Udev rules ensure consistent device recognition and naming, facilitate seamless hardware changes, and allow dynamic device management.
Ensure that you configure the `udev` USB rules for the Qualcomm manufacturing vendor ID **05c6** on the Ubuntu host computer. Run the following commands on your Ubuntu host computer:
1. To go to the directory, run the following command:
cd /etc/udev/rules.d
Copy to clipboard
2. To list the contents of the directory, run the following command:
ls
Copy to clipboard
- If the `51-qcom-usb.rules` file isn’t present, use `sudo vi 51-qcom-usb.rules` to create it, and add the following content to the file:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="05c6", ATTRS{idProduct}=="9008", MODE="0664", GROUP="plugdev"
Copy to clipboard
- If the file exists, then check for the earlier content. Use the following command to view the content:
cat 51-qcom-usb.rules
Copy to clipboard
3. To restart `udev`, run the following command:
sudo systemctl restart udev
Copy to clipboard
If the USB cable is already connected to the host computer, unplug the cable and then reconnect it for the updated rules to take effect.
#### Flash using the QDL tool
The Qualcomm Download (QDL) tool is a flashing utility that communicates with USB devices identified by ID 05c6:9008. The tool uploads a flash loader to the device, which then flashes the images to the universal flash storage (UFS) built into the device.
1. Download the [QDL tool](https://softwarecenter.qualcomm.com/catalog/item/Qualcomm_Device_Loader) on the host computer and extract the contents of the downloaded zip file.
2. To provide executable permission, run the following command:
>
>
> chmod +x ./qdl
> Copy to clipboard
For more information about the QDL tool, see **QDL\_User\_Guide** in your unzipped `qdl` directory.
Important
You must perform a one-time [UFS provisioning](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#provision-ufs).
3. To flash the images, run the following commands:
cd /images/rb3gen2-core-kit/qcom-multimedia-proprietary-image-rb3gen2-core-kit
Copy to clipboard
Note
- If flashing fails, see [How to troubleshoot flashing-related issues](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#flash-issues) for further help.
- Replace the `` with the extracted `qli-2.0-rc3-qcom-multimedia-proprietary-image.zip` file path.
Important
If you are using the Vision Kit, update the `cdt.bin` file using the following command: `cp cdt_vision_kit.bin cdt.bin`.
>
>
> /qdl --storage ufs prog_firehose_ddr.elf rawprogram*.xml patch*.xml
> Copy to clipboard
After flashing and successfully rebooting the device, you can view the device information in the terminal window by running the `lsusb` command.
>
>
> The line 4 of the following sample output shows the device information:
>
>
> # Sample output for QCS6490
>
>
> Bus 002 Device 003: ID 05c6:9135 Qualcomm, Inc. qcs6490-rb3gen2-vision-kit
>
>
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
4. Update USB and Ethernet controller firmware. For instructions, see [FAQs](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#usb-firmware).
- *class* tabincludedirective
- #### Download the software
1. [Download the software](https://artifacts.codelinaro.org/artifactory/qli-ci/flashable-binaries/meta-qcom/rb3gen2-core-kit/qli-2.0-rc3-qcom-multimedia-proprietary-image.zip).
2. Extract the contents of the downloaded zip file on the host computer.
##### Force device into emergency download mode
The device enters emergency download (EDL) mode under two conditions:
- If the device doesn’t have installed software upon initial power-up
- If the currently installed software malfunctions
To facilitate software flashing, you must force the device into EDL mode using one of the following methods.
**Using ADB shell**
To force the device into EDL mode, run the following command:
adb shell reboot edl
Copy to clipboard
For information about how to install ADB, see [FAQs](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#install-adb).
**Using F\_DL button**
1. Connect the device to the host computer through the USB Type-C connector.
2. Hold down the **F\_DL** button.
**Figure: Location of the USB Type-C port and F\_DL button**
3. Connect the device to a 12-V wall power supply.
4. Release the **F\_DL** button.
#### Flash using the QDL tool
The Qualcomm Download (QDL) tool is a flashing utility that communicates with USB devices identified by ID 05c6:9008. The tool uploads a flash loader to the device, which then flashes the images to the universal flash storage (UFS) built into the device.
1. Uninstall any other drivers for the device. Ensure that drivers like Qualcomm USB driver aren’t installed. The device shouldn’t appear under **COM Ports** in the **Device Manager**.
2. Download the [QDL tool](https://softwarecenter.qualcomm.com/catalog/item/Qualcomm_Device_Loader) on the host computer and extract the contents of the downloaded zip file.
For more information about the QDL tool, see **QDL\_User\_Guide** in your unzipped `qdl` directory.
4. Run the `install_driver.bat` script from the unzipped QDL directory.
5. To flash the images, run the following command:
Important
- You must perform a one-time [UFS provisioning](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#provision-ufs).
- If you are using the Vision Kit, copy the contents of the `cdt_vision_kit.bin` file to the `cdt.bin` file.
.\qdl.exe prog_firehose_ddr.elf rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml
Copy to clipboard
6. Update USB and Ethernet controller firmware. For instructions, see [FAQs](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#usb-firmware).
Note
- Wildcards aren’t supported for program filenames. List each image file in the command.
- If flashing fails, see [How to troubleshoot flashing-related issues](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#flash-issues) for further help.
- Replace the `` with the extracted `qli-2.0-rc3-qcom-multimedia-proprietary-image.zip` file path.
- *class* tabincludedirective
- #### Download the software
1. [Download the software](https://artifacts.codelinaro.org/artifactory/qli-ci/flashable-binaries/meta-qcom/rb3gen2-core-kit/qli-2.0-rc3-qcom-multimedia-proprietary-image.zip).
2. Extract the contents of the downloaded zip file on the host computer.
##### Force device into emergency download mode
The device enters emergency download (EDL) mode under two conditions:
- If the device doesn’t have installed software upon initial power-up
- If the currently installed software malfunctions
To facilitate software flashing, you must force the device into EDL mode using one of the following methods.
**Using ADB shell**
To force the device into EDL mode, run the following command:
adb shell reboot edl
Copy to clipboard
For information about how to install ADB, see [FAQs](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#install-adb).
**Using F\_DL button**
1. Connect the device to the host computer through the USB Type-C connector.
2. Hold down the **F\_DL** button.
>
>
> 
**Figure: Location of the USB Type-C port and F\_DL button**
3. Connect the device to a 12-V wall power supply.
4. Release the **F\_DL** button. The device should now be in EDL mode.
5. To verify whether the device has entered EDL mode, run the following command on your host computer:
ioreg -p IOUSB
Copy to clipboard
or
system_profiler SPUSBDataType
Copy to clipboard
**Sample output**
Bus 002 Device 014: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
#### Flash using the QDL tool
The Qualcomm Download (QDL) tool is a flashing utility that communicates with USB devices identified by ID 05c6:9008. The tool uploads a flash loader to the device, which then flashes the images to the universal flash storage (UFS) built into the device.
1. Download the [QDL tool](https://softwarecenter.qualcomm.com/catalog/item/Qualcomm_Device_Loader) on the host computer and extract the contents of the downloaded zip file.
For more information about the QDL tool, see **QDL\_User\_Guide** in your unzipped `qdl` directory.
Important
You must perform a one-time [UFS provisioning](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#provision-ufs).
2. To flash the images, run the following command:
cd /target/qcs6490-rb3gen2-vision-kit/qcom-multimedia-proprietary-image-rb3gen2-core-kit
Copy to clipboard
Note
- If flashing fails, see [How to troubleshoot flashing-related issues](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#flash-issues) for further help.
- Replace the `` with the extracted `qli-2.0-rc3-qcom-multimedia-proprietary-image.zip` file path.
Important
If you are using the Vision Kit, update the `cdt.bin` file using the following command: `cp cdt_vision_kit.bin cdt.bin`.
>
>
> /qdl prog_firehose_ddr.elf rawprogram*.xml patch*.xml
> Copy to clipboard
After flashing and successfully rebooting the device, you can view the device information in the terminal window by running the following command.
>
>
> ioreg -p IOUSB
> Copy to clipboard
>
>
> or
>
>
> system_profiler SPUSBDataType
> Copy to clipboard
>
>
> The line 4 of the following sample output shows the device information.
>
>
> # Sample output for QCS6490
>
>
> Bus 002 Device 003: ID 05c6:9135 Qualcomm, Inc. qcs6490-rb3gen2-vision-kit
>
>
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>
>
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
3. Update USB and Ethernet controller firmware. For instructions, see [FAQs](https://docs.qualcomm.com/doc/80-80022-251/topic/faqs.html#usb-firmware).
## Next steps
- [Set up the device](https://docs.qualcomm.com/doc/80-80022-251/topic/set_up_the_device.html#set-up-the-device)
- [Run sample applications](https://docs.qualcomm.com/doc/80-80022-251/topic/demo_app.html#task-ccx-b24-k1c)
Last Published: May 14, 2026
[Previous Topic
Develop an application](https://docs.qualcomm.com/bundle/publicresource/80-80022-251/topics/develop_application.md) [Next Topic
FAQs](https://docs.qualcomm.com/bundle/publicresource/80-80022-251/topics/faqs.md)