roll: pigweed 48712ad..0942b69 (10 commits)

0942b69:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/234817 pw_allocator: Refactor best- and worst-fit allocators to use buckets
0766dba:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/234816 pw_allocator: Refactor first fit allocators
3bfdac7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/234815 pw_allocator: Refactor Bucket
f84afe1:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/234812 pw_allocator: Parameterize BlockAllocator on blocks
8cc8495:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/234814 pw_malloc: Additional checks when testing
65b5e33:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/249372 pw_allocator: Fix metrics for blocks that shift bytes
33d00a7:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/234811 pw_allocator: Use BlockResult in BlockAllocator
f43ca4f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/242633 pw_allocator: Use move-semantics for Block API
6417a52:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/232214 pw_allocator: Add static polymorphism to Block
a287811:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/248192 pw_bytes: Add utility for checking alignment

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 48712ad0655654..0942b69025f298
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8730908256887283937
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I7fee794b41a07f6e650888b0e4f812319928b286
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/249834
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>
1 file changed
tree: 62b4e0652bd9a064f61afa361cdb36686dc5c78e
  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. OWNERS
  22. pigweed.json
  23. 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.