picodev
picodev is a Python CLI package for Raspberry Pi Pico development. It installs the
Pico SDK and ARM GCC toolchain for the current operating system, creates Pico C/C++
projects, and runs build/flash commands from picodev.toml.
Install
pip install picodev
For local development from this repository:
pip install -e .
Commands
picodev doctor
picodev install
picodev new blink
picodev new hello-world
cd blink
picodev build
picodev clean
picodev flash
The CLI can also be invoked through the Python interpreter, including on Windows:
python -m picodev --help
python -m picodev --version
picodev install downloads the Pico SDK and ARM GCC toolchain. The installer selects
the correct toolchain for:
- Linux x64
- Linux arm64
- macOS x64
- macOS arm64
- Windows x64
The default install location is ~/.picodev. Set PICODEV_HOME to use a
different directory.
picodev build and picodev flash automatically run with the installed Pico SDK
and ARM GCC toolchain environment. You do not need to manually configure paths.
picodev doctor checks the tools required by the current platform.
The installed tree layout:
~/.picodev/toolchains/pico-sdk-2.0.0/
pico-sdk/
~/.picodev/toolchains/arm-none-eabi-gcc-13.2.1/
bin/
arm-none-eabi/
Pico SDK and Toolchain Sources
Pico SDK: https://github.com/raspberrypi/pico-sdk
ARM GCC: https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads
Downloaded archives are verified with SHA-256 digests.
Custom Toolchain Locations
By default, picodev uses the toolchains installed in ~/.picodev/toolchains. You can
override these locations using environment variables:
PICO_SDK_PATH: Path to a custom Pico SDK installationPICO_TOOLCHAIN_PATH: Path to a custom ARM GCC toolchain installation
When these variables are set, picodev build will automatically:
- Use the custom toolchain/SDK paths
- Add the toolchain's
bindirectory to PATH - Configure CMake with the correct paths
Example (Windows PowerShell):
$env:PICO_TOOLCHAIN_PATH = "$env:USERPROFILE\.picodev\toolchains\arm-gcc-13.2.Rel1-windows-x64"
$env:PICO_SDK_PATH = "$env:USERPROFILE\.picodev\toolchains\pico-sdk-2.0.0"
python -m picodev build
Example (Linux/macOS):
export PICO_TOOLCHAIN_PATH="$HOME/.picodev/toolchains/arm-gcc-13.2.Rel1-linux-x64"
export PICO_SDK_PATH="$HOME/.picodev/toolchains/pico-sdk-2.0.0"
picodev build
This is useful when:
- Using a different version of the toolchain or SDK
- Testing with a development version of the Pico SDK
- Sharing a toolchain across multiple projects
- Using system-installed toolchains
Project Format
picodev new blink creates a Pico project:
blink/
picodev.toml
CMakeLists.txt
pico_sdk_import.cmake
main.c
.gitignore
Use --board pico_w to create a Pico W project:
picodev new my-project --board pico_w
Default picodev.toml:
[pico]
board = "pico"
[build]
name = "blink"
build_dir = "build"
sources = ["main.c"]
Build Flow
picodev build uses CMake to compile your Pico project:
- Configures CMake with Pico SDK path
- Builds the project with ARM GCC toolchain
- Generates
.uf2file for flashing
Example:
cd blink
picodev build
Output will be in build/blink.uf2.
To remove all generated build files and start from a clean configuration:
picodev clean
The command only removes the build_dir configured in picodev.toml and refuses
to delete the project root or a directory outside the project.
Flashing
picodev flash programs the ELF firmware over SWD using pyOCD:
- Connect a CMSIS-DAP compatible debug probe to the Pico SWD pins
- Connect the probe over USB
- Run
picodev flash
The command selects rp2040 for Pico/Pico W and rp2350 for Pico 2, then
programs build/<project>.elf. Use --probe <ID> when multiple probes are connected.
picodev flash
To list the debug probes detected by pyOCD:
picodev flash --detect
Supported Boards
pico- Raspberry Pi Pico (RP2040)pico_w- Raspberry Pi Pico W (RP2040 with WiFi)pico2- Raspberry Pi Pico 2 (RP2350)pulsar_rp- UNIT Pulsar RP (RP2350; uses the Pico 2 SDK definition)dualmcu_rp- UNIT DualMCU RP (RP2040; uses the Pico SDK definition)
For example:
picodev new pulsar-project --board pulsar_rp
picodev new dualmcu-project --board dualmcu_rp
Example Project
Default blink project (main.c):
#include <stdio.h>
#include "pico/stdlib.h"
int main() {
stdio_init_all();
const uint LED_PIN = 25;
gpio_init(LED_PIN);
gpio_set_dir(LED_PIN, GPIO_OUT);
while (true) {
gpio_put(LED_PIN, 1);
sleep_ms(500);
gpio_put(LED_PIN, 0);
sleep_ms(500);
}
}
For Pico W, the LED control uses the CYW43 wireless chip:
#include <stdio.h>
#include "pico/stdlib.h"
#include "pico/cyw43_arch.h"
int main() {
stdio_init_all();
if (cyw43_arch_init()) {
printf("Wi-Fi init failed\n");
return -1;
}
while (true) {
cyw43_arch_gpio_put(CYW43_WL_GPIO_LED_PIN, 1);
sleep_ms(500);
cyw43_arch_gpio_put(CYW43_WL_GPIO_LED_PIN, 0);
sleep_ms(500);
}
}
Development Workflow
-
Install toolchains:
picodev install -
Create a project:
picodev new my-project cd my-project
-
Edit
main.cwith your code -
Build:
picodev build -
Clean generated build files when needed:
picodev clean -
Flash to Pico over SWD:
picodev flash -
Your code runs immediately after flashing!
Requirements
- Python 3.9+
- CMake 3.20 or newer (install separately)
- Ninja on Windows (installed by
picodev install) - picotool on Windows (installed by
picodev install) - Git (optional, for submodule initialization)
See the CMake installation guide for detailed Windows,
Ubuntu/Debian, and macOS instructions, including PATH troubleshooting.
On Ubuntu/Debian:
sudo apt install cmake git
On macOS:
brew install cmake git
On Windows:
winget install --exact --id Kitware.CMake --source winget
Alternatively, download the installer from https://cmake.org/download/ and make
sure its option to add CMake to PATH is selected.
If pip warns that picodev.exe was installed in a directory that is not on
PATH, the module form remains available without changing PATH:
python -m picodev doctor
python -m picodev install
To use the shorter picodev command, print the Scripts directory with the
following command and add that directory to your user PATH:
python -c "import sysconfig; print(sysconfig.get_path('scripts'))"
Support
For documentation, bug reports, and feature requests, visit the UNIT-Electronics-Labs/unit_devlab_pico repository. Report problems through GitHub Issues.
License
MIT
Metadata
Release files for picodev 0.1.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| picodev-0.1.12.tar.gz | 23.9 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| picodev-0.1.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 42.6 kB
Release files / picodev-0.1.12.tar.gz
| Download URL | picodev-0.1.12.tar.gz |
|---|---|
| Size | 23.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2dc6ab0d14fe1cf7385d608048a5ebd1f26d314e8f33e598c60f72cb64b8633
|
|
BLAKE2b-256 checksum How to use checksums |
f3fa37610c6d4986453ac919d7d09aedbb5858d68371644f9848f248c74c878a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 14, 2026.
Transparency logRelease files / picodev-0.1.12-py3-none-any.whl
| Download URL | picodev-0.1.12-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ded39985562c5d1dcf37b6e072ff7f4920b7058317ac0e3feb6480dcedc8bf9
|
|
BLAKE2b-256 checksum How to use checksums |
b8308b04f31ba0c2d9c8cc24fbd231a15928a6baf51c86ca780669d8b07c031f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 14, 2026.
Transparency logSecurity for picodev 0.1.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for picodev-0.1.12.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 14, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.