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

# Quick Start

> Get from zero to a running app on your Qualcomm® dev kit in minutes.

<Info>
  This guide is for the **host machine** setup path. If you're running VS Code
  directly on your dev kit, see [Run the Extension
  On-Device](./setup-on-device/on-device) instead — the kit is already flashed
  and configured, so this wizard doesn't apply.
</Info>

## Prerequisites

Complete the setup steps before starting this guide:

<CardGroup cols={2}>
  <Card title="Install Visual Studio Code" icon="code" href="./setup/install-vscode">
    Set up VS Code on Ubuntu or Windows with WSL.
  </Card>

  <Card title="Install the Extension" icon="puzzle-piece" href="./setup/install-extension">
    Download the `.vsix` from Qualcomm Software Center and install it in VS
    Code.
  </Card>

  <Card title="Configure udev Rules" icon="sliders" href="./setup/udev-rules">
    Allow USB access for EDL on Linux hosts.
  </Card>

  <Card title="USB Forwarding (WSL)" icon="usb" href="./setup/wsl-usb">
    Forward the device from Windows into WSL using usbipd.
  </Card>
</CardGroup>

<Check>
  Before continuing, confirm the Qualcomm extension icon is visible in the VS
  Code Activity Bar and the **Home** page loads with a **Get Started** button.
</Check>

***

## Step 1 — Run the Getting Started Wizard

Click **Get Started** on the Home page to launch the setup wizard.

<img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/stepper_get_started_button.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=ef55ec0e8907279f35f002b4f2d5b8ab" alt="Get Started button on Home page" width="858" height="427" data-path="archives/2.1/Tools/QVSCE/images/stepper_get_started_button.png" />

The wizard configures your host and dev kit in 5 steps:

<AccordionGroup>
  <Accordion title="Step 1 — Dev Kit" icon="server" defaultOpen="true">
    Select the development kit you want to target. If a device is already connected via USB, the extension detects and pre-selects it. You can also select a kit that is not yet physically connected.

    <img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/stepper_devkit_selection.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=7ab15a1944a40899ea5b4be9ffdf246d" alt="Wizard — dev kit selection" width="1920" height="1140" data-path="archives/2.1/Tools/QVSCE/images/stepper_devkit_selection.png" />

    <Tip>
      **Qualcomm Device Cloud** support — develop and debug on cloud-hosted devices — is coming soon.
    </Tip>

    <Warning>
      Device not showing up? Verify the USB cable, check `lsusb`, and confirm [udev rules](./setup/udev-rules) and [WSL USB forwarding](./setup/wsl-usb) are configured.
    </Warning>
  </Accordion>

  <Accordion title="Step 2 — Operating System" icon="circle-half-stroke">
    Choose the target OS for the selected dev kit. Select the **Variant** and **Version** using the inline dropdowns. The selected device is shown in the top-right corner.

    <img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/stepper_osvariant_selection.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=483f13c34880e2d472a056f827162b23" alt="Wizard — OS selection" width="1920" height="1140" data-path="archives/2.1/Tools/QVSCE/images/stepper_osvariant_selection.png" />
  </Accordion>

  <Accordion title="Step 3 — SDKs" icon="box">
    The wizard lists SDKs available for the selected dev kit and OS. Select the version using the inline dropdown. The latest version for your host architecture (x86\_64 or arm64) is pre-selected.

    <img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/stepper_sdk_selection.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=30469c2d91bc8ec1d881ed37ca235959" alt="Wizard — SDK selection" width="1920" height="1140" data-path="archives/2.1/Tools/QVSCE/images/stepper_sdk_selection.png" />

    <Note>
      To change the SDK version after initial setup, go to **Dashboard → Downloads → SDK tab**.
    </Note>
  </Accordion>

  <Accordion title="Step 4 — Host Tools" icon="wrench">
    Select the development tools to install on your host machine:

    <img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/stepper_sw_selection.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=29b5dbff4948317a2d0dc432005a404d" alt="Wizard — host tools selection" width="1920" height="1140" data-path="archives/2.1/Tools/QVSCE/images/stepper_sw_selection.png" />

    <CardGroup cols={2}>
      <Card title="Host Software" icon="terminal">
        GCC toolchain and debugger.
      </Card>

      <Card title="VS Code Extensions" icon="puzzle-piece">
        C/C++ IntelliSense, CMake Tools, and others that enhance the editor.
      </Card>
    </CardGroup>

    <Tip>
      Keep the defaults if unsure. You can add more tools later from **Dashboard → Downloads**.
    </Tip>

    <Warning>
      Some tools require elevated privileges. Watch the **VS Code Terminal** for `sudo` password prompts (**View → Terminal** if hidden).
    </Warning>
  </Accordion>

  <Accordion title="Step 5 — Downloads" icon="download">
    Click **Download & Install** to fetch and install everything from the previous steps. Progress is shown across four sections: **Operating System**, **SDK**, **Tools**, and **Extensions**.

    <img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/stepper_software_downloads.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=41418f42d11ffc04c9f1318066d73b20" alt="Wizard — downloads and installation" width="1920" height="1140" data-path="archives/2.1/Tools/QVSCE/images/stepper_software_downloads.png" />

    <Tip>
      Use **Install from archive** (OS) or **Install from zip** (SDK) to skip the download if you already have the files on disk.
    </Tip>

    <Warning>
      **Do not close VS Code** during the download — interrupted installs can break the toolchain. Watch the Terminal for `sudo` prompts.
    </Warning>

    After installation, all software appears in **Dashboard → Downloads**:

    | Tab | Contents |
    | - | - |
    | Operating System | OS images for your dev kit — flash directly from here |
    | SDKs | Host-side libraries and headers — configure device after install |
    | Tools | CLI tools (GCC toolchain, debugger) |
    | Extensions | VS Code extensions (C/C++, CMake Tools, etc.) |
  </Accordion>
