Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 5b38e63e04e699fdebfce92640e2d7c825ca4a6a
commit5b38e63e04e699fdebfce92640e2d7c825ca4a6a[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Jan 29 17:54:19 2025 -0800
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 29 17:54:19 2025 -0800
treed0ba5a29b536caedf0b256cb5fd3810cca4cc1a6
parent31b2ded1b198c5a1908dd8ea02160142103c9323 [diff]
roll: pigweed a42890d..1fec695 (5 commits)

1fec695:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/263515 pw_uart: clang-tidy fix
c332380:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/263097 build: Roll rust toolchain
4379803:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/263552 pw_transfer: clang-tidy fixes
f1cc327:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/263494 clang-tidy: Config updates
23840c1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/263514 pw_software_update: clang-tidy fix

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: a42890dfefc2ac..1fec695ebe7809
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8724356947819929329
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I75db1e251329d692d1d48615003dca2ed777f673
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/263414
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
2 files changed
tree: d0ba5a29b536caedf0b256cb5fd3810cca4cc1a6
  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. .clangd.shared
  14. .gitignore
  15. .pw_console.yaml
  16. AUTHORS
  17. BUILD.bazel
  18. CONTRIBUTING.md
  19. LICENSE
  20. MODULE.bazel
  21. MODULE.bazel.lock
  22. OWNERS
  23. pigweed.json
  24. 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.