roll: pigweed 7fbccd0..0822879 (9 commits)

0822879:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/277532 pw_ide: Distinguish duplicate targets
1af8e0f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/276476 pw_bluetooth_proxy: Handle channel dtor during recombination
0f62a5e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/275693 pw_ide: Use clangd rule from @pigweed directly
d932875:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/277552 docs: Explain Label in style guide
a7a3cbe:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/272594 pw_ide: Replace compile command refresh with custom implementation
8e2ae80:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/277852 pw_bluetooth_sapphire: Fix l2cap_fuzzer timeout with 1MB input data
24596e9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/276935 bazel: Switch to Python 3.12
9b00f1a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/275714 pw_kernel: Add colors and visual cleanups to console output
69aedd9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/277792 pw_env_setup: Update watchdog

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 7fbccd0805fa21..0822879ad08d34
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8719843930649453697
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I536fd13787be1867075266157b66cd4190576226
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/277912
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
2 files changed
tree: a287e9038bbc3aff97ed56bbae9760aa97763a5d
  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.