roll: pigweed pw_async2: Rework pw_async2 coroutines

- Update Coro to support waiting only on futures or other coroutines.
- Abort coroutine execution when allocation of a nested coroutine fails.
  Previously, coroutines required Status-compatible return types, and
  the framework would inject an INTERNAL status on allocation failure.
- Support any return type for coroutines, including void.
- Return a custom Result-like type instead of Poll from Coro::Pend. This
  allows the type to report an "aborted" status for coroutines that fail
  to allocate.
- Make Coro::Pend private to direct users to upstream Coro task impls.
- Introduce CoroTask, a coroutine task that crashes on allocation
  failure. FallibleCoroTask allows specifying an error handler.
- Deprecate CoroOrElseTask. FallibleCoroTask should be used instead.
- Simplify the coroutine implementation in various ways including
  removing some helper types and avoiding pw::Function.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/374695
Original-Revision: 45dfce49734fcf472a9b9de61332efff31f0219d

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 2c9165a12cc4a3..45dfce49734fcf
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8688297865244954673
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I1937a4989398b3f18698f22a92943994799430d4
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/381733
1 file changed
tree: 71252b3d4eabdb367c592408174e66d6db04c838
  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. .pylintrc
  18. AUTHORS
  19. BUILD.bazel
  20. CONTRIBUTING.md
  21. LICENSE
  22. MODULE.bazel
  23. MODULE.bazel.lock
  24. mypy.ini
  25. OWNERS
  26. pw
  27. README.md
  28. workflows.json
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.