roll: pigweed 3c04c1c..654d7ad (11 commits)

654d7ad:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/265452 CMake: Add more missing headers and deps
e7c7ee6:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/266152 pw_kernel: Add experimental prototype
cbc2c8a:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/265992 pw_toolchain: Document pw::ConstexprTag
0093c1c:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/266132 docs: Update changelog
101907b:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/265616 docs: Update Bazel docgen guide
e450027:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/263872 pw_presubmit: Add rp2350 to presubmit
0ccbac3:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/265876 pw_toolchain: Move pw::ConstexprTag to pw_toolchain
82c223e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/265873 pw_hex_dump: Enable layering check
42dcfa3:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/266113 pw_bluetooth_proxy: Add missing `parameter_total_size` to test helper
ec7307e:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/266092 bazel: Add stub kernel bazel_presubmit program
4103b07:https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/266112 docs: Update bazel_integration.rst

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: 3c04c1c1c81f5a..654d7ad276fe86
Roll-Count: 1
Roller-URL: https://cr-buildbucket.appspot.com/build/8723551453298509537
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I16870c6fd9e1f9d7c867b5feab12f872a8dd68f7
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/266055
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: 0966b70e144652b4863306f359e538e5335d6675
  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. MODULE.bazel.lock
  22. OWNERS
  23. pigweed.json
  24. 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.