commit | e315604b4f87885859d7fef36c0aa7b2b4c8f211 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Fri Apr 04 16:54:27 2025 -0700 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Apr 04 16:54:27 2025 -0700 |
tree | 3fd1a0267640e335cf2642a49bd79aa6d51aa62f | |
parent | efcb59e2e8c1f256c994cbc7ef03ec40b0ac4d70 [diff] |
roll: pigweed f59444c..90d1391 (12 commits) 90d1391:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281383 mbedtls: Remove `-fno-lto` from config 284af91:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281278 pw_kernel: Support Rust ABI thread entry points d780738:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/280836 pw_bluetooth_sapphire: Acquire wake leases in CommandChannel 5e3fd74:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/278013 pw_bluetooth_sapphire: Acquire wake leases in l2cap::ChannelImpl d91e37c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/277233 pw_kernel: Implement syscalls 143289f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281452 pw_tokenizer: Move test out of pw::tokenizer to reflect real use 7ce7812:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281279 bazel: Explicitly specify platforms for crates_std 7a7e380:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281374 pw_kernel: Thread entrypoints are `extern "C" fn`s 0478608:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/280977 pw_kernel: Add optional Mutex debug logging 26e657b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/269613 LTO: Retain symbols that were discarded by LTO 58e290a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/245173 pw_tokenizer: Clarify tokenization in headers b6ba89f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/281392 bazel: Update libusb source hash Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: f59444c8dae1be..90d1391ff0c2fc Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8718475686117913121 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ide6a823053341614fb5d6ba785d0b665245c2bb1 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/281434 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: 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
.