| commit | d3b9325539c0726c1bcf0598d493f26896f9f149 | [log] [tgz] |
|---|---|---|
| author | Joshua Liebow-Feeser <joshlf@pigweed.infra.roller.google.com> | Mon Aug 18 13:03:16 2025 -0700 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Aug 18 13:03:16 2025 -0700 |
| tree | 513979e046728191615711446212b9000945bdf5 | |
| parent | f0b0f43ef27a6d0afe278758c69fdc3e1a7590d2 [diff] |
roll: pigweed pw_kernel: Remove trait impls on Timer Remove impls of `[Partial]Eq` and `[Partial]Ord` on `Timer`. Before this commit, these impls considered two `Timer`s to be equal if their deadlines were equal, and disregarded their callbacks. If a `Timer` were inserted into a `HashMap` or similar collection, inserting a `Timer` with the same deadline as an existing `Timer` would cause the new one to replace the old one (probably not what the programmer would intend). Instead, we replace `ForeignList::sorted_insert` with `sorted_insert_by_key`, which sorts based on a specific field of the element type. This allows us to insert `Timer`s into `ForeignList`s by explicitly selecting the `deadline` field as the key. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/313832 Original-Revision: 70a7885506f1d03cbbe0d4e8b6a3965901958f58 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: e6c4f7493b2c8d..70a7885506f1d0 Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8706169056635696273 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I708adc433727698d1de062368f28314b4e5cce12 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/314072 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.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.