roll: pigweed e1e82ce..057c218 (9 commits)

057c218:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267772 pw_tokenizer: Remove invalid argument from CMake custom command
b568955:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/260218 pw_bluetooth_sapphire: Support solicitation uuids in scan filters
eec66b2:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267614 docs: Add guidance for extending Python imports
fe7961c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267512 pw_toolchain: Infinite loop function
551ff04:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267515 pw_bluetooth_proxy: Remove unused includes
32bbaba:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267518 pw_bluetooth_proxy: Test close and reset across all channel types
318a909:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/264640 pw_containers: Add size reports
4474c41:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267517 pw_bluetooth_proxy: Support event_fn in GATT channels
8237d75:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/267516 pw_bluetooth_proxy: Allow designated init of rfcomm config fields

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: e1e82ce2b51df6..057c2187d3731d
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8723021781316228465
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib5aa67eadb8fc915512070a75b27a34f4d2a1462
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/267832
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: b3e607aa8a8cbc45c0fbee2f94cc2473d06516bc
  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.