roll: pigweed pw_async2: Move DoDestroy out of the base Task class DoDestroy() makes it possible for Dispatchers to own a Task's memory. The dispatcher calls DoDestroy() to free the task when it completes. Tasks not owned by the dispatcher should not implement DoDestroy(). Move the virtual DoDestroy() function to a derived OwnedTask class to make memory ownership explicit. Track if a Task is an OwnedTask with a member variable. This simplifies removing the task execution lock in a subsequent CL. The Dispatcher checks if the task needs to be destroyed while the dispatcher lock is held, then releases the lock and calls DoDestroy(). Since the Dispatcher owns these tasks exclusively, it is not necessary to hold the lock. This avoids deallocating memory while the dispatcher lock is held, and is a step towards removing the task execution lock. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/340534 Original-Revision: c3435af9777324f7246bbdaa87277b957cdac60d Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: fc42b65a4d06cf..c3435af9777324 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8699184704622453041 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I577139c945bbd817b5a1c8d304e444eed832b4c7 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/340633 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>
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.
git clone https://pigweed.googlesource.com/pigweed/quickstart/bazel pw_bazel_quickstart cd pw_bazel_quickstart
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.
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
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
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)
bazelisk test //... will run the unit tests defined in this project, such as the ones in modules/blinky/blinky_test.cc.
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.
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.