> ## Documentation Index
> Fetch the complete documentation index at: https://dragonwingdocs.qualcomm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Wasp

## **What is Wasp?**

**Wasp** is Qualcomm’s **Zephyr-based** embedded software platform for small subsystem processors across Qualcomm SoCs. It provides a complete RTOS with a standardized, reusable firmware stack providing common drivers, services, and integration support.

## **What does the Wasp SDK provide?**

The Wasp SDK (`wasp-sdk`) is the platform *manifest repository* for Wasp. It provides:

* **Board support packages (BSPs)** — SoC and board definitions for all supported Qualcomm platforms.
* **Qualcomm subsystem drivers** — drivers for infrastructure IP blocks (clocks, power regulators, GPIOs, TLMM, IPCC, SPMI, and more).
* **Platform services** — OS abstraction layer (OSAL), inter-processor communication (mproc), power management, logging, and more.
* **Build and workspace tooling** — West extensions (`west qc-build`, `west qc-sign`) for building and signing Qualcomm firmware images using the standard Zephyr workspace workflow.
* **Device tree infrastructure** — split static (Zephyr macro-based) and dynamic (libfdt DTB) device tree support, optimized for Qualcomm SoC resource management.
* **CI and test support** — QEMU board variants for off-target testing, ZTest integration, and Coral CI pipeline configuration.

## **Relationship to Zephyr**

Wasp is built on top of the [<u>Zephyr RTOS</u>](https://zephyrproject.org/). Zephyr provides the kernel, scheduler, device driver model, device tree framework, build system (CMake + West), and the upstream driver ecosystem. Wasp extends Zephyr with Qualcomm-specific platform code that cannot or has not yet been contributed upstream.

The relationship is intentionally layered:

* **Upstream Zephyr** — kernel, generic subsystems, and drivers that are not Qualcomm-specific. See how Wasp tracks upstream Zephyr releases in the [<u>branching model</u>](https://animated-fortnight-o3ll9mn.pages.github.io/integration/branching-model.html).
* `wasp-sdk` — Qualcomm platform code: BSPs, HAL drivers, and platform services. Code in this layer is intended to follow Zephyr coding conventions and driver APIs so that it can be contributed upstream over time (although leverage with other Software Platforms results in divergence in some cases).
* **Product firmware images** — application-level code and configuration that consumes the SDK to produce signed firmware images for specific SoC targets.

Qualcomm has approval to contribute most code to the Zephyr project (Apache 2.0 license), and upstreaming Qualcomm drivers is an active goal.

## **Repository Layout**

The SDK is structured as a [<u>west</u>](https://docs.zephyrproject.org/latest/develop/west/index.html) manifest repository. The workspace is structured as follows:

```text theme={null}
<workspace>/
├── wasp-sdk/       ← this repository (manifest)
├── zephyr/         ← upstream Zephyr RTOS
├── modules/        ← external modules (HALs, libraries)
└── applications/   ← application code
```