roll: pigweed e165669..ac4e444 (10 commits)

ac4e444:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255019 pw_multibuf: Add move tests for alloc future
81652cf:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255059 pw_multibuf: Fix alloc future desired_size()
66ac324:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255018 pw_multibuf: Android.bp for multibuf allocator
2b84a1d:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255016 pw_multibuf: Split async alloc out into its own target
b439dd3:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255015 pw_multibuf: Move async to new MultiBufAllocatorAsync
aaaac0a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255014 pw_multibuf: Introduce supertype for alloc futures
2d063e1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/254828 pw_multibuf: Move mem notify functionality inside alloc future
0a85225:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/254827 pw_multibuf: Remove unneeded PW_NO_LOCK_SAFETY_ANALYSIS
a2459e9:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255012 pw_kvs: Initialize memory for span in test
21d015f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/255172 pw_bluetooth_proxy: Update TODOs for ACL fragmentation

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: e1656695d75485..ac4e444390b13e
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8728271107106028497
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I369c3c4f9a2d915739860f6506cb65044cf50bee
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/255076
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: 550a31973514d0aa7c841a7690c4a1422a4dd3af
  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.