Qualcomm Explains How Its Robotics Stack Becomes an SDK Archive

Qualcomm’s robotics catalog spans navigation, perception, sensors and simulation. But its newly published QIR material chiefly spells out the machinery beneath that breadth: build rules that turn components and their dependencies into distributable SDK archives.

The Qualcomm Intelligent Robotics SDK combines Qualcomm Linux layers with dedicated robotics layers. Its meta-qcom-robotics-sdk documentation covers BitBake build classes, distribution configuration, recipes, package groups, images and SDK assembly.

The build path is explicit

Four BitBake classes divide the assembly work. They package ROS-style components, collect runtime dependencies, create symbolic links in the finished root filesystem and assemble distributable robotics SDK archives. The psdk-image class gathers a toolchain, setup scripts, sample content, runtime scripts and runtime packages into a QIRP SDK archive.

The primary ROS 2 configuration enables ROS 2 Jazzy and sets the distribution name to “QCOM Robotics Reference Distro with ROS.” The layer identifies wrynose as its supported Yocto version.

A catalog from motion planning to sensor services

The layer supplies appends and integrations for MoveIt motion planning, Navigation2, ROS perception and communication packages, containers, and support libraries including Ceres Solver, HDF5 and LXC. Its recipe catalog also includes Cartographer SLAM, data transport, OCR, Orbbec cameras, AMR services, audio, cameras, IMU support, neural-network inference, robot-base control, system monitoring, video and RPLidar.

Included application examples

• AprilTag detection, depth estimation, face and hand detection, and pose estimation.
• Object detection and segmentation, a ResNet-101 example, and remote assistance.
• Simulated pick-and-place and simulated AMR simple motion.

Images and package groups are named in the layer

The specification lists qcom-robotics-image and qcom-robotics-proprietary-image recipes. It also names package groups for ROS 2, open-source robotics, proprietary robotics, and open-source packages with proprietary dependencies, alongside a qirp-sdk recipe.