Google Git
Sign in
pigweed/pigweed/quickstart/bazel/60c87f7825fa553bec2be7fb7cc66c4ff7cc4eb2
commit
60c87f7825fa553bec2be7fb7cc66c4ff7cc4eb2
[log]
author
Lloyd Pique <lpique@pigweed.infra.roller.google.com>
Wed May 06 17:24:57 2026 -0700
committer
CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Wed May 06 17:24:57 2026 -0700
tree
b4168b64481c621a8cbfcaf5974264e4b0677e30
parent
c37c839687acd25bef98e8a0442a9bf2deca3a5e [diff]
roll: pigweed pw_kernel: Disable a lint warning in pw_gdb_protocol

With a pending Rust toolchain roll, a lint error was being raised in
pw_gdb_protocol that the code in packet.rs should switch to obtaining
`std::io::ErrorKind::InvalidInput` from `core`.

Instead as the lint warning comes from a nightly feature Pigweed isn't
using, we disable the lint warning by adding a
`#[allow(clippy::std_instead_of_core)]` to the function.

Original-Bug: 509645441
Test: ./pw build k_host_lint
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/407034
Original-Revision: de872e3f95247cee33a7cd643c7a29bd5bcaa875

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: d43acc26e2509f..de872e3f95247c
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8682506698063605889
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ie0aa229e56501d815ac412b78874b23cf74c0b7e
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/407612
1 file changed
tree: b4168b64481c621a8cbfcaf5974264e4b0677e30
  1. .github/
  2. .vscode/
  3. apps/
  4. modules/
  5. system/
  6. targets/
  7. tools/
  8. .bazelignore
  9. .bazelrc
  10. .bazelversion
  11. .buildifier.json
  12. .clang-format
  13. .clang-tidy
  14. .clangd.shared
  15. .gitignore
  16. .pw_console.yaml
  17. .pylintrc
  18. AUTHORS
  19. BUILD.bazel
  20. CONTRIBUTING.md
  21. LICENSE
  22. MODULE.bazel
  23. MODULE.bazel.lock
  24. mypy.ini
  25. OWNERS
  26. pw
  27. README.md
  28. workflows.json
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It is a LED-blinking service (featuring RPC control!) for the Raspberry Pi Pico. It can also be run on any computer using the included simulator.

Getting the code

git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart
cd pw_bazel_quickstart

Dependencies

The only dependency that must be installed is Bazelisk.

Bazelisk is a launcher for the Bazel build system that allows for easy management of multiple Bazel versions.

Instructions for installing Bazelisk can be found here.

Running on the simulator

To run the simulator, type: bazelisk run //apps/blinky:simulator_blinky Then, in a new console, connect to the simulator using: bazelisk run //apps/blinky:simulator_console

Running on hardware

To start, connect a Raspberry Pi Pico, Pico 2, or debug probe via USB.

To run on the Raspberry Pi Pico, type: bazelisk run //apps/blinky:flash_rp2040 Then, in a new console, connect to the device using: bazelisk run //apps/blinky:rp2040_console

Controlling the LED

Once connected with a console, RPCs can be sent to control the LED. Try running:

device.set_led(True)
device.set_led(False)
device.toggle_led()
device.blink(blink_count=3)

Running unit tests on the host device

bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.

Running unit tests on hardware

bazelisk run @pigweed//targets/rp2040/py:unit_test_server in one console followed by bazelisk test //... --config=rp2040 will also allow running the unit tests on-device.

Next steps

Try poking around the codebase for inspiration about how Pigweed projects can be organized. Most of the relevant code in this quickstart (including RPC definitions) is inside modules/blinky, with some client-side Python code in tools/console.py.