VS Code Setup

VS Code is the recommended development workflow for Hack-A-Bot 2026.

This page is the shared starting point for teams working with Raspberry Pi Pico projects. It is also the default editor recommendation across the site, even when a project uses a different runtime or library stack.

Official References

Start Here

  1. Install Visual Studio Code.
  2. Install the Raspberry Pi Pico VS Code extension.
  3. Let the extension install the toolchain it needs, or point it at an existing setup if you already have one.
  4. Create or import your project in VS Code before wiring the rest of the system together.

Minimum Host Checks

The official Raspberry Pi setup guidance is stricter than a normal text editor install. Before you start:

  • Use a recent VS Code release. Raspberry Pi’s published setup notes call out VS Code 1.92.1 or newer for the Pico extension.
  • On Linux, make sure you have Python 3.9+, git, tar, and a native C/C++ compiler available.
  • On macOS, run xcode-select --install before you expect compiling or debugging to work cleanly.
  • Use VS Code to prove a very small test first: blink an LED, print to serial, or read one sensor.
  • Confirm build, flash, and serial output before you start integrating motors, radios, or larger mechanisms.
  • Keep one known-good baseline project so you can separate software problems from wiring or power problems.

First Project Flow

The official Raspberry Pi flow is a good baseline for event-day bring-up:

  1. Create a new project from examples and start with blink.
  2. Choose the correct Pico-series board in the project wizard.
  3. Put the board into BOOTSEL mode before your first flash.
  4. Expect the first project setup to take several minutes while the extension installs the SDK and toolchain.
  5. Use the extension’s Run button for the fastest proof that compile and flash are both working.

If you prefer to flash manually, the extension also generates a UF2 file in your build directory that you can drag onto a Pico in BOOTSEL mode.

Good Early Checks

  • Can you build and flash reliably?
  • Can you open a serial monitor and see output?
  • Have you written down which board, pins, and power rails you are using?
  • If you change several things at once, can you still recover to a known working state?

Useful Features To Lean On

  • The official extension can create Pico SDK example projects directly from VS Code.
  • It handles SDK and toolchain setup automatically for the standard path.
  • Raspberry Pi also documents integrated offline Pico SDK documentation inside the editor, which is useful once you are wiring peripherals under time pressure.

If Your Project Uses Other Tools

  • Some project resources may still reference MicroPython, Arduino IDE, MATLAB, or ROS 2.
  • Treat VS Code as the default path unless your project supervisor explicitly tells you to use a different stack.

Common VS Code-Specific Problems

  • First-run setup taking longer than expected because the extension is downloading the SDK and tools.
  • Build or toolchain errors caused by missing Linux or macOS prerequisites.
  • Conflicts from old manual Pico SDK installs or older Pico setup methods already on the machine.
  • GitHub API rate limiting when the extension tries to fetch SDK or toolchain versions. The official extension README documents a user-level GitHub token setting for this case.

More Help

If your environment still is not working after a simple blink or serial test, ask a supervisor before moving on to the rest of the build.

This site uses Just the Docs, a documentation theme for Jekyll.