roll: pigweed pw_bluetooth_sapphire: Reland "[bt][gap] Update inspect properties for pairing"

This is a reland of commit 028ad1ae9b2ee08f45be36af3a7fe0df4777dd3b

This reverts commit 374c4d6cb4501a6bcc89ed3fd1ef456a447b1cf6.

Relanding this with no changes (except for a merge conflict resolution).
Originally reverted because it was a parent change of fxr/1062293, which
did need to be reverted.

Original change's description:
> [bt][gap] Update inspect properties for pairing
>
> Add inspect node to PairingStateManager and update inspect hierarchy
> between BredrConnection, PairingStateManager, and
> SecureSimplePairingSttate/LegacyPairingState.
>
> Test: fx test //src/connectivity/bluetooth
> Change-Id: I123f2ce325d6e0c5580f5434ea465fae7c1e80be
> Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1100556
> Reviewed-by: Marie Janssen <jamuraa@google.com>
> Commit-Queue: Lulu Wang <luluwang@google.com>

Original-Bug: b/42173830
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1108261
GitOrigin-RevId: 263e156f32362bc91eba445f7ce6a7340f0026cb
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/235313
Presubmit-Verified: CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Original-Revision: e0174978dc6d09339844a9c93121fb53aec1aa01

Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed
Rolled-Commits: aae9c54eecd1c9..e0174978dc6d09
Roller-URL: https://ci.chromium.org/b/8736969746660696657
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I8528dd5c7d3767bbbda70ac3d4d269921b036f3a
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/235206
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: ff1225b933efad106fa614f6564f4af68450416d
  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.