QIR SDK components
The QIR SDK has the following components that help you build, run, and update robotics applications on Qualcomm Dragonwing hardware.- ROS 2 Jazzy packages tuned for Qualcomm Dragonwing hardware.
- Prebuilt Qualcomm Linux robotics images (
qcom-robotics-image,qcom-robotics-proprietary-image) and Ubuntuaptpackages (qirp-sdk,qirp-sdk-desktop). - Cross-compile toolchain for building applications on the host and deploying them to the device.
- End-to-end sample applications for platform, robotics, and AI vision use cases.
- Qualcomm Linux overlays (optional) that expand a base robotics image into the full Qualcomm proprietary stack without reflashing.
1
Learn the supported devices, operating systems and scenarios.
First, understand the following information:
Supported OS-device matrix
What OS the QIR SDK supports for each device.
On-device operating system
Differences between Qualcomm Linux and Ubuntu OS when using the robotics workflow.
Robotics working scenarios
What you can do in three main scenarios.
2
Pick your combination.
Review the Workflow decision tree and pick a combination using the Workflow picker.
3
Go through the tutorial for the scenario combination you choose.
Follow the matching tab on the Scenarios page, based on your choice.
4
Check end-to-end samples.
Supported OS-device matrix
The QIR SDK targets three platforms for robotics application development. Each device differs in compute class, camera and sensor ports, and OS support. The following table lists the device and operating system combinations covered by the unified robotics workflow.
Match a device to your project priority:
- IQ-9075 EVK — the widest sample coverage, including every AI sample, all robotics simulations, and multi-camera pipelines on either OS.
- IQ-8275 EVK — the Qualcomm proprietary multimedia stack (
qrb_ros_camera,qrb_ros_video,qrb_ros_audio_service,qrb_ros_colorspace_convert) on Qualcomm Linux. - VENTUNO™ Q — a lower-cost board that can be used as a Single-board Computer (SBC).
On-device operating system
The QIR SDK ships in two flavors that share ROS 2 Jazzy and most sample sources but differ in packaging, image build, and update model. The following table lists and compares the features supported by each host.- Pick Qualcomm Linux when you plan to customize the OS or ship a hardened Yocto image.
-
Pick Ubuntu when you want a Debian-based experience with
apt-managed updates and no Yocto.
The following table maps the Ubuntu image variant to the correct QIR SDK package. Installing the wrong package causes runtime errors.
Robotics working scenarios
The QIR SDK supports three scenarios, from a short evaluation to a full production build. The following table compares the scope, output, and time investment among the three scenarios.
The scenarios build on each other — most teams pass through Evaluate on the way to Development, and through Development on the way to Production. All three scenarios and their runnable examples live on the Scenarios page.
Robotics workflow decision tree
The following decision-tree diagram shows the full robotics workflow: start with the state of your device, branch on your goal, and land on the concrete tools and packages you use. Every leaf maps to a runnable procedure on the Scenarios or End-to-end samples page.Pick your combination
Use the picker to select a device, an operating system, and a scenario. The card at the bottom links to the matching tab on the Scenarios page.Next steps
Pick the entry point that matches how deep you want to go.- Scenarios — pick a tab for Evaluate, Development, or Production. Each tab pairs the workflow diagram with a runnable example.