roll: pigweed d058875..4249230 (10 commits)

4249230:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271736 pw_ide: Add a clangd dashboard UI to help user find issues
018a807:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/264633 pw_ide: Add a button to dump logs and settings.json
bc5c177:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/264612 pw_ide: Add webview in sidebar to see extension report
d7be437:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/272512 pw_kernel: Remove unused WaitQueue::wake_thread method
52f1e7f:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/272593 pw_env_setup: Restrict visibility of py libraries
1a42475:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/272672 pw_allocator: Add source files to Android.bp targets
57db167:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271685 pw_kernel: Optimize SpinLocks
9f43335:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271812 pw_kernel: Add Mutex
eeed50e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/271753 pw_kernel: Make some scheduler variable names more descriptive
b6da978:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/272592 pw_env_setup: Fix docs headings

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: d058875cb35bb1..42492303110d25
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8721366659929075025
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ia4e2ef9bbf7cb6bfd90b72d0aaa53ff9fd54de23
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/272515
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
1 file changed
tree: 5dbaf80eeb47d24e639735a1b5ce15f9dc1d2311
  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. AUTHORS
  18. BUILD.bazel
  19. CONTRIBUTING.md
  20. LICENSE
  21. MODULE.bazel
  22. MODULE.bazel.lock
  23. OWNERS
  24. pigweed.json
  25. 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.