</AccordionGroup>

***

## Step 2 — Activate Your Device

Navigate to the **Device** section and click **Activate** next to your connected device. This sets it as the *Active Device* for builds and flashing.

<img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/devices_available.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=0c0cb7bac249996229d606498d6748d7" alt="Available devices list" width="670" height="199" data-path="archives/2.1/Tools/QVSCE/images/devices_available.png" />

<img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/devices_active.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=8ce51d0a79247091ed6c25c6bbf449c3" alt="Activated device" width="654" height="346" data-path="archives/2.1/Tools/QVSCE/images/devices_active.png" />

<Note>
  For devices running Ubuntu OS, see the [Ubuntu Device
  Setup](./setup/install-vscode#ubuntu-device-setup) section.
</Note>

***

## Step 3 — Flash Device Software

Open **Dashboard → Downloads → Operating System tab** and click **Flash & Setup Device** next to the image for your dev kit.

<img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/dashboard_downloads_os.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=87beb9ff989dbd217048940ffd93c85c" alt="Downloads — Operating System tab" width="1569" height="378" data-path="archives/2.1/Tools/QVSCE/images/dashboard_downloads_os.png" />

<Warning>
  **Do not disconnect the device during flashing.** An interrupted flash can
  destabilize the device and may require power-cycle + manual EDL + reflash to
  recover.
</Warning>

***

## Step 4 — Develop Your Application

Navigate to **Projects** to browse sample projects or import templates from the SDK. IntelliSense is configured automatically when a project is open.

<img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/projects_recent.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=ad9ddcd9e8e82d9e5035bf947b5b0d34" alt="Projects — recent projects" width="332" height="226" data-path="archives/2.1/Tools/QVSCE/images/projects_recent.png" />

Use the **Status Bar buttons** to build, deploy, run, and select your target device:

<CardGroup cols={3}>
  <Card title="Build" icon="hammer">
    Cross-compile the application for the active device.
  </Card>

  <Card title="Deploy" icon="rocket">
    Build and push the binary to the active device.
  </Card>

  <Card title="Run" icon="play">
    Execute the deployed binary on the device.
  </Card>

  <Card title="Refresh Device" icon="arrows-rotate">
    Re-scan for connected devices.
  </Card>

  <Card title="Select a Connected Device" icon="microchip">
    Choose which connected device to target.
  </Card>
</CardGroup>

<img src="https://mintcdn.com/qualcomm-staging/blZpKs_b9On5nj-y/archives/2.1/Tools/QVSCE/images/status_bar_buttons.png?fit=max&auto=format&n=blZpKs_b9On5nj-y&q=85&s=81c8ee1f7e4cc56fd6d1cc1f8706cea0" alt="VS Code Status Bar — Build, Deploy, Run, Refresh Device, and device selector buttons" width="1548" height="1016" data-path="archives/2.1/Tools/QVSCE/images/status_bar_buttons.png" />

<Warning>
  By default, **Deploy** installs the binary at `/usr/bin`, overwriting any
  existing binary with the same name on the device.
</Warning>