Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 2c4541cdd274ef6b9ab913a735a5afc9d8abbbe2
commit2c4541cdd274ef6b9ab913a735a5afc9d8abbbe2[log] [tgz]
authorYuval Peress <peress@pigweed.infra.roller.google.com>Mon Jul 14 22:53:30 2025 -0700
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 14 22:53:30 2025 -0700
treea5537eb1034873266ab99bbcce730124c1a51876
parenta82a5f6cf164b1d2c83645641c15f681701b6584 [diff]
roll: pigweed pw_env_setup: Update constraints for cryptography

The cryptography library version was conflicting with the latest
compatible version to Zephyr's. There seem to be no breaking changes
with updating the version so uprev Pigweed's constraints so ToT Pigweed
can be compatible with Zephyr's.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/305013
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: 77ec8928648a0d315499ac3b7df03f29f6ba9a9a

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: b93d534d1d0269..77ec8928648a0d
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8709302761495319377
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I832dacdb09184a0251c0c85705243d927bf608f4
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/305112
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: a5537eb1034873266ab99bbcce730124c1a51876
  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. AUTHORS
  18. BUILD.bazel
  19. CONTRIBUTING.md
  20. LICENSE
  21. MODULE.bazel
  22. MODULE.bazel.lock
  23. OWNERS
  24. pigweed.json
  25. README.md
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.