Skip to main content

​
Status Bar Actions

The VS Code Status Bar at the bottom of the window contains action buttons added by the extension: VS Code Status Bar — Qualcomm action buttons
#ButtonAction
1BuildCross-compile the project for the active device
2DeployBuild + push the binary to the device
3RunExecute the deployed binary on the device
4Refresh DeviceRe-scan for connected devices
5Select a Connected DeviceChoose which connected device to target
Deploy installs the binary at /usr/bin by default. This overwrites any existing binary with the same name on the device. Rename your output binary if you want to keep multiple versions.

​
Build

Click Build (or run the Build task via Ctrl+Shift+B). The extension uses the SDK toolchain configured by the workspace and compiles the project. 
cmake -B build -DCMAKE_TOOLCHAIN_FILE=$QSC_TOOLCHAIN
cmake --build build

​
Deploy

Click Deploy. The extension compiles the project (same as Build) and then pushes the binary over ADB or SSH. 
# Equivalent ADB push
adb push ./build/my-app /usr/bin/my-app

​
Run

Click Run to execute the deployed binary on the active device. The extension launches the binary over ADB or SSH and streams its output to the integrated terminal. 
# Equivalent ADB invocation
adb shell /usr/bin/my-app

​
Debug

1

Set a breakpoint

Click in the gutter next to a source line to set a breakpoint.
2

Start the debug session

Click Debug in the Status Bar or press F5.
3

Inspect state

The debug panel provides access to: - Variables pane — local and global variable values - Watch pane — custom expressions - Call Stack — full call chain from the breakpoint - Registers — hardware register contents - Disassembly — mixed source + assembly view - Memory — raw memory inspection
The debug configuration is auto-generated in .vscode/launch.json. Edit this file to change the remote target address, binary path, or GDB/LLDB arguments.

​
Troubleshooting builds

The .vscode/c_cpp_properties.json file may be stale. Run QVSCE: Regenerate Workspace from the Command Palette (Ctrl+Shift+P) to regenerate it.
Verify the active device is correctly set in Dashboard → Devices. Check that ADB/SSH connectivity is working:
adb devices   # ADB
ssh user@<device-ip> echo ok   # SSH
Ensure the binary was compiled with debug symbols (-g flag). Verify that gdbserver is installed on the device — run which gdbserver over ADB/SSH to confirm.